[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D6DDJMPNF8V9HDD2Y01S97":3,"skill-same:01M6D6DDJMPNF8V9HDD2Y01S97":77},{"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":23,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6D6DDJMPNF8V9HDD2Y01S97","jtbd-positioning",null,"Jobs-to-be-Done positioning analysis — identify primary job, map functional\u002Fsocial\u002Femotional dimensions, position around job outcome","GeorgeQLe\u002Fagentic-skills","GeorgeQLe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21134126?v=4","01M6D2JP418S0VGJGF8M93EC3H","George Le","01M6D2JPBAKYD82TA5FS6HKQ3D",1,"MIT","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Fframeworks\u002Fjtbd-positioning\u002Farchive\u002Fv0.0\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35],"jtbd","positioning","jtbd positioning","research","analysis","outcome","v0","jobs","social","dimensions","done","map","2026-11-10 10:12:30",false,"---\nname: jtbd-positioning\ndescription: Jobs-to-be-Done positioning analysis — identify primary job, map functional\u002Fsocial\u002Femotional dimensions, position around job outcome\ntype: research\nversion: v0.0\ninvocation: sub-skill\nparent: positioning\n---\n\n## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `\u002Fpack install \u003Cpack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.\n\n# JTBD Positioning — Jobs-to-be-Done Analysis\n\n## Report-First Approval Gate\n\nDefault to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.\n\nDo not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write\u002Fupdate\u002Ffix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research\u002Freport writes.\n\nWhen stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.\n\n## Prerequisites\n\n- **Hard**: `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`) must exist. If not, tell the user to run `\u002Ficp` first and stop.\n- **Hard**: `research\u002Fcompetitive-analysis.md` (or `research\u002F{slug}\u002Fcompetitive-analysis.md`) must exist. If not, tell the user to run `\u002Fcompetitive-analysis` first and stop.\n- **Soft**: `research\u002Fjourney-map.md` (or `research\u002F{slug}\u002Fjourney-map.md`) — recommended for richer job context but not blocking.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Load Context\n\n- Read `research\u002Ficp.md` — ICP segments, pain points, value props, trigger events\n- Read `research\u002Fcompetitive-analysis.md` — competitor landscape, what alternatives offer\n- Read `research\u002Fjourney-map.md` if it exists — where value is delivered, the aha moment, switching triggers\n- Read CLAUDE.md, README, and key source files for product context\n\n### 2. Identify the Primary Job\n\nDetermine the primary \"job\" the target customer is hiring this product to do. A job is not a feature or a task — it is a higher-level progress the customer is trying to make in their life or work.\n\nFormat as a job statement: \"When [situation], I want to [motivation], so I can [expected outcome].\"\n\nGround the job in ICP evidence:\n- What pain points from the ICP map to unfinished or poorly-served jobs?\n- What trigger events cause the customer to \"fire\" their current solution and \"hire\" a new one?\n- What does the journey map reveal about what the customer is truly trying to accomplish?\n\n### 3. Map Functional Dimensions\n\nWhat the job accomplishes practically:\n- What tasks does the job complete?\n- What outputs does the customer expect?\n- What quality standards define \"done well\"?\n- How does the customer measure functional success?\n\n### 4. Map Social Dimensions\n\nHow doing the job affects how others perceive the customer:\n- How does the customer want to be seen by peers, managers, or customers?\n- What professional identity does completing this job reinforce?\n- What status or credibility does the customer gain?\n- What social risks exist if the job is done poorly?\n\n### 5. Map Emotional Dimensions\n\nHow doing the job makes the customer feel:\n- What frustrations does the customer experience with current solutions?\n- What confidence or relief does successful completion bring?\n- What anxiety or uncertainty exists during the process?\n- What delight or satisfaction signals \"done well\"?\n\n### 6. Identify Desired Outcome State\n\nDefine what \"done well\" looks like from the customer's perspective:\n- Functional success criteria\n- Social success criteria\n- Emotional success criteria\n- What does the customer's world look like after the job is completed successfully?\n\n### 7. Position Around Job Outcome\n\nDetermine how the product delivers the desired outcome better than alternatives:\n- Which dimensions (functional\u002Fsocial\u002Femotional) does the product win on?\n- Where do alternatives fall short on delivering the full outcome?\n- What is the product's unique advantage in delivering \"done well\"?\n- How should the product be framed to make the job-outcome connection obvious?\n\n### 8. Validate with User\n\nUse AskUserQuestion to present findings and validate:\n- \"Is this the right job? Are there jobs I've missed or overweighted?\"\n- Present the job statement, dimensional map, and outcome positioning\n- Ask whether the functional\u002Fsocial\u002Femotional weighting feels accurate\n\n## Output\n\n### `research\u002Fpositioning-jtbd.md` (or `research\u002F{slug}\u002Fpositioning-jtbd.md`)\n\n```markdown\n# JTBD Positioning Analysis\n\n> Based on: research\u002Ficp.md, research\u002Fcompetitive-analysis.md[, research\u002Fjourney-map.md]\n> Date: [current date]\n> Methodology: Jobs-to-be-Done\n\n## Job Statement\n\nWhen [situation], I want to [motivation], so I can [expected outcome].\n\n## Functional Dimensions\n\n| Dimension | Description | Current Solution Performance | Evidence |\n|-----------|-------------|------------------------------|----------|\n| [dimension] | [what it accomplishes] | [how current solutions perform] | [source] |\n\n## Social Dimensions\n\n| Dimension | Description | Importance | Evidence |\n|-----------|-------------|------------|----------|\n| [dimension] | [how it affects perception] | High\u002FMedium\u002FLow | [source] |\n\n## Emotional Dimensions\n\n| Dimension | Description | Current Pain Level | Evidence |\n|-----------|-------------|-------------------|----------|\n| [dimension] | [how it makes them feel] | High\u002FMedium\u002FLow | [source] |\n\n## Desired Outcome\n\n[Description of what \"done well\" looks like across all dimensions]\n\n### Functional Success\n- [criterion]\n\n### Social Success\n- [criterion]\n\n### Emotional Success\n- [criterion]\n\n## Position\n\n[How the product delivers the desired outcome better than alternatives]\n\n### Winning Dimensions\n| Dimension Type | Specific Dimension | Product Advantage | vs. Alternatives |\n|---------------|-------------------|-------------------|------------------|\n| [Functional\u002FSocial\u002FEmotional] | [dimension] | [advantage] | [how alternatives fall short] |\n\n### Positioning Implication\n[How this job-outcome framing should shape product positioning]\n\n## Evidence Matrix\n\n| Claim | Evidence Source | Evidence Type | Confidence |\n|-------|---------------|---------------|------------|\n| [claim about the job] | [source file\u002Fsection] | Observed\u002FInferred\u002FHypothesized | High\u002FMedium\u002FLow |\n```\n\nCreate the `research\u002F` directory if it doesn't exist.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- **Must ground in ICP evidence.** Jobs must come from observed customer behavior and pain points, not aspirational product vision.\n- **If the job is unclear, surface that as a finding.** Do not force a clean job statement when evidence is ambiguous — document the ambiguity.\n- **One primary job.** There may be related jobs, but identify the single primary job the product is hired for. Secondary jobs can be noted but should not dilute the primary.\n- **Present before writing.** Never write output files until findings have been presented and validated.\n- **Do not overwrite existing `research\u002Fpositioning-jtbd.md`** without asking the user first.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `..\u002FALIGNMENT-PAGE.md`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n","## Pack Availability Guard\n\nBefore telling the user to run a skill from another project-local pack, check `.agents\u002Fproject.json.enabled_packs`. If the target pack is not enabled, recommend `\u002Fpack install \u003Cpack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.\n\n# JTBD Positioning — Jobs-to-be-Done Analysis\n\n## Report-First Approval Gate\n\nDefault to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.\n\nDo not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write\u002Fupdate\u002Ffix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research\u002Freport writes.\n\nWhen stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.\n\n## Prerequisites\n\n- **Hard**: `research\u002Ficp.md` (or `research\u002F{slug}\u002Ficp.md`) must exist. If not, tell the user to run `\u002Ficp` first and stop.\n- **Hard**: `research\u002Fcompetitive-analysis.md` (or `research\u002F{slug}\u002Fcompetitive-analysis.md`) must exist. If not, tell the user to run `\u002Fcompetitive-analysis` first and stop.\n- **Soft**: `research\u002Fjourney-map.md` (or `research\u002F{slug}\u002Fjourney-map.md`) — recommended for richer job context but not blocking.\n\n## Process\n\n### 0. Product-Path Scope Resolution\n\nResolve research scope by product path before using code or app structure as a hint:\n\n1. If `$ARGUMENTS` names a non-archived `research\u002F{slug}\u002F` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product\u002Fapp name, not the ICP, audience, or segment label.\n2. If `$ARGUMENTS` names only `research\u002F_archive\u002F{slug}\u002F` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.\n3. Read `research\u002F.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research\u002F_archive\u002F` from active target selection.\n4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.\n5. If no active manifest target exists, list non-archived product directories under `research\u002F`, excluding `research\u002F_archive\u002F` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.\n6. If no product directories exist, use flat `research\u002F` single-product mode.\n7. Detect monorepo\u002Fapp\u002Fpackage structure only as a secondary hint. Suggest creating a missing `research\u002F{slug}\u002F` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research\u002F{slug}\u002F`.\n\nWhen product path `{slug}` is active, read and write research under `research\u002F{slug}\u002F`, specs under `specs\u002F{slug}\u002F`, and treat top-level `research\u002F*.md` files as flat-mode documents or cross-path summaries.\n\n### 1. Load Context\n\n- Read `research\u002Ficp.md` — ICP segments, pain points, value props, trigger events\n- Read `research\u002Fcompetitive-analysis.md` — competitor landscape, what alternatives offer\n- Read `research\u002Fjourney-map.md` if it exists — where value is delivered, the aha moment, switching triggers\n- Read CLAUDE.md, README, and key source files for product context\n\n### 2. Identify the Primary Job\n\nDetermine the primary \"job\" the target customer is hiring this product to do. A job is not a feature or a task — it is a higher-level progress the customer is trying to make in their life or work.\n\nFormat as a job statement: \"When [situation], I want to [motivation], so I can [expected outcome].\"\n\nGround the job in ICP evidence:\n- What pain points from the ICP map to unfinished or poorly-served jobs?\n- What trigger events cause the customer to \"fire\" their current solution and \"hire\" a new one?\n- What does the journey map reveal about what the customer is truly trying to accomplish?\n\n### 3. Map Functional Dimensions\n\nWhat the job accomplishes practically:\n- What tasks does the job complete?\n- What outputs does the customer expect?\n- What quality standards define \"done well\"?\n- How does the customer measure functional success?\n\n### 4. Map Social Dimensions\n\nHow doing the job affects how others perceive the customer:\n- How does the customer want to be seen by peers, managers, or customers?\n- What professional identity does completing this job reinforce?\n- What status or credibility does the customer gain?\n- What social risks exist if the job is done poorly?\n\n### 5. Map Emotional Dimensions\n\nHow doing the job makes the customer feel:\n- What frustrations does the customer experience with current solutions?\n- What confidence or relief does successful completion bring?\n- What anxiety or uncertainty exists during the process?\n- What delight or satisfaction signals \"done well\"?\n\n### 6. Identify Desired Outcome State\n\nDefine what \"done well\" looks like from the customer's perspective:\n- Functional success criteria\n- Social success criteria\n- Emotional success criteria\n- What does the customer's world look like after the job is completed successfully?\n\n### 7. Position Around Job Outcome\n\nDetermine how the product delivers the desired outcome better than alternatives:\n- Which dimensions (functional\u002Fsocial\u002Femotional) does the product win on?\n- Where do alternatives fall short on delivering the full outcome?\n- What is the product's unique advantage in delivering \"done well\"?\n- How should the product be framed to make the job-outcome connection obvious?\n\n### 8. Validate with User\n\nUse AskUserQuestion to present findings and validate:\n- \"Is this the right job? Are there jobs I've missed or overweighted?\"\n- Present the job statement, dimensional map, and outcome positioning\n- Ask whether the functional\u002Fsocial\u002Femotional weighting feels accurate\n\n## Output\n\n### `research\u002Fpositioning-jtbd.md` (or `research\u002F{slug}\u002Fpositioning-jtbd.md`)\n\n```markdown\n# JTBD Positioning Analysis\n\n> Based on: research\u002Ficp.md, research\u002Fcompetitive-analysis.md[, research\u002Fjourney-map.md]\n> Date: [current date]\n> Methodology: Jobs-to-be-Done\n\n## Job Statement\n\nWhen [situation], I want to [motivation], so I can [expected outcome].\n\n## Functional Dimensions\n\n| Dimension | Description | Current Solution Performance | Evidence |\n|-----------|-------------|------------------------------|----------|\n| [dimension] | [what it accomplishes] | [how current solutions perform] | [source] |\n\n## Social Dimensions\n\n| Dimension | Description | Importance | Evidence |\n|-----------|-------------|------------|----------|\n| [dimension] | [how it affects perception] | High\u002FMedium\u002FLow | [source] |\n\n## Emotional Dimensions\n\n| Dimension | Description | Current Pain Level | Evidence |\n|-----------|-------------|-------------------|----------|\n| [dimension] | [how it makes them feel] | High\u002FMedium\u002FLow | [source] |\n\n## Desired Outcome\n\n[Description of what \"done well\" looks like across all dimensions]\n\n### Functional Success\n- [criterion]\n\n### Social Success\n- [criterion]\n\n### Emotional Success\n- [criterion]\n\n## Position\n\n[How the product delivers the desired outcome better than alternatives]\n\n### Winning Dimensions\n| Dimension Type | Specific Dimension | Product Advantage | vs. Alternatives |\n|---------------|-------------------|-------------------|------------------|\n| [Functional\u002FSocial\u002FEmotional] | [dimension] | [advantage] | [how alternatives fall short] |\n\n### Positioning Implication\n[How this job-outcome framing should shape product positioning]\n\n## Evidence Matrix\n\n| Claim | Evidence Source | Evidence Type | Confidence |\n|-------|---------------|---------------|------------|\n| [claim about the job] | [source file\u002Fsection] | Observed\u002FInferred\u002FHypothesized | High\u002FMedium\u002FLow |\n```\n\nCreate the `research\u002F` directory if it doesn't exist.\n\n## Task Classification\n\nWhen this skill produces follow-up work, file it by execution semantics:\n\n- Immediately actionable implementation or documentation work goes in `tasks\u002Ftodo.md`.\n- Human-only external actions tied to automated steps go in `tasks\u002Fmanual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI\u002FAPI work stay in `tasks\u002Ftodo.md`.\n- One-time condition-gated records, baselines, or future measurements go in `tasks\u002Frecord-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.\n- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks\u002Frecurring-todo.md` with cadence, owner\u002Fagent, next due, evidence path, and escalation conditions.\n- Do not put non-blocking records or recurring obligations in `tasks\u002Ftodo.md` unless they have been explicitly promoted into current execution work.\n\n## Constraints\n\n- **Must ground in ICP evidence.** Jobs must come from observed customer behavior and pain points, not aspirational product vision.\n- **If the job is unclear, surface that as a finding.** Do not force a clean job statement when evidence is ambiguous — document the ambiguity.\n- **One primary job.** There may be related jobs, but identify the single primary job the product is hired for. Secondary jobs can be noted but should not dilute the primary.\n- **Present before writing.** Never write output files until findings have been presented and validated.\n- **Do not overwrite existing `research\u002Fpositioning-jtbd.md`** without asking the user first.\n\n## Alignment Page\n\nWhen this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `..\u002FALIGNMENT-PAGE.md`.\n\n## Default Shipping Contract\n\nFollow the shared shipping contract convention in CLAUDE.md.\n",{"name":5,"type":27,"parent":25,"version":41,"invocation":42,"description":7},"v0.0","sub-skill","master","96e2912af886dd1606b1b97df707715aef062b02","packs\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Fframeworks\u002Fjtbd-positioning\u002Farchive\u002Fv0.0",0,"https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills","https:\u002F\u002Fagentic-skills-blush.vercel.app","https:\u002F\u002Fgithub.com\u002FGeorgeQLe","georgeqle.com","George Le is a futurist and serial tech entrepreneur who wants to work toward a world where humanity is free from robotic tasks.","2026-11-10 04:07:24",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add GeorgeQLe\u002Fagentic-skills --skill jtbd-positioning",{"tool":59,"command":60},"bunx","bunx skills add GeorgeQLe\u002Fagentic-skills --skill jtbd-positioning",{"tool":62,"command":63},"pnpm","pnpm dlx skills add GeorgeQLe\u002Fagentic-skills --skill jtbd-positioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Fpacks\u002Fbusiness-research\u002Fclaude\u002Fpositioning\u002Fframeworks\u002Fjtbd-positioning\u002Farchive\u002Fv0.0\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",102,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fwriting-for-agents\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"SKILL-MECHANICS.md",2629,"https:\u002F\u002Fgithub.com\u002FnicolasLuduena\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fhand\u002Fwriting-for-agents\u002FSKILL-MECHANICS.md",[78,90,100,112,125,136],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":36},"01M6G0NJES15RJKZE6YZ0TSYGF","source-checkout-allowed","Valid source-checkout-only fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fsource-checkout-allowed\u002FSKILL.md",[],[85,86,87,88,30,89],"source checkout allowed","checkout","fixture","only","valid",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":36},"01M6G0NFZ3R1MNB1E3DVTM0WB7","deck-install-valid","Valid deck install fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fdeck-install\u002FSKILL.md",[],[97,98,99,89,87,30],"deck install valid","deck","install",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":36},"01M6G0ND3QZQC4MDZ9NVB97PT2","codex-pack-guard-valid","Valid Codex Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-pack-guard\u002FSKILL.md",[],[107,108,109,89,110,111,87,30],"codex pack guard valid","pack","guard","codex","availability",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":36},"01M6G0NA9YB3NKGZKD3S96JMNB","codex-missing-skill-valid","Valid Codex missing skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-missing-skill-fallback\u002FSKILL.md",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[122,123,89,110,30,124,87],"codex missing skill valid","missing","fallback",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":36},"01M6G0N7PC0EKFD40ZWQAXSAQ9","codex-base-skill-fallback-valid","Valid Codex base skill fallback fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fcodex-base-skill-fallback\u002FSKILL.md",[131],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},[89,110,124,133,134,135,30,87],"base skill","codex base skill fallback valid","base",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":36},"01M6G0N4VRR2YKZQ6N3Y6S2BQA","claude-pack-guard-valid","Valid Claude Pack Availability Guard fixture.","https:\u002F\u002Fgithub.com\u002FGeorgeQLe\u002Fagentic-skills\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-install-routing\u002Fvalid\u002Fclaude-pack-guard\u002FSKILL.md",[],[89,109,108,143,111,30,87],"claude pack guard valid"]