[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AZAXF5FVFCDJF52MV4QWC":3,"skill-same:01M78AZAXF5FVFCDJF52MV4QWC":51},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M78AZAXF5FVFCDJF52MV4QWC","documentation-freshness",null,"Assess whether agent-facing project guidance remains current using bounded Git evidence, explicit adoption signals, and reviewable refresh decisions.","hermes-jarvis-bot\u002Fhermes-agent-config-kit","hermes-jarvis-bot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F288284026?v=4","01M78AV3BBD4M67J3YWSQRKP1Q","01M78AV3C2SKH53E0PZMXAKTTS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fdocumentation-freshness\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: documentation-freshness\ndescription: \"Assess whether agent-facing project guidance remains current using bounded Git evidence, explicit adoption signals, and reviewable refresh decisions.\"\nversion: 0.1.0\nlicense: MIT\nmetadata:\n  hermes_config_kit:\n    source_repo: AnastasiyaW\u002Fclaude-code-config\n    source_path: rules\u002Fagent-docs-freshness.md\n    adapter: hermes-agent-config-kit\n    conversion: adapted\n---\n\n# Documentation Freshness\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Frules\u002Fagent-docs-freshness.md`.\n\nThis module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.\n\n# Documentation Freshness\n\nThis module distinguishes documentation that exists from documentation that remains current. It provides a read-only review protocol for agent-facing project guidance. It does not create files, activate validators, install integrations, or schedule recurring checks.\n\n## When to use\n\nUse this module when a long-running repository has agent guidance, a knowledge base, layer notes, feature narratives, or generated reference material and there is reason to suspect the implementation has moved ahead of it.\n\nUse `documentation-integrity` for path, command, link, and generated-output correctness. Use this module for the separate question: has relevant project change accumulated since the documentation was last intentionally refreshed?\n\n## Read-only freshness protocol\n\n1. Identify the documentation anchor and its owner. Prefer a project guidance file, a layer index, a knowledge-base entry point, or a documented generated-output manifest.\n2. Verify that the anchor is intentionally part of the project; do not treat an arbitrary markdown file as required documentation.\n3. Inspect the most recent commit touching the anchor and the commits since it using Git history.\n4. Classify intervening changes by relevance: documentation-only, implementation change, interface\u002Fconfiguration change, operational change, or unrelated work.\n5. Inspect a small representative sample of relevant diffs and compare their claims with the anchor.\n6. Record one outcome: current, refresh recommended, insufficient evidence, or no adopted documentation surface.\n\nCommit distance is a signal, not a verdict. A large count of unrelated commits does not prove drift; a single interface change can make an otherwise recent document stale.\n\n## Adoption boundary\n\nDocumentation freshness checks should be opt-in through an explicit project convention: a named guidance path, a documented knowledge-base root, a maintained layer tree, or a repository-specific validation command.\n\nDo not impose a documentation requirement on every small repository. A lightweight project may need only a concise README and current local context. A long-running project earns stronger freshness review when its complexity, collaboration, or operational risk makes stale guidance costly.\n\nIf a repository declares durable project tracking but has no stated documentation surface, report the gap and propose a small manual adoption step. Do not create a tree, run generation, or add enforcement without operator confirmation.\n\n## Safe response to suspected drift\n\n1. Gather evidence before editing: changed paths, interfaces, commands, generated outputs, and any affected guidance sections.\n2. Propose the smallest refresh that restores accurate navigation and operational safety.\n3. Keep implementation truth in source control, manifests, tests, and telemetry; documentation summarises and points to those sources.\n4. Treat generated reference material as reviewable output, not authoritative truth.\n5. Obtain operator confirmation before write-impacting documentation changes under the project's policy.\n6. After an approved refresh, validate referenced paths, commands, counts, and consumer-facing instructions with `documentation-integrity`.\n\n## Avoid\n\n- Treating an age threshold as an automatic failure.\n- Blocking work or session completion solely because documentation is old.\n- Automatically generating documentation or spending external-provider budget to refresh it.\n- Treating a document-presence check as proof that the document is correct or current.\n- Adding active enforcement, background automation, or repository configuration as part of this guidance.\n\n## Reporting\n\nReport the documentation anchor, Git evidence reviewed, relevant change categories, freshness outcome, proposed refresh scope, and any operator-confirmation point. State clearly when the evidence is only suggestive.\n\nUseful output is a bounded, evidence-based maintenance decision, not a ceremonial document-age score.\n","# Documentation Freshness\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Frules\u002Fagent-docs-freshness.md`.\n\nThis module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.\n\n# Documentation Freshness\n\nThis module distinguishes documentation that exists from documentation that remains current. It provides a read-only review protocol for agent-facing project guidance. It does not create files, activate validators, install integrations, or schedule recurring checks.\n\n## When to use\n\nUse this module when a long-running repository has agent guidance, a knowledge base, layer notes, feature narratives, or generated reference material and there is reason to suspect the implementation has moved ahead of it.\n\nUse `documentation-integrity` for path, command, link, and generated-output correctness. Use this module for the separate question: has relevant project change accumulated since the documentation was last intentionally refreshed?\n\n## Read-only freshness protocol\n\n1. Identify the documentation anchor and its owner. Prefer a project guidance file, a layer index, a knowledge-base entry point, or a documented generated-output manifest.\n2. Verify that the anchor is intentionally part of the project; do not treat an arbitrary markdown file as required documentation.\n3. Inspect the most recent commit touching the anchor and the commits since it using Git history.\n4. Classify intervening changes by relevance: documentation-only, implementation change, interface\u002Fconfiguration change, operational change, or unrelated work.\n5. Inspect a small representative sample of relevant diffs and compare their claims with the anchor.\n6. Record one outcome: current, refresh recommended, insufficient evidence, or no adopted documentation surface.\n\nCommit distance is a signal, not a verdict. A large count of unrelated commits does not prove drift; a single interface change can make an otherwise recent document stale.\n\n## Adoption boundary\n\nDocumentation freshness checks should be opt-in through an explicit project convention: a named guidance path, a documented knowledge-base root, a maintained layer tree, or a repository-specific validation command.\n\nDo not impose a documentation requirement on every small repository. A lightweight project may need only a concise README and current local context. A long-running project earns stronger freshness review when its complexity, collaboration, or operational risk makes stale guidance costly.\n\nIf a repository declares durable project tracking but has no stated documentation surface, report the gap and propose a small manual adoption step. Do not create a tree, run generation, or add enforcement without operator confirmation.\n\n## Safe response to suspected drift\n\n1. Gather evidence before editing: changed paths, interfaces, commands, generated outputs, and any affected guidance sections.\n2. Propose the smallest refresh that restores accurate navigation and operational safety.\n3. Keep implementation truth in source control, manifests, tests, and telemetry; documentation summarises and points to those sources.\n4. Treat generated reference material as reviewable output, not authoritative truth.\n5. Obtain operator confirmation before write-impacting documentation changes under the project's policy.\n6. After an approved refresh, validate referenced paths, commands, counts, and consumer-facing instructions with `documentation-integrity`.\n\n## Avoid\n\n- Treating an age threshold as an automatic failure.\n- Blocking work or session completion solely because documentation is old.\n- Automatically generating documentation or spending external-provider budget to refresh it.\n- Treating a document-presence check as proof that the document is correct or current.\n- Adding active enforcement, background automation, or repository configuration as part of this guidance.\n\n## Reporting\n\nReport the documentation anchor, Git evidence reviewed, relevant change categories, freshness outcome, proposed refresh scope, and any operator-confirmation point. State clearly when the evidence is only suggestive.\n\nUseful output is a bounded, evidence-based maintenance decision, not a ceremonial document-age score.\n",{"name":5,"license":14,"version":23,"metadata":24,"description":7},"0.1.0",{"hermes_config_kit":25},{"adapter":26,"conversion":27,"source_path":28,"source_repo":29},"hermes-agent-config-kit","adapted","rules\u002Fagent-docs-freshness.md","AnastasiyaW\u002Fclaude-code-config","main","07d02526f424fc814f8350d6b0b728e81576603d","hermes\u002Fskills\u002Fdocumentation-freshness",0,"https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot","2026-11-14 18:25:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill documentation-freshness",{"tool":43,"command":44},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill documentation-freshness",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill documentation-freshness","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fdocumentation-freshness\u002FSKILL.md",true,[],[52,58,65,72,79,86],{"skillNo":53,"name":54,"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":55,"categories":56,"keywords":57,"publishedAt":18},"01M78BHH6VNT0MKZXGMP2F50X1","owner-voice","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fowner-voice\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M78BHD34XJHAK6EMZ7J1M80X","humanize-russian","Редактировать русский текст для ясности и естественного звучания, сохраняя факты,\nтермины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст\nживее, отредактировать русский черновик или статью перед публикацией.\nНе определяет авторство и не обещает обход детекторов. Для английского —\nhumanize-english; для структуры и доказательств — article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-russian\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M78BH9D09HCA7ECZMPEEAE5Y","humanize-english","Edit English drafts for clear, natural language while preserving facts, uncertainty,\ntechnical meaning, citations and genre. Use when: humanize this text, remove AI-style\nfiller, improve English prose, or edit an English article before publication.\nNot an authorship detector or a promise to bypass one. For Russian use\nhumanize-russian; for thesis\u002Fevidence and structure use article-structure-review.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fhumanize-english\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M78BH44Q25YMA16MC6FKZ2WY","caveman","Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse \"caveman\" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says \"caveman\", \"talk like caveman\", \"use caveman\", \"less tokens\", \"be brief\", or Russian \"пещерный режим\", \"говори как пещерный\", \"кратко\", \"меньше токенов\", \"экономь токены\" — or invokes \u002Fcaveman. Preserves the user's language (Russian in → Russian caveman out). Off only: \"stop caveman\" \u002F \"normal mode\" \u002F \"обычный режим\". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Fcaveman\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M78BGY0JTMTW3J3YE5RQTHCK","article-structure-review","Проверить структуру технической статьи после черновика: задача читателя, жанр,\nопора значимых утверждений на доказательства и честные ограничения.\nUse after the first draft, before publication. Исправлять структуру, когда это\nвходит в запрос; не создавать обязательный конвейер из других навыков.\nДля локальной языковой редактуры — humanize-english или humanize-russian.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M78BGRJYZGK1TNTCHWGY32W3","video-post-production","Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames\u002Fscenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.","https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fupstream\u002Fclaude-code-config\u002Fsnapshot\u002Fskills\u002Fvideo-production\u002Fvideo-post-production\u002FSKILL.md",[],[]]