[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSP5T7XGWSJD2G1Z0VD317":3,"skill-same:01M6GSP5T7XGWSJD2G1Z0VD317":119},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":14,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":74},"01M6GSP5T7XGWSJD2G1Z0VD317","code-review",null,"Strict review of a PR, diff, commit range, branch, staged\u002Funstaged changes, or AI patch. Finds only high-confidence issues introduced or exposed by the reviewed change.","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\u002Fcode-review\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"code","review","code review","staged","dispatch","subagent dispatch","changes","subagent","for","reviews","commit","patch","only","true","issues","diff","high","pr","change","branch","2026-11-10 10:12:30",false,"---\nname: code-review\ndescription: Strict review of a PR, diff, commit range, branch, staged\u002Funstaged changes, or AI patch. Finds only high-confidence issues introduced or exposed by the reviewed change.\ncompatibility: Requires subagent dispatch, including for lightweight reviews.\ndisable-model-invocation: true\n---\n\n# Code Review\n\nReview only the requested change. Report only high-confidence, change-linked findings.\n\n## Core rules\n\n- Do not run the review yourself in the main thread. Dispatching subagents preserves your context window from large diff files and runs deep specialist logic.\n- Do not expand scope beyond the requested PR, diff, commit range, branch, or local changes.\n- If the review target is unclear, ask one clarifying question and stop.\n- Do not run builds, tests, linters, typechecks, benchmarks, or broad validation unless asked.\n- Do not report unrelated pre-existing issues unless the change makes them reachable or worse.\n- Do not report style preferences, speculation, generic test\u002Fdoc requests, or issues tooling should catch.\n- Standards findings require an explicit cited repo rule.\n- Keep findings only if they score 80+ under `references\u002Ffalse-positive-rubric.md`.\n- If a required skill, subagent, intake source, or reference file is unavailable, stop and explain.\n\n## Workflow\n\n1. **Setup**\n   Before continuing, ensure the following skills are activated or loaded:\n   - `addy-code-review-and-quality`\n   - `delegate-to-subagents`: delegate tasks to the most suitable subagents\n\n2. **Lock target**\n   - PR: review that PR.\n   - Local: review staged, unstaged, or both exactly as requested.\n   - Fixed point: review against the named branch, commit, or base.\n   - If user says `review since X` and X is not fixed, ask exactly: `Review against what — a branch, a commit, or main?`. Then stop.\n\n3. **Collect intake**\n   - PR: follow `references\u002Fpr-protocol.md`.\n   - Local: collect the requested `git diff --cached`, `git diff`, or both separately.\n   - Fixed point: collect `git diff \u003Ctarget>...HEAD` and `git log \u003Ctarget>..HEAD --oneline`.\n\n4. **Triage large changes**\n   If the change exceeds 1000 changed lines or 15 files, follow `references\u002Flarge-change-triage.md`.\n\n5. **Gather coding standards**\n   - Read relevant repo instructions, standards, ADRs, contribution docs, and configs from repo root and touched-path ancestors.\n   - Prefer snippets over full files.\n   - Skip standards enforced mechanically by tooling unless the change bypasses or weakens that tooling.\n   - Common context files are listed in `references\u002Fstandards-files.md`.\n\n6. **Find spec**\n   - Use PR metadata, linked issues, commits, user-supplied paths, or obvious files under `docs\u002F`, `specs\u002F`, `.scratch\u002F`, `.agents\u002Fscratchpad\u002F**`.\n   - If none exists, record `no spec available` and skip spec compliance review.\n\n7. **Review**\n   Dispatch parallel subagents concurrently in a single turn (do NOT run them sequentially across multiple turns) using available catalog names as the `agent_type`:\n   - `addy-code-reviewer`: correctness, regressions, edge cases, architecture boundaries. The subagent prompt should require activating the `addy-code-review-and-quality` skill.\n   - `addy-security-auditor`: vuln, unsafe data handling, auth\u002Fauthz, injection, secrets, attack surface. The subagent prompt should require activating the `addy-security-and-hardening` skill.\n   - `addy-test-engineer`: inadequate, misleading, or broken tests for changed behavior\n   - `generalist or default`: quality review covering maintainability, standards, code smells, spec compliance if available, and PR-only checks if reviewing a PR. The subagent prompt should require:\n     - `references\u002Fmaintainability-criteria.md`\n     - `references\u002Fcode-smells.md`\n     - explicit repo standards only\n     - spec, if available\n     - `references\u002Fpr-protocol.md`, if reviewing a PR\n\n   For all reviews, you MUST run all four required subagents in parallel (concurrently) within the same response turn to prevent context bloat and speed up execution, unless the user explicitly asks for a lightweight review. If the runtime doesn't allow it, run as many as possible concurrently. For large changes, chunk input per `references\u002Flarge-change-triage.md`.\n\n8. **Each subagent result must include**\n   - role\n   - file and line\n   - issue\n   - why it is introduced, exposed, or made reachable by the change\n   - evidence\n   - practical impact\n   - severity\n   - specific fix\n   - preliminary confidence\n\n9. **Filter false positives with fast-tier subagents**\n   - Apply `references\u002Ffalse-positive-rubric.md`.\n   - Verify each finding against the exact diff hunk.\n   - Keep only findings on changed lines, or unchanged lines directly reached\u002Fexposed by changed hunks with explicit evidence.\n   - Drop findings that rely only on nearby unchanged context.\n   - Keep only findings scoring 80+.\n   - Assign final severity.\n\n10. **Output**\n\n- Use the user’s requested mode.\n- For PR comment or machine-readable output, use `references\u002Foutput-formats.md`.\n- Normal format:\n  - severity\n  - file\u002Fline\n  - issue\n  - impact\n  - suggested fix\n- If no findings survive, say:\n  `No change-linked issues were found.`\n\n## Tone\n\nBe brief, direct, and serious. Do not soften important correctness, security, or maintainability problems.\n\n## Final checklist\n\n- [ ] Prerequisite skills (`addy-code-review-and-quality` and `delegate-to-subagents`) were successfully activated.\n- [ ] Target is fixed or clarified.\n- [ ] PR eligibility was checked, if applicable.\n- [ ] Relevant context and standards were reviewed.\n- [ ] Spec review ran or `no spec available` was recorded.\n- [ ] Required catalog subagents ran for correctness, security, tests, and general quality.\n- [ ] Large-change triage ran if thresholds were exceeded.\n- [ ] Every kept finding is change-linked and verified against an exact diff hunk.\n- [ ] Standards findings cite explicit repo rules.\n- [ ] False-positive score is 80+ for every kept finding.\n- [ ] Findings cite code, standards, specs, or diff evidence as applicable.\n- [ ] Output matches the requested mode.\n","# Code Review\n\nReview only the requested change. Report only high-confidence, change-linked findings.\n\n## Core rules\n\n- Do not run the review yourself in the main thread. Dispatching subagents preserves your context window from large diff files and runs deep specialist logic.\n- Do not expand scope beyond the requested PR, diff, commit range, branch, or local changes.\n- If the review target is unclear, ask one clarifying question and stop.\n- Do not run builds, tests, linters, typechecks, benchmarks, or broad validation unless asked.\n- Do not report unrelated pre-existing issues unless the change makes them reachable or worse.\n- Do not report style preferences, speculation, generic test\u002Fdoc requests, or issues tooling should catch.\n- Standards findings require an explicit cited repo rule.\n- Keep findings only if they score 80+ under `references\u002Ffalse-positive-rubric.md`.\n- If a required skill, subagent, intake source, or reference file is unavailable, stop and explain.\n\n## Workflow\n\n1. **Setup**\n   Before continuing, ensure the following skills are activated or loaded:\n   - `addy-code-review-and-quality`\n   - `delegate-to-subagents`: delegate tasks to the most suitable subagents\n\n2. **Lock target**\n   - PR: review that PR.\n   - Local: review staged, unstaged, or both exactly as requested.\n   - Fixed point: review against the named branch, commit, or base.\n   - If user says `review since X` and X is not fixed, ask exactly: `Review against what — a branch, a commit, or main?`. Then stop.\n\n3. **Collect intake**\n   - PR: follow `references\u002Fpr-protocol.md`.\n   - Local: collect the requested `git diff --cached`, `git diff`, or both separately.\n   - Fixed point: collect `git diff \u003Ctarget>...HEAD` and `git log \u003Ctarget>..HEAD --oneline`.\n\n4. **Triage large changes**\n   If the change exceeds 1000 changed lines or 15 files, follow `references\u002Flarge-change-triage.md`.\n\n5. **Gather coding standards**\n   - Read relevant repo instructions, standards, ADRs, contribution docs, and configs from repo root and touched-path ancestors.\n   - Prefer snippets over full files.\n   - Skip standards enforced mechanically by tooling unless the change bypasses or weakens that tooling.\n   - Common context files are listed in `references\u002Fstandards-files.md`.\n\n6. **Find spec**\n   - Use PR metadata, linked issues, commits, user-supplied paths, or obvious files under `docs\u002F`, `specs\u002F`, `.scratch\u002F`, `.agents\u002Fscratchpad\u002F**`.\n   - If none exists, record `no spec available` and skip spec compliance review.\n\n7. **Review**\n   Dispatch parallel subagents concurrently in a single turn (do NOT run them sequentially across multiple turns) using available catalog names as the `agent_type`:\n   - `addy-code-reviewer`: correctness, regressions, edge cases, architecture boundaries. The subagent prompt should require activating the `addy-code-review-and-quality` skill.\n   - `addy-security-auditor`: vuln, unsafe data handling, auth\u002Fauthz, injection, secrets, attack surface. The subagent prompt should require activating the `addy-security-and-hardening` skill.\n   - `addy-test-engineer`: inadequate, misleading, or broken tests for changed behavior\n   - `generalist or default`: quality review covering maintainability, standards, code smells, spec compliance if available, and PR-only checks if reviewing a PR. The subagent prompt should require:\n     - `references\u002Fmaintainability-criteria.md`\n     - `references\u002Fcode-smells.md`\n     - explicit repo standards only\n     - spec, if available\n     - `references\u002Fpr-protocol.md`, if reviewing a PR\n\n   For all reviews, you MUST run all four required subagents in parallel (concurrently) within the same response turn to prevent context bloat and speed up execution, unless the user explicitly asks for a lightweight review. If the runtime doesn't allow it, run as many as possible concurrently. For large changes, chunk input per `references\u002Flarge-change-triage.md`.\n\n8. **Each subagent result must include**\n   - role\n   - file and line\n   - issue\n   - why it is introduced, exposed, or made reachable by the change\n   - evidence\n   - practical impact\n   - severity\n   - specific fix\n   - preliminary confidence\n\n9. **Filter false positives with fast-tier subagents**\n   - Apply `references\u002Ffalse-positive-rubric.md`.\n   - Verify each finding against the exact diff hunk.\n   - Keep only findings on changed lines, or unchanged lines directly reached\u002Fexposed by changed hunks with explicit evidence.\n   - Drop findings that rely only on nearby unchanged context.\n   - Keep only findings scoring 80+.\n   - Assign final severity.\n\n10. **Output**\n\n- Use the user’s requested mode.\n- For PR comment or machine-readable output, use `references\u002Foutput-formats.md`.\n- Normal format:\n  - severity\n  - file\u002Fline\n  - issue\n  - impact\n  - suggested fix\n- If no findings survive, say:\n  `No change-linked issues were found.`\n\n## Tone\n\nBe brief, direct, and serious. Do not soften important correctness, security, or maintainability problems.\n\n## Final checklist\n\n- [ ] Prerequisite skills (`addy-code-review-and-quality` and `delegate-to-subagents`) were successfully activated.\n- [ ] Target is fixed or clarified.\n- [ ] PR eligibility was checked, if applicable.\n- [ ] Relevant context and standards were reviewed.\n- [ ] Spec review ran or `no spec available` was recorded.\n- [ ] Required catalog subagents ran for correctness, security, tests, and general quality.\n- [ ] Large-change triage ran if thresholds were exceeded.\n- [ ] Every kept finding is change-linked and verified against an exact diff hunk.\n- [ ] Standards findings cite explicit repo rules.\n- [ ] False-positive score is 80+ for every kept finding.\n- [ ] Findings cite code, standards, specs, or diff evidence as applicable.\n- [ ] Output matches the requested mode.\n",{"name":5,"description":7,"compatibility":54,"disable-model-invocation":55},"Requires subagent dispatch, including for lightweight reviews.",true,"main","2ce71d590264b43342c52d3011b0097c5ece7e21","skills\u002Fdefault\u002Fcode-review","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjapurcell","2026-11-11 08:59:34",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":55},[64,67,70],{"tool":65,"command":66},"npx","npx skills add japurcell\u002Fskills --skill code-review",{"tool":68,"command":69},"bunx","bunx skills add japurcell\u002Fskills --skill code-review",{"tool":71,"command":72},"pnpm","pnpm dlx skills add japurcell\u002Fskills --skill code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002FSKILL.md",[75,81,85,91,95,99,103,107,111,115],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"agents\u002Fopenai.yaml","REFERENCE","参考文档",164,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Fagents\u002Fopenai.yaml",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"evals\u002Fevals.json",5192,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Fevals\u002Fevals.json",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fgrade_benchmark.py","SCRIPT","脚本",9105,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Fevals\u002Fgrade_benchmark.py",{"path":92,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fcode-smells.md",1625,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Fcode-smells.md",{"path":96,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Ffalse-positive-rubric.md",841,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Ffalse-positive-rubric.md",{"path":100,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Flarge-change-triage.md",1168,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Flarge-change-triage.md",{"path":104,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fmaintainability-criteria.md",1596,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Fmaintainability-criteria.md",{"path":108,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Foutput-formats.md",1568,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Foutput-formats.md",{"path":112,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fpr-protocol.md",717,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Fpr-protocol.md",{"path":116,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fstandards-files.md",550,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fcode-review\u002Freferences\u002Fstandards-files.md",[120,147,168,196,219,239],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":49},"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",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[130,131,132,133,134,37,135,136,137,138,139,47,140,141,142,143,144,145,146],"create","spec","spec create","feature","planning","system","use","Existing","task","output","product","implementation","revise","compatibility","behavioral","idea","path",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":49},"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",[153],{"categoryNo":127,"categoryName":128,"taxonomyType":26,"taxonomyTypeDesc":27},[155,156,157,130,158,159,160,161,39,162,138,163,164,165,166,167,146],"prd ralph","ralph","prd","progress","verify","at","complete","it","log","scoped","false","file","id",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":49},"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",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[178,179,180,181,182,183,184,185,136,186,187,30,188,189,190,191,192,193,194,195,37],"fsdp style guide","style guide","FSDP","style","guide","visual regression","regression","design","visual","tasks","visual design","alerts","work","branding","layout","audit","ux","behavior",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":49},"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",[],[203,204,205,206,207,190,208,209,210,211,212,213,214,215,136,37,216,217,218],"agency priorities","priorities","agency","self","alignment","plan","goals","proposals","direction","how","project","strategic","service","when","briefings","self-contained",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":228,"publishedAt":49},"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",[225],{"categoryNo":226,"categoryName":227,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员",[229,230,207,231,130,190,232,233,234,235,160,205,41,215,136,236,237,238,137,216],"report","accomplishment report","cost","concise","human","time","update","closeout","savings","execplan",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":251,"publishedAt":49},"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",[245,248],{"categoryNo":246,"categoryName":247,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":249,"categoryName":250,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[252,253,37,136,254,255,216],"writing","writing for agents","documents","editing"]