[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736WZ5FG6MDFBXR4MEZQD8V":3,"skill-same:01M736WZ5FG6MDFBXR4MEZQD8V":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M736WZ5FG6MDFBXR4MEZQD8V","repo-docs-boundary",null,"Audit or maintain README, contributor setup, and durable repository docs placement while preserving the active repository policy.","graysurf\u002Fagent-runtime-kit","graysurf","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10785178?v=4","01M736PQHYKHFMNBYF8BT93NM4","01M736PQJWYH7G046WAN7EQCHD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fmeta\u002Fskills\u002Frepo-docs-boundary\u002Fexpected\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: repo-docs-boundary\ndescription: >\n  Audit or maintain README, contributor setup, and durable repository docs\n  placement while preserving the active repository policy.\n---\n\n# Repository Docs Boundary\n\n## Contract\n\nPrereqs:\n\n- Resolve the target git repository from the current working directory or an\n  explicit path.\n- Before writing, inspect the active repository policy and documentation\n  entrypoints: `AGENTS.md`, `CLAUDE.md`, `AGENT_DOCS.toml`, `README.md`,\n  `DEVELOPMENT.md`, `CONTRIBUTING.md`, `docs\u002F`, package manifests, CI config,\n  and project-owned validation scripts when present.\n- Activate and follow the repository's required docs intent before editing.\n  A closer repository rule overrides this general placement guide.\n\nInputs:\n\n- Mode:\n  - `audit` inspects and recommends changes without writing.\n  - `apply` makes a narrow requested documentation change after inspection.\n  - `new-repo` proposes or creates minimal first-pass entrypoints.\n- Optional repository path; default is the current working directory.\n- User constraints such as audience, package type, install surface, maturity,\n  validation command, or preferred language.\n\nOutputs:\n\n- In `audit` mode, a concise section inventory with `keep`, `move`,\n  `summarize+link`, `split`, `delete`, or `create` recommendations.\n- In `apply` or `new-repo` mode, narrowly edited root docs and only the\n  supporting `docs\u002F**` files that need a durable owner, plus validation results.\n- Focused open questions when repository purpose, audience, install path, or\n  contributor validation cannot be verified.\n\nFailure modes:\n\n- Repository purpose or workflow is too unclear to document concretely.\n- Existing prose conflicts with live manifests, scripts, CI, or tests.\n- A proposed edit would duplicate an authoritative rule in multiple places.\n- Repository policy requires a different placement or validation path.\n\n## Entrypoint\n\nChoose one mode before acting:\n\n```text\nrepo-docs-boundary audit [repo-path]\nrepo-docs-boundary apply [repo-path]\nrepo-docs-boundary new-repo [repo-path]\n```\n\nDefault ambiguous or broad requests to `audit`. Treat a narrow explicit edit\nas `apply`. Resolve the repository root, run its declared preflight, and inspect\nthe relevant definitions and call sites before changing documentation.\n\n## Source Priority\n\nUse the strongest available source for each claim:\n\n1. User requirements for audience, positioning, and requested scope.\n2. Local manifests, package metadata, scripts, CI, hooks, docs catalogs, and\n   tests.\n3. Existing documentation after checking it against live project files.\n4. Inference, labeled when it affects placement or wording.\n\nFor external, unstable, or version-sensitive facts, activate the repository's\n`task-tools` intent and run `agent-docs preflight --intent task-tools`, then\nfollow `core\u002Fpolicies\u002Fexternal-facts.md` before asserting them.\n\n## Placement Rules\n\n### README.md\n\nKeep `README.md` user-facing. It should quickly establish repository identity,\naudience, value, install or run path, shortest useful example, major\ncapabilities, and links to contributor or detailed documentation.\n\nAvoid full development setup, exhaustive validation matrices, agent or PR\npolicy, long troubleshooting trees, internal design rationale, generated-file\nrules, and release ceremony unless ordinary users truly need them.\n\n### DEVELOPMENT.md\n\nKeep `DEVELOPMENT.md` contributor-focused and short enough to read before a\nnormal edit. Retain the setup prerequisites, required preflight, exact build or\ngeneration commands, finish-line validation, source-of-truth boundaries,\nhigh-risk gotchas, and release or delivery boundaries needed for routine work.\n\nMove rare runbooks, long rationale, complete troubleshooting trees, historical\nbackground, and tool reference detail outward. Do not reduce\n`DEVELOPMENT.md` to a link catalog: mandatory rules and exact everyday commands\nremain inline.\n\n### docs\u002F\n\nUse the repository's existing docs area for durable architecture, operations,\nadvanced configuration, troubleshooting, API or protocol reference, historical\ndecisions that remain useful, and feature-specific guides. When no closer rule\nexists, prefer lowercase kebab-case filenames and avoid new root-level Markdown\nfiles.\n\n## Workflow\n\n1. Classify the request as `audit`, `apply`, or `new-repo`.\n2. Resolve the repository root and inspect policy, root docs, docs indexes,\n   manifests, build scripts, CI, and validation surfaces relevant to the claims.\n3. Inventory each meaningful section by current location, target audience,\n   must-read-before-edit status, user-facing value, and long-form detail.\n4. Select one canonical owner for each rule or command. Keep short summaries in\n   root entrypoints and link to long-form detail instead of duplicating it.\n5. For `audit`, report evidence-backed placement findings and proposed actions\n   without editing.\n6. For `new-repo`, draft the smallest complete `README.md` and\n   `DEVELOPMENT.md`; create `docs\u002F` files only when necessary to prevent root\n   entrypoint bloat.\n7. For `apply`, edit narrowly and preserve the established tone, headings,\n   language, and link style. Do not rewrite unrelated sections to fit a generic\n   template.\n8. Run the repository's declared docs or development validation. If none\n   exists, check changed Markdown links and obvious stale references; report\n   any skipped validation and why.\n\n## Review Checklist\n\n- A non-contributor can understand and try the project from `README.md`.\n- Contributors can find setup, preflight, source-of-truth, and validation gates\n  in `DEVELOPMENT.md` without reading a long runbook first.\n- Long-lived detail has one stable owner under `docs\u002F` or a narrower existing\n  project area.\n- Root docs link to canonical detail without maintaining duplicate rules.\n- Relative links resolve and claims agree with current project files.\n- The result distinguishes verified facts, assumptions, and open questions.\n\n## Boundary\n\nThis skill owns documentation placement judgment, audits, and narrow docs\nedits. It does not own product strategy, package design, CI design, release\nautomation, or repository policy changes beyond documenting the current source\nof truth. When the documentation review reveals a behavior gap, name and route\nthe gap through the repository's implementation workflow instead of papering\nover it with prose.\n","# Repository Docs Boundary\n\n## Contract\n\nPrereqs:\n\n- Resolve the target git repository from the current working directory or an\n  explicit path.\n- Before writing, inspect the active repository policy and documentation\n  entrypoints: `AGENTS.md`, `CLAUDE.md`, `AGENT_DOCS.toml`, `README.md`,\n  `DEVELOPMENT.md`, `CONTRIBUTING.md`, `docs\u002F`, package manifests, CI config,\n  and project-owned validation scripts when present.\n- Activate and follow the repository's required docs intent before editing.\n  A closer repository rule overrides this general placement guide.\n\nInputs:\n\n- Mode:\n  - `audit` inspects and recommends changes without writing.\n  - `apply` makes a narrow requested documentation change after inspection.\n  - `new-repo` proposes or creates minimal first-pass entrypoints.\n- Optional repository path; default is the current working directory.\n- User constraints such as audience, package type, install surface, maturity,\n  validation command, or preferred language.\n\nOutputs:\n\n- In `audit` mode, a concise section inventory with `keep`, `move`,\n  `summarize+link`, `split`, `delete`, or `create` recommendations.\n- In `apply` or `new-repo` mode, narrowly edited root docs and only the\n  supporting `docs\u002F**` files that need a durable owner, plus validation results.\n- Focused open questions when repository purpose, audience, install path, or\n  contributor validation cannot be verified.\n\nFailure modes:\n\n- Repository purpose or workflow is too unclear to document concretely.\n- Existing prose conflicts with live manifests, scripts, CI, or tests.\n- A proposed edit would duplicate an authoritative rule in multiple places.\n- Repository policy requires a different placement or validation path.\n\n## Entrypoint\n\nChoose one mode before acting:\n\n```text\nrepo-docs-boundary audit [repo-path]\nrepo-docs-boundary apply [repo-path]\nrepo-docs-boundary new-repo [repo-path]\n```\n\nDefault ambiguous or broad requests to `audit`. Treat a narrow explicit edit\nas `apply`. Resolve the repository root, run its declared preflight, and inspect\nthe relevant definitions and call sites before changing documentation.\n\n## Source Priority\n\nUse the strongest available source for each claim:\n\n1. User requirements for audience, positioning, and requested scope.\n2. Local manifests, package metadata, scripts, CI, hooks, docs catalogs, and\n   tests.\n3. Existing documentation after checking it against live project files.\n4. Inference, labeled when it affects placement or wording.\n\nFor external, unstable, or version-sensitive facts, activate the repository's\n`task-tools` intent and run `agent-docs preflight --intent task-tools`, then\nfollow `core\u002Fpolicies\u002Fexternal-facts.md` before asserting them.\n\n## Placement Rules\n\n### README.md\n\nKeep `README.md` user-facing. It should quickly establish repository identity,\naudience, value, install or run path, shortest useful example, major\ncapabilities, and links to contributor or detailed documentation.\n\nAvoid full development setup, exhaustive validation matrices, agent or PR\npolicy, long troubleshooting trees, internal design rationale, generated-file\nrules, and release ceremony unless ordinary users truly need them.\n\n### DEVELOPMENT.md\n\nKeep `DEVELOPMENT.md` contributor-focused and short enough to read before a\nnormal edit. Retain the setup prerequisites, required preflight, exact build or\ngeneration commands, finish-line validation, source-of-truth boundaries,\nhigh-risk gotchas, and release or delivery boundaries needed for routine work.\n\nMove rare runbooks, long rationale, complete troubleshooting trees, historical\nbackground, and tool reference detail outward. Do not reduce\n`DEVELOPMENT.md` to a link catalog: mandatory rules and exact everyday commands\nremain inline.\n\n### docs\u002F\n\nUse the repository's existing docs area for durable architecture, operations,\nadvanced configuration, troubleshooting, API or protocol reference, historical\ndecisions that remain useful, and feature-specific guides. When no closer rule\nexists, prefer lowercase kebab-case filenames and avoid new root-level Markdown\nfiles.\n\n## Workflow\n\n1. Classify the request as `audit`, `apply`, or `new-repo`.\n2. Resolve the repository root and inspect policy, root docs, docs indexes,\n   manifests, build scripts, CI, and validation surfaces relevant to the claims.\n3. Inventory each meaningful section by current location, target audience,\n   must-read-before-edit status, user-facing value, and long-form detail.\n4. Select one canonical owner for each rule or command. Keep short summaries in\n   root entrypoints and link to long-form detail instead of duplicating it.\n5. For `audit`, report evidence-backed placement findings and proposed actions\n   without editing.\n6. For `new-repo`, draft the smallest complete `README.md` and\n   `DEVELOPMENT.md`; create `docs\u002F` files only when necessary to prevent root\n   entrypoint bloat.\n7. For `apply`, edit narrowly and preserve the established tone, headings,\n   language, and link style. Do not rewrite unrelated sections to fit a generic\n   template.\n8. Run the repository's declared docs or development validation. If none\n   exists, check changed Markdown links and obvious stale references; report\n   any skipped validation and why.\n\n## Review Checklist\n\n- A non-contributor can understand and try the project from `README.md`.\n- Contributors can find setup, preflight, source-of-truth, and validation gates\n  in `DEVELOPMENT.md` without reading a long runbook first.\n- Long-lived detail has one stable owner under `docs\u002F` or a narrower existing\n  project area.\n- Root docs link to canonical detail without maintaining duplicate rules.\n- Relative links resolve and claims agree with current project files.\n- The result distinguishes verified facts, assumptions, and open questions.\n\n## Boundary\n\nThis skill owns documentation placement judgment, audits, and narrow docs\nedits. It does not own product strategy, package design, CI design, release\nautomation, or repository policy changes beyond documenting the current source\nof truth. When the documentation review reveals a behavior gap, name and route\nthe gap through the repository's implementation workflow instead of papering\nover it with prose.\n",{"name":5,"description":7},"main","da7119f2ebece510d6955cea72743069f5496c73","tests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fmeta\u002Fskills\u002Frepo-docs-boundary\u002Fexpected","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit","https:\u002F\u002Fgithub.com\u002Fgraysurf","Building reliable tools for teams of AI coding agents · Rust \u002F TypeScript · @sympoies","2026-08-29 05:27:47",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add graysurf\u002Fagent-runtime-kit --skill repo-docs-boundary",{"tool":36,"command":37},"bunx","bunx skills add graysurf\u002Fagent-runtime-kit --skill repo-docs-boundary",{"tool":39,"command":40},"pnpm","pnpm dlx skills add graysurf\u002Fagent-runtime-kit --skill repo-docs-boundary","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Fmeta\u002Fskills\u002Frepo-docs-boundary\u002Fexpected\u002FSKILL.md",true,[],[45,51,56,63,70,77],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M736XWK14DFRERMQ8RT3HS0Z","removable-skill","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fcodex\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":52,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M736XTPQEKAYESDM1REN2KAN","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-skill\u002Ftests\u002Fgolden\u002Fclaude\u002Fplugins\u002Ffixture\u002Fskills\u002Fremovable-skill\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M736XRMWHMJB4X563G9J6QYY","removable-project-skill","Fixture project-local skill used to prove remove-project-skill dry-run coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fremove-project-skill\u002F.agents\u002Fskills\u002Fremovable-project-skill\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M736XPT65YZMPCBD4K3RHV4P","project-sample-skill","Fixture project-local skill used to prove create-project-skill governance coverage.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-smoke\u002Ffixtures\u002Fskill-lifecycle\u002Fcreate-project-skill\u002F.agents\u002Fskills\u002Fproject-sample-skill\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M736XKZVYWVQA1YB0P459WND","project-local-skill","Fixture project-local skill used by runtime-kit project-local smoke checks.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fprojects\u002Fproject-local-smoke\u002F.agents\u002Fskills\u002Fproject-local-skill\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M736XHA73KZ5G2TKWSED5P1B","topic-radar","Aggregate read-only AI and technology trend signals (Polymarket, Hacker News, GitHub, arXiv, Hugging Face, news search) into source-grounded Markdown or JSON; the lower-level data engine behind `daily-brief`.","https:\u002F\u002Fgithub.com\u002Fgraysurf\u002Fagent-runtime-kit\u002Fblob\u002Fmain\u002Ftests\u002Fgolden\u002Fhermes\u002Fplugins\u002Freporting\u002Fskills\u002Ftopic-radar\u002Fexpected\u002FSKILL.md",[],[]]