[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSQTBWAZCF09RQJ0158QCE":3,"skill-same:01M6GSQTBWAZCF09RQJ0158QCE":101},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6GSQTBWAZCF09RQJ0158QCE","create-skill",null,"Create or revise portable agent skills with clear triggers, focused instructions, and self-contained resources. Use when creating, modifying, refactoring, or deduplicating a skill or its SKILL.md, or authoring skill evaluations and benchmarks.","japurcell\u002Fskills","japurcell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10947458?v=4","01M6GSJK1YAG95R6VHF47V30KY","Adam Purcell","01M6GSJK6817NVR5FVDMFFNJ6H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"create","create skill","with","self","resources","instructions","refactoring","clear","triggers","authoring","use","revise","benchmarks","self-contained","portable","when","2026-11-10 10:12:30",false,"---\nname: create-skill\ndescription: Create or revise portable agent skills with clear triggers, focused instructions, and self-contained resources. Use when creating, modifying, refactoring, or deduplicating a skill or its SKILL.md, or authoring skill evaluations and benchmarks.\n---\n\n# Create Skill\n\n## Core Principles\n\n### Concise is key\n\nThe context window is a public good. A Skill shares the context window with everything else an agent needs, including:\n\n- The system prompt\n- Conversation history\n- Other Skills’ metadata\n- The user request\n\nBeing concise in SKILL.md matters: once an agent loads it, every token competes with conversation history and other context. So keep SKILL.md and its associated resources as concise as possible while preserving intended behavior.\n\n**Default assumption**: The agent is already very smart\n\nOnly add context the agent doesn’t already have. Challenge each piece of information:\n\n- “Does the agent really need this explanation?”\n- “Can I assume the agent has this information?”\n- “Does this paragraph justify its token cost?”\n\n## Workflow\n\n1. **Scope the request**\n   - Identify the authoritative skill source and the requested write boundary. Read the target project's applicable instructions and conventions.\n   - For a new skill, match the frontmatter `name` to the bundle directory. For a revision, preserve both names unless the user requests a rename.\n   - Search available skills for near-duplicate names or overlapping descriptions. Refine a matching skill instead of creating a shadow skill; explain the choice.\n\n2. **Activate authoring guidance**\n   - Activate the `skill-creator` skill for the authoring and iteration workflow.\n   - When drafting or changing agent-facing guidance, activate the `writing-for-agents` skill. Skip it when the change is confined to evaluation fixtures or graders.\n\n3. **Draft or revise the skill**\n   - Before pruning or restructuring, map every behavioral obligation to its replacement. Preserve explicit exclusions, conditions, approval requirements, and actionable task verification.\n   - Write invocation instructions as “activate the `\u003Cname>` skill” or “activate the `\u003Cname>` and `\u003Cname>` skills”, including worker instructions.\n   - Retain an existing `disable-model-invocation: true` unless a human explicitly approves removing it. If a validator rejects the field, check its allowlist against the target host's documented support and report the mismatch.\n   - Consult the [Claude Code frontmatter reference](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fskills#frontmatter-reference) when choosing invocation controls and argument hints. Use documented field names and account for differences in other target hosts. Additionally, include `arguments`, `allowed-tools`, `disallowed-tools`, `compatibility` and any other helpful fields when known.\n   - When adding or revising an `argument-hint`, read [argument hints](references\u002Fargument-hints.md) for invocation syntax and YAML quoting.\n   - Keep the description trigger-oriented: state what the skill does and clear `Use when ...` conditions. Keep workflow steps in the body.\n   - Keep the body under 200 lines. Keep references one level deep, preferably in an immediate reference directory; link directly from SKILL.md with a loading condition and read needed references completely. References longer than 100 lines MUST start with a table of contents.\n   - Keep resources self-contained within the bundle. Refer to other skills through activation language, and derive target-project details from its applicable instructions instead of linking to the author's repository documents.\n   - Keep a skill's own maintenance and evaluation instructions in README.md files. When writing or running evaluations and benchmarks is the skill's task, keep that procedure in its runtime instructions and bundled references.\n   - Follow the [effective-skills checklist](https:\u002F\u002Fplatform.claude.com\u002Fdocs\u002Fen\u002Fagents-and-tools\u002Fagent-skills\u002Fbest-practices#checklist-for-effective-skills). Spell out exact commands and paths when required by the skill's task.\n   - **Extract deterministic logic into skill-bundled scripts when it would otherwise be rewritten repeatedly or when a script materially improves reliability.** Reuse existing tools and commands directly when they already meet the task's needs. Scripts can run without loading their source into context, reducing context use and repeated inference. Follow CLI design best practices, provide actionable errors and clear usage documentation, and document required packages and verify their availability.\n\n4. **Write and run evaluations**\n   - Add or update `evals\u002Fevals.json` with at least three realistic scenarios covering creation, modification, and a negative or duplicate-avoidance case.\n   - Use deterministic assertions and a grader when the output can be checked objectively. Preserve scenario-specific conditions and malformed\u002Fmissing-input cases.\n   - Benchmark new skills against `without_skill`; compare modified skills against an explicit `old_skill` snapshot. Use a fresh iteration and preserve earlier valid failures.\n   - Read [evaluation validation and evidence](references\u002Fvalidation.md) when writing scenarios or graders, running evaluations, or interpreting benchmarks.\n   - Use the target project's existing validation tools and maintained skill's acceptance scope. Resolve tooling from the available skill installation rather than assuming the author's checkout layout.\n\n5. **Review the result**\n   - Compress changed passages before finalizing. Remove repetition and explanation that adds no behavioral guidance; preserve every obligation, condition, exception, and safeguard.\n   - Check that each runtime reference resolves within the bundle and has a distinct loading trigger.\n   - Confirm that another project can use the skill without this repository's documents or checkout layout.\n   - Preserve unrelated content and report the changed source, verification performed, and any unresolved limits.\n","# Create Skill\n\n## Core Principles\n\n### Concise is key\n\nThe context window is a public good. A Skill shares the context window with everything else an agent needs, including:\n\n- The system prompt\n- Conversation history\n- Other Skills’ metadata\n- The user request\n\nBeing concise in SKILL.md matters: once an agent loads it, every token competes with conversation history and other context. So keep SKILL.md and its associated resources as concise as possible while preserving intended behavior.\n\n**Default assumption**: The agent is already very smart\n\nOnly add context the agent doesn’t already have. Challenge each piece of information:\n\n- “Does the agent really need this explanation?”\n- “Can I assume the agent has this information?”\n- “Does this paragraph justify its token cost?”\n\n## Workflow\n\n1. **Scope the request**\n   - Identify the authoritative skill source and the requested write boundary. Read the target project's applicable instructions and conventions.\n   - For a new skill, match the frontmatter `name` to the bundle directory. For a revision, preserve both names unless the user requests a rename.\n   - Search available skills for near-duplicate names or overlapping descriptions. Refine a matching skill instead of creating a shadow skill; explain the choice.\n\n2. **Activate authoring guidance**\n   - Activate the `skill-creator` skill for the authoring and iteration workflow.\n   - When drafting or changing agent-facing guidance, activate the `writing-for-agents` skill. Skip it when the change is confined to evaluation fixtures or graders.\n\n3. **Draft or revise the skill**\n   - Before pruning or restructuring, map every behavioral obligation to its replacement. Preserve explicit exclusions, conditions, approval requirements, and actionable task verification.\n   - Write invocation instructions as “activate the `\u003Cname>` skill” or “activate the `\u003Cname>` and `\u003Cname>` skills”, including worker instructions.\n   - Retain an existing `disable-model-invocation: true` unless a human explicitly approves removing it. If a validator rejects the field, check its allowlist against the target host's documented support and report the mismatch.\n   - Consult the [Claude Code frontmatter reference](https:\u002F\u002Fcode.claude.com\u002Fdocs\u002Fen\u002Fskills#frontmatter-reference) when choosing invocation controls and argument hints. Use documented field names and account for differences in other target hosts. Additionally, include `arguments`, `allowed-tools`, `disallowed-tools`, `compatibility` and any other helpful fields when known.\n   - When adding or revising an `argument-hint`, read [argument hints](references\u002Fargument-hints.md) for invocation syntax and YAML quoting.\n   - Keep the description trigger-oriented: state what the skill does and clear `Use when ...` conditions. Keep workflow steps in the body.\n   - Keep the body under 200 lines. Keep references one level deep, preferably in an immediate reference directory; link directly from SKILL.md with a loading condition and read needed references completely. References longer than 100 lines MUST start with a table of contents.\n   - Keep resources self-contained within the bundle. Refer to other skills through activation language, and derive target-project details from its applicable instructions instead of linking to the author's repository documents.\n   - Keep a skill's own maintenance and evaluation instructions in README.md files. When writing or running evaluations and benchmarks is the skill's task, keep that procedure in its runtime instructions and bundled references.\n   - Follow the [effective-skills checklist](https:\u002F\u002Fplatform.claude.com\u002Fdocs\u002Fen\u002Fagents-and-tools\u002Fagent-skills\u002Fbest-practices#checklist-for-effective-skills). Spell out exact commands and paths when required by the skill's task.\n   - **Extract deterministic logic into skill-bundled scripts when it would otherwise be rewritten repeatedly or when a script materially improves reliability.** Reuse existing tools and commands directly when they already meet the task's needs. Scripts can run without loading their source into context, reducing context use and repeated inference. Follow CLI design best practices, provide actionable errors and clear usage documentation, and document required packages and verify their availability.\n\n4. **Write and run evaluations**\n   - Add or update `evals\u002Fevals.json` with at least three realistic scenarios covering creation, modification, and a negative or duplicate-avoidance case.\n   - Use deterministic assertions and a grader when the output can be checked objectively. Preserve scenario-specific conditions and malformed\u002Fmissing-input cases.\n   - Benchmark new skills against `without_skill`; compare modified skills against an explicit `old_skill` snapshot. Use a fresh iteration and preserve earlier valid failures.\n   - Read [evaluation validation and evidence](references\u002Fvalidation.md) when writing scenarios or graders, running evaluations, or interpreting benchmarks.\n   - Use the target project's existing validation tools and maintained skill's acceptance scope. Resolve tooling from the available skill installation rather than assuming the author's checkout layout.\n\n5. **Review the result**\n   - Compress changed passages before finalizing. Remove repetition and explanation that adds no behavioral guidance; preserve every obligation, condition, exception, and safeguard.\n   - Check that each runtime reference resolves within the bundle and has a distinct loading trigger.\n   - Confirm that another project can use the skill without this repository's documents or checkout layout.\n   - Preserve unrelated content and report the changed source, verification performed, and any unresolved limits.\n",{"name":5,"description":7},"main","8a912f4cf9bf915fb92e5b29671f0ed22555bcb7","skills\u002Fdefault\u002Fcreate-skill","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjapurcell","2026-11-11 08:59:34",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add japurcell\u002Fskills --skill create-skill",{"tool":57,"command":58},"bunx","bunx skills add japurcell\u002Fskills --skill create-skill",{"tool":60,"command":61},"pnpm","pnpm dlx skills add japurcell\u002Fskills --skill create-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002FSKILL.md",true,[65,71,75,79,85,89,93,97],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"evals\u002Fevals.json","REFERENCE","参考文档",4689,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Fevals\u002Fevals.json",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Ffiles\u002Fplan-maker-request.md",662,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Fevals\u002Ffiles\u002Fplan-maker-request.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Ffiles\u002Frelease-notes-brief.md",886,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Fevals\u002Ffiles\u002Frelease-notes-brief.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fgrade_benchmark.py","SCRIPT","脚本",15004,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Fevals\u002Fgrade_benchmark.py",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"evals\u002Ftest_grade_benchmark.py",3814,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Fevals\u002Ftest_grade_benchmark.py",{"path":90,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":91,"sourceHtmlUrl":92},"README.md",5534,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002FREADME.md",{"path":94,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fargument-hints.md",1746,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Freferences\u002Fargument-hints.md",{"path":98,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fvalidation.md",3072,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcreate-skill\u002Freferences\u002Fvalidation.md",[102,130,152,181,201,222],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":113,"publishedAt":40},"01M6PT0ZTYCN4DHK3SXWS79WSY","spec-create","Create or revise a portable behavioral SPEC for a feature or whole product. Use when specifying a new idea, documenting an existing system for reimplementation, or defining a change while preserving compatibility. Implementation planning is a separate task.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fspec-create\u002FSKILL.md",[108],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,114,115,116,117,118,119,34,120,121,122,123,124,125,35,126,127,128,129],"spec","spec create","feature","planning","for","system","Existing","task","output","change","product","implementation","compatibility","behavioral","idea","path",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":40},"01M6GSVHQ4MY4R4SMS8RY6324Q","prd-ralph","Complete at most one eligible unfinished PRD task, verify it, log progress, and optionally create one scoped commit.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fprd-ralph\u002FSKILL.md",[136],{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},[138,139,140,24,141,142,143,144,145,146,121,147,148,149,150,151,129],"prd ralph","ralph","prd","progress","verify","at","complete","commit","it","log","scoped","false","file","id",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":40},"01M6GSYMGHE2FEGEFKD926EJH8","fsdp-style-guide","Mandatory for all UI\u002FUX design, implementation, review, audit, or visual regression tasks. Always use for any work that affects user-facing appearance, behavior, accessibility, branding, layout, navigation, forms, dialogs, alerts, tables, or visual design.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Ffsdp-style-guide\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000032","设计师",[162,163,164,165,166,167,168,169,34,170,171,172,173,174,175,176,177,178,179,180,118],"fsdp style guide","style guide","FSDP","style","guide","visual regression","regression","design","visual","tasks","review","visual design","alerts","work","branding","layout","audit","ux","behavior",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":40},"01M6GSYHEQARNM7WN0RJA7K7T2","agency-priorities","Provide self-contained USDA strategic goals and Forest Service priorities for agency briefings, proposals, and work-plan alignment. Use when explaining agency direction or evaluating how a project contributes to USDA and Forest Service priorities.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Fagency-priorities\u002FSKILL.md",[],[188,189,190,27,191,175,192,193,194,195,196,197,198,199,34,118,39,200,37],"agency priorities","priorities","agency","alignment","plan","goals","proposals","direction","how","project","strategic","service","briefings",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":40},"01M6GSY9VVN8RSJ5QYM540ZJ1D","accomplishment-report","Create a concise Forest Service executive accomplishment report when all work in an ExecPlan is completed, or update its existing report. Use at ExecPlan closeout and when asked to report completed work, agency alignment, and estimated AI-assisted versus human-only time and cost savings.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Faccomplishment-report\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000034","行政与办公人员",[211,212,191,213,24,175,214,215,216,217,143,190,218,199,34,219,220,221,120,39],"report","accomplishment report","cost","concise","human","time","update","only","closeout","savings","execplan",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":234,"publishedAt":40},"01M6GSY7J8ZMCE319P8Y6JZ432","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fwriting-for-agents\u002FSKILL.md",[228,231],{"categoryNo":229,"categoryName":230,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":232,"categoryName":233,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000036","内容创作者",[235,236,118,34,237,238,39],"writing","writing for agents","documents","editing"]