[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPW88EVBWFR8GCJM22RN4X":3,"skill-same:01M7DPW88EVBWFR8GCJM22RN4X":108},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":14,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M7DPW88EVBWFR8GCJM22RN4X","product-research",null,"Use when planning and synthesizing product\u002Fuser research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation\u002Fsample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team\u002Fux-researcher-designer (persona\u002Fjourney artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A\u002FB) — this is the research-ops method + insight-repository layer.","Prudhviraj101\u002FX_Agent","Prudhviraj101","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141725940?v=4","01M7DN1Y3RW3QD7692M89MPS3D","MALLA PRUDHVI RAJ S S N MURTHY","01M7DN1Y4A763ESFP16P13EE19",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: product-research\ndescription: Use when planning and synthesizing product\u002Fuser research as a method-and-repository discipline — selecting the right method for the goal (generative interviews vs usability test vs concept test vs validation), computing method-based saturation\u002Fsample size with an explicit confidence level, or synthesizing coded observations into insights while flagging single-source anecdotes. Never fabricates user insight; an insight requires recurrence across independent participants. Distinct from product-team\u002Fux-researcher-designer (persona\u002Fjourney artifacts), product-discovery (discovery-sprint planning), and experiment-designer (live A\u002FB) — this is the research-ops method + insight-repository layer.\nversion: 2.9.0\nauthor: claude-code-skills\nlicense: MIT\ntags: [research-ops, product-research, ux-research, jtbd, usability, saturation, insight-synthesis, research-repository]\ncompatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]\n---\n\n# product-research\n\nProduct \u002F user research as an operational discipline: choosing the right method, sizing it honestly, and synthesizing findings into governed insights. The core rule: **method must match the goal**, and **an insight requires recurrence across independent participants** — a single quote is an anecdote.\n\n## Purpose\n\nProduct researchers, ResearchOps teams, and PMs running discovery need method rigor and an insight repository they can trust. This skill structures three decisions:\n\nThree deterministic tools:\n\n1. `study_designer.py` — Maps (research goal × product stage) to an appropriate method and emits a method-matched plan skeleton (objective, participant criteria, guide structure, success criteria). Redirects live A\u002FB to `product-team\u002Fexperiment-designer`.\n2. `saturation_planner.py` — Method-based sample guidance with an explicit **confidence label**: Nielsen problem-discovery (5\u002Fsegment), Guest et al. thematic saturation (~12), and evaluative coverage. Never claims a prevalence rate from a small-n usability test.\n3. `insight_synthesizer.py` — Clusters coded observations by tag, counts distinct participants, ranks by cross-participant recurrence, and flags any candidate below the source threshold as an **ANECDOTE**, never promoting it to an insight.\n\n## When to use\n\nInvoke this skill when:\n\n- You are planning a study and need the method to match the goal (generative vs evaluative vs validation).\n- You need a defensible sample size \u002F saturation rationale with a stated confidence.\n- You have raw coded observations and need to synthesize insights without over-claiming.\n- You are setting up or auditing a research repository and need the insight-vs-observation discipline.\n\n**Do NOT use this skill to**: generate personas \u002F journey maps (use `product-team\u002Fux-researcher-designer`), plan a discovery sprint or validate an opportunity (use `product-team\u002Fproduct-discovery`), design or analyze a live product A\u002FB experiment (use `product-team\u002Fexperiment-designer`), or do market sizing \u002F surveys (use the `market-research` sibling).\n\n## Workflow\n\n1. **Frame the study** — Fill `assets\u002Fresearch_plan_template.md` (research questions, method rationale, participant criteria, analysis plan, repository tagging scheme).\n2. **Pick the method** — Run `study_designer.py --goal {discovery|evaluative|validation} --stage {concept|prototype|beta|live} --profile {b2b-saas|consumer-app|enterprise|marketplace|hardware|platform}`. Honor the redirect if it routes to experiment-designer.\n3. **Size it** — Run `saturation_planner.py --method {usability|thematic|evaluative-coverage} --segments N`. Record the confidence label and limits.\n4. **Synthesize** — After fielding, code observations and run `insight_synthesizer.py --input observations.json --min-sources 3`. Treat ANECDOTE-flagged clusters as signals to probe, not findings to ship.\n5. **File in the repository** — Tag insights to the atomic schema at synthesis time, with their evidence and confidence.\n\n## Scripts\n\n| Script | Purpose | Profiles |\n|---|---|---|\n| `scripts\u002Fstudy_designer.py` | (goal × stage) → method + plan skeleton | b2b-saas, consumer-app, enterprise, marketplace, hardware, platform |\n| `scripts\u002Fsaturation_planner.py` | Method-based sample guidance + confidence | n\u002Fa (method-driven) |\n| `scripts\u002Finsight_synthesizer.py` | Cluster observations, flag anecdotes | n\u002Fa (evidence-driven) |\n\nAll three: stdlib-only, `--help`, `--sample`, `--output {human,json}`.\n\n## Onboarding & customization\n\nRun the onboarding questionnaire **once before you start** — it captures your defaults so every tool in this skill is pre-configured. Customization is the point: the answers actually change tool behavior (e.g. the insight source-threshold).\n\n```bash\npython3 scripts\u002Fonboard.py            # interactive (also: --defaults, --set key=value, --reset)\npython3 scripts\u002Fonboard.py --show     # see the questions + current effective config\n```\n\nAnswers are saved to `~\u002F.config\u002Fresearch-ops\u002Fproduct-research.json` (global) or `.\u002F.research-ops\u002Fproduct-research.json` (`--scope project`) and are read automatically by `config_loader.py`. They set the default product **profile**, the **insight source-threshold** (how many independent participants make a finding an insight, not an anecdote), the default **saturation method**, and the **high-stakes** flag. CLI flags always override saved config; `RESEARCH_OPS_NO_CONFIG=1` ignores it.\n\n**The four questions:** product profile · insight source-threshold · saturation method · high-stakes flag.\n\n## Optimize with autoresearch (opt-in)\n\nThis skill ships an **isolated, opt-in** bridge to `engineering\u002Fautoresearch-agent`. Only when you ask to \"optimize the synthesis\" \u002F \"run a loop\" does an autoresearch experiment iteratively refine the coding\u002Fclustering of a fixed evidence set so more cross-participant patterns surface. `scripts\u002Far_evaluator.py` is the ground-truth evaluator; it prints `validated_insights: \u003Cint>` (higher is better). It optimizes the **coding**, never fabricates evidence.\n\n```bash\n\u002Far:setup --domain custom --name insight-synthesis \\\n  --target observations.json \\\n  --eval \"python3 ar_evaluator.py --target observations.json\" \\\n  --metric validated_insights --direction higher\n\u002Far:loop custom\u002Finsight-synthesis\n```\n\nIsolated: no hard dependency — autoresearch runs only on demand, and the loop edits `observations.json`, never the evaluator.\n\n## References\n\n- `references\u002Fresearch_methods_canon.md` — Portigal *Interviewing Users*; Christensen\u002FUlwick JTBD; Rohrer's UX-research methods landscape (NN\u002Fg); Sauro & Lewis *Quantifying the User Experience*; Goodman\u002FKuniavsky.\n- `references\u002Fsampling_and_saturation.md` — Nielsen \"test with 5 users\"; Guest, Bunce & Johnson saturation; Faulkner on more-than-5; Sauro usability sample size; Braun & Clarke thematic analysis.\n- `references\u002Frepository_and_synthesis.md` — ResearchOps \u002F atomic research (Tomer Sharon \"Polaris\"); insight-vs-observation discipline; repository governance; affinity mapping; democratization guardrails.\n\n## Assumptions\n\n- Method selection assumes you can name the goal honestly; if the goal is fuzzy, grill it first (the goal drives everything).\n- Saturation guidance is method-based, not a power calculation — usability tests find problems, not prevalence rates.\n- The synthesizer counts evidence you provide; coding quality is upstream of it. Garbage tags → garbage clusters.\n- The insight threshold (`--min-sources`) defaults to 3; raise it for high-stakes or heterogeneous populations.\n\n## Anti-patterns\n\n- **Mismatching method to goal.** A usability test cannot discover unmet needs; an interview cannot measure task success.\n- **Reporting usability problems as percentages.** Small-n tests surface problems, not population rates.\n- **Promoting an anecdote to an insight.** One participant is a signal to probe, not a finding.\n- **Framing interview questions as feature reactions.** Probe the job-to-be-done and recent real behavior, not hypothetical opinions.\n- **Synthesizing without a repository scheme.** Tag at synthesis time, or insights rot unfindable.\n\n## Distinct from\n\n| Neighbor | Scope | Difference |\n|---|---|---|\n| `product-team\u002Fux-researcher-designer` | Personas, journey maps, usability frameworks tied to design output | That produces **artifacts**; this is **method + repository discipline** |\n| `product-team\u002Fproduct-discovery` | Opportunity validation, discovery-sprint planning | That plans **discovery sprints**; this designs and synthesizes the **research** |\n| `product-team\u002Fexperiment-designer` | Live product A\u002FB hypothesis + sample size | That runs **live experiments**; this runs **qualitative\u002Fevaluative research** |\n| `market-research` (sibling) | Market sizing, surveys, segmentation | That studies **the market**; this studies **users** |\n\n## Quick examples\n\n```bash\npython3 scripts\u002Fstudy_designer.py --sample\npython3 scripts\u002Fsaturation_planner.py --method thematic --segments 3\npython3 scripts\u002Finsight_synthesizer.py --sample --min-sources 3\n```\n\nThe synthesizer sample correctly promotes \"import-confusion\" (3 independent participants) to INSIGHT and flags \"wants-slack\" (1 participant) as an ANECDOTE.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-research-ops` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is this study generative (discover problems) or evaluative (test a solution)?\"**\n   Recommended: name it first — the method follows from the goal.\n   Canon: Rohrer, *When to Use Which User-Experience Research Methods* (NN\u002Fg).\n\n2. **\"What's your sample size and saturation rationale — and at what confidence?\"**\n   Recommended: method-based n (5\u002Fsegment usability; ~12 for thematic saturation), state the confidence.\n   Canon: Nielsen; Guest, Bunce & Johnson (2006); Faulkner (2003).\n\n3. **\"How many independent participants support each insight — or is it a single-source anecdote?\"**\n   Recommended: require recurrence across ≥3 sources before calling it an insight; flag singletons.\n   Canon: atomic research \u002F ResearchOps; Braun & Clarke thematic analysis.\n\n4. **\"Are your interview \u002F usability tasks framed as outcomes (jobs) or as feature reactions?\"**\n   Recommended: frame around the job-to-be-done and recent real behavior, not hypothetical opinion.\n   Canon: Christensen\u002FUlwick Jobs-to-be-Done; Portigal *Interviewing Users*.\n\n5. **\"Where does this land in the repository, and how is it tagged for reuse?\"**\n   Recommended: tag to the atomic schema at synthesis time, not later.\n   Canon: Tomer Sharon, *Polaris* \u002F ResearchOps repository practice.\n\nWalk depth-first. Lock 1-2 before opening 3-5. After all are answered, invoke `study_designer.py` → `saturation_planner.py` → (after fielding) `insight_synthesizer.py`.\n","# product-research\n\nProduct \u002F user research as an operational discipline: choosing the right method, sizing it honestly, and synthesizing findings into governed insights. The core rule: **method must match the goal**, and **an insight requires recurrence across independent participants** — a single quote is an anecdote.\n\n## Purpose\n\nProduct researchers, ResearchOps teams, and PMs running discovery need method rigor and an insight repository they can trust. This skill structures three decisions:\n\nThree deterministic tools:\n\n1. `study_designer.py` — Maps (research goal × product stage) to an appropriate method and emits a method-matched plan skeleton (objective, participant criteria, guide structure, success criteria). Redirects live A\u002FB to `product-team\u002Fexperiment-designer`.\n2. `saturation_planner.py` — Method-based sample guidance with an explicit **confidence label**: Nielsen problem-discovery (5\u002Fsegment), Guest et al. thematic saturation (~12), and evaluative coverage. Never claims a prevalence rate from a small-n usability test.\n3. `insight_synthesizer.py` — Clusters coded observations by tag, counts distinct participants, ranks by cross-participant recurrence, and flags any candidate below the source threshold as an **ANECDOTE**, never promoting it to an insight.\n\n## When to use\n\nInvoke this skill when:\n\n- You are planning a study and need the method to match the goal (generative vs evaluative vs validation).\n- You need a defensible sample size \u002F saturation rationale with a stated confidence.\n- You have raw coded observations and need to synthesize insights without over-claiming.\n- You are setting up or auditing a research repository and need the insight-vs-observation discipline.\n\n**Do NOT use this skill to**: generate personas \u002F journey maps (use `product-team\u002Fux-researcher-designer`), plan a discovery sprint or validate an opportunity (use `product-team\u002Fproduct-discovery`), design or analyze a live product A\u002FB experiment (use `product-team\u002Fexperiment-designer`), or do market sizing \u002F surveys (use the `market-research` sibling).\n\n## Workflow\n\n1. **Frame the study** — Fill `assets\u002Fresearch_plan_template.md` (research questions, method rationale, participant criteria, analysis plan, repository tagging scheme).\n2. **Pick the method** — Run `study_designer.py --goal {discovery|evaluative|validation} --stage {concept|prototype|beta|live} --profile {b2b-saas|consumer-app|enterprise|marketplace|hardware|platform}`. Honor the redirect if it routes to experiment-designer.\n3. **Size it** — Run `saturation_planner.py --method {usability|thematic|evaluative-coverage} --segments N`. Record the confidence label and limits.\n4. **Synthesize** — After fielding, code observations and run `insight_synthesizer.py --input observations.json --min-sources 3`. Treat ANECDOTE-flagged clusters as signals to probe, not findings to ship.\n5. **File in the repository** — Tag insights to the atomic schema at synthesis time, with their evidence and confidence.\n\n## Scripts\n\n| Script | Purpose | Profiles |\n|---|---|---|\n| `scripts\u002Fstudy_designer.py` | (goal × stage) → method + plan skeleton | b2b-saas, consumer-app, enterprise, marketplace, hardware, platform |\n| `scripts\u002Fsaturation_planner.py` | Method-based sample guidance + confidence | n\u002Fa (method-driven) |\n| `scripts\u002Finsight_synthesizer.py` | Cluster observations, flag anecdotes | n\u002Fa (evidence-driven) |\n\nAll three: stdlib-only, `--help`, `--sample`, `--output {human,json}`.\n\n## Onboarding & customization\n\nRun the onboarding questionnaire **once before you start** — it captures your defaults so every tool in this skill is pre-configured. Customization is the point: the answers actually change tool behavior (e.g. the insight source-threshold).\n\n```bash\npython3 scripts\u002Fonboard.py            # interactive (also: --defaults, --set key=value, --reset)\npython3 scripts\u002Fonboard.py --show     # see the questions + current effective config\n```\n\nAnswers are saved to `~\u002F.config\u002Fresearch-ops\u002Fproduct-research.json` (global) or `.\u002F.research-ops\u002Fproduct-research.json` (`--scope project`) and are read automatically by `config_loader.py`. They set the default product **profile**, the **insight source-threshold** (how many independent participants make a finding an insight, not an anecdote), the default **saturation method**, and the **high-stakes** flag. CLI flags always override saved config; `RESEARCH_OPS_NO_CONFIG=1` ignores it.\n\n**The four questions:** product profile · insight source-threshold · saturation method · high-stakes flag.\n\n## Optimize with autoresearch (opt-in)\n\nThis skill ships an **isolated, opt-in** bridge to `engineering\u002Fautoresearch-agent`. Only when you ask to \"optimize the synthesis\" \u002F \"run a loop\" does an autoresearch experiment iteratively refine the coding\u002Fclustering of a fixed evidence set so more cross-participant patterns surface. `scripts\u002Far_evaluator.py` is the ground-truth evaluator; it prints `validated_insights: \u003Cint>` (higher is better). It optimizes the **coding**, never fabricates evidence.\n\n```bash\n\u002Far:setup --domain custom --name insight-synthesis \\\n  --target observations.json \\\n  --eval \"python3 ar_evaluator.py --target observations.json\" \\\n  --metric validated_insights --direction higher\n\u002Far:loop custom\u002Finsight-synthesis\n```\n\nIsolated: no hard dependency — autoresearch runs only on demand, and the loop edits `observations.json`, never the evaluator.\n\n## References\n\n- `references\u002Fresearch_methods_canon.md` — Portigal *Interviewing Users*; Christensen\u002FUlwick JTBD; Rohrer's UX-research methods landscape (NN\u002Fg); Sauro & Lewis *Quantifying the User Experience*; Goodman\u002FKuniavsky.\n- `references\u002Fsampling_and_saturation.md` — Nielsen \"test with 5 users\"; Guest, Bunce & Johnson saturation; Faulkner on more-than-5; Sauro usability sample size; Braun & Clarke thematic analysis.\n- `references\u002Frepository_and_synthesis.md` — ResearchOps \u002F atomic research (Tomer Sharon \"Polaris\"); insight-vs-observation discipline; repository governance; affinity mapping; democratization guardrails.\n\n## Assumptions\n\n- Method selection assumes you can name the goal honestly; if the goal is fuzzy, grill it first (the goal drives everything).\n- Saturation guidance is method-based, not a power calculation — usability tests find problems, not prevalence rates.\n- The synthesizer counts evidence you provide; coding quality is upstream of it. Garbage tags → garbage clusters.\n- The insight threshold (`--min-sources`) defaults to 3; raise it for high-stakes or heterogeneous populations.\n\n## Anti-patterns\n\n- **Mismatching method to goal.** A usability test cannot discover unmet needs; an interview cannot measure task success.\n- **Reporting usability problems as percentages.** Small-n tests surface problems, not population rates.\n- **Promoting an anecdote to an insight.** One participant is a signal to probe, not a finding.\n- **Framing interview questions as feature reactions.** Probe the job-to-be-done and recent real behavior, not hypothetical opinions.\n- **Synthesizing without a repository scheme.** Tag at synthesis time, or insights rot unfindable.\n\n## Distinct from\n\n| Neighbor | Scope | Difference |\n|---|---|---|\n| `product-team\u002Fux-researcher-designer` | Personas, journey maps, usability frameworks tied to design output | That produces **artifacts**; this is **method + repository discipline** |\n| `product-team\u002Fproduct-discovery` | Opportunity validation, discovery-sprint planning | That plans **discovery sprints**; this designs and synthesizes the **research** |\n| `product-team\u002Fexperiment-designer` | Live product A\u002FB hypothesis + sample size | That runs **live experiments**; this runs **qualitative\u002Fevaluative research** |\n| `market-research` (sibling) | Market sizing, surveys, segmentation | That studies **the market**; this studies **users** |\n\n## Quick examples\n\n```bash\npython3 scripts\u002Fstudy_designer.py --sample\npython3 scripts\u002Fsaturation_planner.py --method thematic --segments 3\npython3 scripts\u002Finsight_synthesizer.py --sample --min-sources 3\n```\n\nThe synthesizer sample correctly promotes \"import-confusion\" (3 independent participants) to INSIGHT and flags \"wants-slack\" (1 participant) as an ANECDOTE.\n\n## Forcing-question library (Matt Pocock grill discipline)\n\nWalked one at a time by `\u002Fcs:grill-research-ops` or the orchestrator. Recommended answer + canon citation per question. Never bundled.\n\n1. **\"Is this study generative (discover problems) or evaluative (test a solution)?\"**\n   Recommended: name it first — the method follows from the goal.\n   Canon: Rohrer, *When to Use Which User-Experience Research Methods* (NN\u002Fg).\n\n2. **\"What's your sample size and saturation rationale — and at what confidence?\"**\n   Recommended: method-based n (5\u002Fsegment usability; ~12 for thematic saturation), state the confidence.\n   Canon: Nielsen; Guest, Bunce & Johnson (2006); Faulkner (2003).\n\n3. **\"How many independent participants support each insight — or is it a single-source anecdote?\"**\n   Recommended: require recurrence across ≥3 sources before calling it an insight; flag singletons.\n   Canon: atomic research \u002F ResearchOps; Braun & Clarke thematic analysis.\n\n4. **\"Are your interview \u002F usability tasks framed as outcomes (jobs) or as feature reactions?\"**\n   Recommended: frame around the job-to-be-done and recent real behavior, not hypothetical opinion.\n   Canon: Christensen\u002FUlwick Jobs-to-be-Done; Portigal *Interviewing Users*.\n\n5. **\"Where does this land in the repository, and how is it tagged for reuse?\"**\n   Recommended: tag to the atomic schema at synthesis time, not later.\n   Canon: Tomer Sharon, *Polaris* \u002F ResearchOps repository practice.\n\nWalk depth-first. Lock 1-2 before opening 3-5. After all are answered, invoke `study_designer.py` → `saturation_planner.py` → (after fielding) `insight_synthesizer.py`.\n",{"name":5,"tags":24,"author":32,"license":15,"version":33,"description":7,"compatible_tools":34},[25,5,26,27,28,29,30,31],"research-ops","ux-research","jtbd","usability","saturation","insight-synthesis","research-repository","claude-code-skills","2.9.0",[35,36,37,38,39,40],"claude-code","codex-cli","cursor","antigravity","opencode","gemini-cli","main","229636be8dd3adf33e35a2aa95b85dc022251d6b",".agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent","https:\u002F\u002Fgithub.com\u002FPrudhviraj101","B.Tech CSE (AI\u002FML) Student | Building practical software with AI 🚀 | AI\u002FML Developer | Building AI agents, intelligent automation & real-world software ","2026-10-02 21:19:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Prudhviraj101\u002FX_Agent --skill product-research",{"tool":54,"command":55},"bunx","bunx skills add Prudhviraj101\u002FX_Agent --skill product-research",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Prudhviraj101\u002FX_Agent --skill product-research","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002FSKILL.md",true,[62,68,74,78,82,88,92,96,100,104],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Fresearch_plan_template.md","ASSET","资产文件",1546,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fassets\u002Fresearch_plan_template.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Frepository_and_synthesis.md","REFERENCE","参考文档",2626,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Freferences\u002Frepository_and_synthesis.md",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fresearch_methods_canon.md",2607,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Freferences\u002Fresearch_methods_canon.md",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fsampling_and_saturation.md",2536,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Freferences\u002Fsampling_and_saturation.md",{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Far_evaluator.py","SCRIPT","脚本",2618,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Far_evaluator.py",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fconfig_loader.py",3823,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Fconfig_loader.py",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"scripts\u002Finsight_synthesizer.py",4929,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Finsight_synthesizer.py",{"path":97,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":98,"sourceHtmlUrl":99},"scripts\u002Fonboard.py",4320,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Fonboard.py",{"path":101,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fsaturation_planner.py",5919,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Fsaturation_planner.py",{"path":105,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fstudy_designer.py",6534,"https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Falirezarezvani\u002Fresearch-ops__product-research\u002Fscripts\u002Fstudy_designer.py",[109,118,126,134,141,149],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7DQMKNKM6F5G21PPJNW3HR5","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7DQMF21V9VHCTVS8H5JFNJM","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7DQM8HREQ0DN1HV12K0W3VT","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7DQM5J7B71CQ8EVHBXCCCN2","systematic-planning","Formulate crisp, executable multi-phase implementation plans for non-trivial features, refactors, and architectural migrations. Use before writing code on any task with multiple files, uncertain requirements, or breaking changes.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsystematic-planning\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":19},"01M7DQKG6WREWGRRCKHCJS96Y1","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fslack-gif-creator\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":113,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":156,"publishedAt":19},"01M7DQJY7AN1XCX6G3ACA5K4JH","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FPrudhviraj101\u002FX_Agent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[]]