[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6D8GSWPXC04681NY3XA9BKB":3,"skill-same:01M6D8GSWPXC04681NY3XA9BKB":65},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6D8GSWPXC04681NY3XA9BKB","description-frontmatter-authoring",null,"Create or revise Markdown `description` frontmatter so `docgarden match` routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.","jesse-black\u002Fdocgarden","jesse-black","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5840911?v=4","01M6D8G07TP5PJH5NHT9YJ8E1Y","Jesse Black","01M6D8G0C92CS19125JXMPEVSQ",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002Fskills\u002Fdescription-frontmatter-authoring\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"authoring","description frontmatter authoring","docs","documents","create","repository","tuning","discovery","markdown","results","use","document","query","revise","2026-11-10 10:12:30",false,"---\nname: description-frontmatter-authoring\ndescription: Create or revise Markdown `description` frontmatter so `docgarden match` routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.\n---\n\n# Description Frontmatter Authoring\n\nUse this skill to make frontmatter descriptions work as the repository's routing layer.\n\n`docgarden match` is metadata-first discovery, not full-text search. It scores `name`, path context, and frontmatter `description`; it does not rely on the document body for normal routing. A good description tells an agent what the document is for and when to read it.\n\n## Workflow\n\n1. Identify the routing job.\n   - Write down 2-5 realistic queries that should find the document.\n   - Write down nearby documents that should not outrank it.\n\n2. Inspect the current route.\n   - Run `docgarden match \u003Cquery>` for each realistic query.\n   - Use `docgarden match --explain \u003Cquery>` when ranking looks surprising.\n\n3. Rewrite the description as a positive routing cue.\n   - Lead with the document type or task family.\n   - Include action words an agent or user would actually ask for.\n   - Include the scope only when it helps separate this document from similar ones.\n   - Keep it one sentence unless the document truly has multiple routing jobs.\n\n4. Remove accidental attractors.\n   - Avoid saying what the document is not. Negated phrases still add matchable tokens.\n   - Avoid broad words that make the document appear for unrelated workflows.\n   - Avoid duplicating another document's strongest trigger phrase unless both should route together.\n\n5. Validate the route and the lint policy.\n   - Rerun the same `docgarden match \u003Cquery>` checks.\n   - After modifying any Markdown file, run `docgarden lint \u003Cchanged-files> --color never`.\n\n## Description Pattern\n\nUse this shape:\n\n```text\n\u003CDocument kind> for \u003Cspecific task\u002Fscope>; read when \u003Cagent intent, workflow, or decision point>.\n```\n\nExamples:\n\n```yaml\ndescription: \"Working design draft for `docgarden match` scoring, including the shipped BM25F model, stopword handling, and future tuning directions.\"\n```\n\n```yaml\ndescription: \"Create, update, revise, reopen, or rescope an ExecPlan using `docs\u002FPLANS.md`; use when shaping plan requirements before implementation.\"\n```\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items; read when looking for deferred implementation work, small backlog items, or candidate topics to promote into a future plan.\"\n```\n\n## Negative-Phrase Trap\n\nDo not encode exclusions in the discovery description.\n\nBad:\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items that are not part of an active ExecPlan.\"\n```\n\nThis can surface TODO for queries about active plans because `active` and `ExecPlan` are still strong tokens.\n\nBetter:\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items; read when looking for deferred implementation work, small backlog items, or candidate topics to promote into a future plan.\"\n```\n\nMove exclusion details into the body if humans need them. The description should describe the positive route.\n\n## Heuristics\n\n- Prefer verbs from expected user requests: create, update, review, implement, debug, validate, route, score.\n- Prefer concrete nouns from the repository vocabulary: ExecPlan, frontmatter, match, lint, config, scoring, skills.\n- Use path-like scope words only when useful: active plan, completed plan, design doc, skill.\n- Keep stable context in descriptions; put volatile status or long rationale in the body.\n- If two documents compete, make their descriptions contrast by job, not by negation.\n\n## Done Criteria\n\nA description is good enough when:\n\n- expected queries route to the document near the top\n- unrelated documents stop appearing because of accidental shared words\n- the description remains true when read alone in `docgarden match` output\n- `docgarden lint \u003Cchanged-files> --color never` passes\n","# Description Frontmatter Authoring\n\nUse this skill to make frontmatter descriptions work as the repository's routing layer.\n\n`docgarden match` is metadata-first discovery, not full-text search. It scores `name`, path context, and frontmatter `description`; it does not rely on the document body for normal routing. A good description tells an agent what the document is for and when to read it.\n\n## Workflow\n\n1. Identify the routing job.\n   - Write down 2-5 realistic queries that should find the document.\n   - Write down nearby documents that should not outrank it.\n\n2. Inspect the current route.\n   - Run `docgarden match \u003Cquery>` for each realistic query.\n   - Use `docgarden match --explain \u003Cquery>` when ranking looks surprising.\n\n3. Rewrite the description as a positive routing cue.\n   - Lead with the document type or task family.\n   - Include action words an agent or user would actually ask for.\n   - Include the scope only when it helps separate this document from similar ones.\n   - Keep it one sentence unless the document truly has multiple routing jobs.\n\n4. Remove accidental attractors.\n   - Avoid saying what the document is not. Negated phrases still add matchable tokens.\n   - Avoid broad words that make the document appear for unrelated workflows.\n   - Avoid duplicating another document's strongest trigger phrase unless both should route together.\n\n5. Validate the route and the lint policy.\n   - Rerun the same `docgarden match \u003Cquery>` checks.\n   - After modifying any Markdown file, run `docgarden lint \u003Cchanged-files> --color never`.\n\n## Description Pattern\n\nUse this shape:\n\n```text\n\u003CDocument kind> for \u003Cspecific task\u002Fscope>; read when \u003Cagent intent, workflow, or decision point>.\n```\n\nExamples:\n\n```yaml\ndescription: \"Working design draft for `docgarden match` scoring, including the shipped BM25F model, stopword handling, and future tuning directions.\"\n```\n\n```yaml\ndescription: \"Create, update, revise, reopen, or rescope an ExecPlan using `docs\u002FPLANS.md`; use when shaping plan requirements before implementation.\"\n```\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items; read when looking for deferred implementation work, small backlog items, or candidate topics to promote into a future plan.\"\n```\n\n## Negative-Phrase Trap\n\nDo not encode exclusions in the discovery description.\n\nBad:\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items that are not part of an active ExecPlan.\"\n```\n\nThis can surface TODO for queries about active plans because `active` and `ExecPlan` are still strong tokens.\n\nBetter:\n\n```yaml\ndescription: \"Follow-up tasks and cleanup items; read when looking for deferred implementation work, small backlog items, or candidate topics to promote into a future plan.\"\n```\n\nMove exclusion details into the body if humans need them. The description should describe the positive route.\n\n## Heuristics\n\n- Prefer verbs from expected user requests: create, update, review, implement, debug, validate, route, score.\n- Prefer concrete nouns from the repository vocabulary: ExecPlan, frontmatter, match, lint, config, scoring, skills.\n- Use path-like scope words only when useful: active plan, completed plan, design doc, skill.\n- Keep stable context in descriptions; put volatile status or long rationale in the body.\n- If two documents compete, make their descriptions contrast by job, not by negation.\n\n## Done Criteria\n\nA description is good enough when:\n\n- expected queries route to the document near the top\n- unrelated documents stop appearing because of accidental shared words\n- the description remains true when read alone in `docgarden match` output\n- `docgarden lint \u003Cchanged-files> --color never` passes\n",{"name":5,"description":7},"main","a3937e6e80074000b5213e737409f99f6a8443e2","skills\u002Fdescription-frontmatter-authoring",0,"https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden","https:\u002F\u002Fgithub.com\u002Fjesse-black","Building the accessible communication tool I wish I'd had sooner.","2026-07-22 22:14:44",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add jesse-black\u002Fdocgarden --skill description-frontmatter-authoring",{"tool":57,"command":58},"bunx","bunx skills add jesse-black\u002Fdocgarden --skill description-frontmatter-authoring",{"tool":60,"command":61},"pnpm","pnpm dlx skills add jesse-black\u002Fdocgarden --skill description-frontmatter-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002Fskills\u002Fdescription-frontmatter-authoring\u002FSKILL.md",true,[],[66,79,87,102,115,133],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":75,"publishedAt":38},"01M6D8H0WMA0PYJXE10H076KB3","Skill Beacon","skillbeacon metadata for scoped skill discovery.","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002Ftests\u002Fdiscovery-repo\u002F.agents\u002Fskills\u002Fskillbeacon\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[68,76,77,31,78],"beacon","metadata","skill discovery",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":38},"01M6D8GXTTDAG9V9M5W1QCWSCK","Build Beacon","buildbeacon metadata for scoped skill discovery.","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002Ftests\u002Fdiscovery-repo\u002F.agents\u002Fskills\u002Fimplement\u002FSKILL.md",[],[76,86,81,77,31,78],"build",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":38},"01M6D8GPRP006YE31GRYKDRYCP","planner-execplan","Create, update, revise, reopen, or rescope a plan or ExecPlan using `PLANS.md`. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplanner-execplan\u002FSKILL.md",[],[94,95,96,28,97,98,34,99,100,37,101],"planner","planner execplan","change","update","plan","active","requirements","plans",{"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":108,"publishedAt":38},"01M6D8GKJJ1867WVATETQF36AR","generator-execplan","Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan.","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerator-execplan\u002FSKILL.md",[],[109,99,110,111,112,34,113,98,114],"generator execplan","resume","work","up","implement","continue",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":124,"publishedAt":38},"01M6D8GG5PKA3X8VAS35CRWHKH","evaluator-execplan","Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan.","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fevaluator-execplan\u002FSKILL.md",[121],{"categoryNo":122,"categoryName":123,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",[125,126,127,128,129,130,98,131,34,132,99],"evaluator execplan","review","code review","pr","code","worktree","branch","record",{"skillNo":134,"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":135,"categories":136,"keywords":138,"publishedAt":38},"01M6D8GCV06H47BZZB4K0A4T7K","https:\u002F\u002Fgithub.com\u002Fjesse-black\u002Fdocgarden\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdescription-frontmatter-authoring\u002FSKILL.md",[137],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,24,27,28,29,30,31,32,33,34,35,36,37,26]]