[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78B0ZGQB28YFBTJWPRSC7JA":3,"skill-same:01M78B0ZGQB28YFBTJWPRSC7JA":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},"01M78B0ZGQB28YFBTJWPRSC7JA","harness-feedback",null,"Treat a harness-overload complaint as an engineering finding: classify it into a profile, measure the burden, and correct the smallest scope instead of disabling the check.","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\u002Fharness-feedback\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: harness-feedback\ndescription: \"Treat a harness-overload complaint as an engineering finding: classify it into a profile, measure the burden, and correct the smallest scope instead of disabling the check.\"\nversion: 0.1.0\nlicense: MIT\nmetadata:\n  hermes_config_kit:\n    source_repo: AnastasiyaW\u002Fclaude-code-config\n    source_path: skills\u002Fdevelopment\u002Fharness-feedback\u002FSKILL.md\n    adapter: hermes-agent-config-kit\n    conversion: adapted\n---\n\n# Harness Feedback\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fdevelopment\u002Fharness-feedback\u002FSKILL.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# Harness Feedback\n\nUpstream source policy treats a harness-overload complaint as an engineering finding rather than permission to disable a safety check. Hermes adaptation keeps the profile taxonomy, feedback loop, and required-report discipline, while describing the intake mechanism generically instead of naming a specific hook.\n\n## Principle\n\nTreat \"the harness is too strict\" as an engineering finding, not as permission to disable a safety check. Find the boundary that owns the mismatch and move the check to the narrowest profile that actually needs its evidence.\n\n## When to use\n\nUse when an agent reports that a test, VM, proof, evaluator, or release gate is overloaded, too strict, blocking staging, or causing false positives. Do not use for ordinary test selection, a single test failure, or a full security audit that has no harness-scope question attached.\n\n## Profiles\n\nUse these profiles unless the project has a more specific, documented contract:\n\n| Profile | Purpose | Typical blocking checks |\n|---|---|---|\n| `staging-smoke` | Fast proof that the changed build starts and the critical path works | build, focused regression, one stable smoke\u002Fcontract check |\n| `security-proof` | Prove an adversarial or trust-boundary claim | hostile tests, source\u002Fcollector proof, fresh-context evaluator |\n| `release-attestation` | Prove the exact releasable artifact and its identity | signing, tool-identity, installer\u002Fpackage checks |\n| `nightly-stress` | Find intermittent and capacity failures | race, stress, environment matrix, long-running evals |\n\n`staging-smoke` must not require signing, production credentials, a release certificate, or a long VM stress run. `security-proof` may run on an unsigned staging build when its claim is about source or runtime behaviour. A release check may remain blocking for release promotion without becoming a per-edit gate.\n\n## Feedback loop\n\nFor every overload signal, record:\n\n1. requested profile and change boundary;\n2. gate that blocked or dominated the run;\n3. command, elapsed time, failure count, and evidence actually produced;\n4. whether the gate was relevant, duplicated, flaky, or misplaced;\n5. the smallest profile split or deletion of duplicate coverage;\n6. a before\u002Fafter run of the affected profile and a fresh review of the rule.\n\nIf the harness has a deterministic overload-signal mechanism, use it as the intake event: store the metadata outside the conversation and let it force the final report to name the mismatch rather than paraphrase it away. Where no such mechanism exists, record the same fields by hand in the project's normal durable-record location (backlog, incident log, or handoff). Durable policy changes belong in the repository; raw session traces do not.\n\n## Required report\n\nDo not write \"overkill\" and move on. Report:\n\n```text\nHarness feedback: OVERLOAD | CLEAR\nRequested profile: staging-smoke | security-proof | release-attestation | nightly-stress\nMis-scoped gate: \u003Cname>\nEvidence: \u003Ccommand, result, elapsed time, or explicit missing proof>\nCorrection: \u003Cprofile split or rule change>\nVerification: \u003Cbefore\u002Fafter commands and result>\nResidual risk: \u003Cwhat remains intentionally gated and where>\n```\n\n## Gotchas\n\n- A fresh evaluator is an independence control, not a release-signing check.\n- A VM can be a reusable execution environment without forcing release-identity checks into every VM smoke.\n- A green fast gate does not prove release readiness; a red release-only gate does not invalidate a staging smoke unless the staging claim depends on it.\n- Do not replace a misplaced gate with retries, sleeps, or a bypass marker.\n- Do not infer overload from one slow run; distinguish an environment failure from a profile-contract error.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Action |\n|---|---|---|\n| Staging smoke asks for signing | Release gate leaked into staging profile | split `release-attestation` and run the smoke on the unsigned staging artifact |\n| Security proof blocks on a production VM | Runtime environment and release identity are coupled | keep the VM, remove release-only assertions from the security profile |\n| Same gate fails repeatedly | Wrong scope, flaky boundary, or missing fixture | classify the failure and add a focused reproducer; never silently retry |\n| Agent says \"tests passed\" with no profile | Evidence contract is incomplete | require the report fields above and the exact command\u002Fresult |\n| Fix removes a safety check | Causal ownership was not traced | restore the check, document the narrower boundary, and re-verify it there |\n\n## Relationship to other modules\n\n- Use `harness-audit` for a holistic scorecard of a project's agent-working conventions; use this module for one specific reported overload signal.\n- Use `harness-design` when the underlying generator\u002Fevaluator split itself needs redesigning, not just re-scoping.\n- Use `proof-verify` for the frozen-acceptance-criteria verification cycle that a corrected profile still has to satisfy.\n","# Harness Feedback\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fdevelopment\u002Fharness-feedback\u002FSKILL.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# Harness Feedback\n\nUpstream source policy treats a harness-overload complaint as an engineering finding rather than permission to disable a safety check. Hermes adaptation keeps the profile taxonomy, feedback loop, and required-report discipline, while describing the intake mechanism generically instead of naming a specific hook.\n\n## Principle\n\nTreat \"the harness is too strict\" as an engineering finding, not as permission to disable a safety check. Find the boundary that owns the mismatch and move the check to the narrowest profile that actually needs its evidence.\n\n## When to use\n\nUse when an agent reports that a test, VM, proof, evaluator, or release gate is overloaded, too strict, blocking staging, or causing false positives. Do not use for ordinary test selection, a single test failure, or a full security audit that has no harness-scope question attached.\n\n## Profiles\n\nUse these profiles unless the project has a more specific, documented contract:\n\n| Profile | Purpose | Typical blocking checks |\n|---|---|---|\n| `staging-smoke` | Fast proof that the changed build starts and the critical path works | build, focused regression, one stable smoke\u002Fcontract check |\n| `security-proof` | Prove an adversarial or trust-boundary claim | hostile tests, source\u002Fcollector proof, fresh-context evaluator |\n| `release-attestation` | Prove the exact releasable artifact and its identity | signing, tool-identity, installer\u002Fpackage checks |\n| `nightly-stress` | Find intermittent and capacity failures | race, stress, environment matrix, long-running evals |\n\n`staging-smoke` must not require signing, production credentials, a release certificate, or a long VM stress run. `security-proof` may run on an unsigned staging build when its claim is about source or runtime behaviour. A release check may remain blocking for release promotion without becoming a per-edit gate.\n\n## Feedback loop\n\nFor every overload signal, record:\n\n1. requested profile and change boundary;\n2. gate that blocked or dominated the run;\n3. command, elapsed time, failure count, and evidence actually produced;\n4. whether the gate was relevant, duplicated, flaky, or misplaced;\n5. the smallest profile split or deletion of duplicate coverage;\n6. a before\u002Fafter run of the affected profile and a fresh review of the rule.\n\nIf the harness has a deterministic overload-signal mechanism, use it as the intake event: store the metadata outside the conversation and let it force the final report to name the mismatch rather than paraphrase it away. Where no such mechanism exists, record the same fields by hand in the project's normal durable-record location (backlog, incident log, or handoff). Durable policy changes belong in the repository; raw session traces do not.\n\n## Required report\n\nDo not write \"overkill\" and move on. Report:\n\n```text\nHarness feedback: OVERLOAD | CLEAR\nRequested profile: staging-smoke | security-proof | release-attestation | nightly-stress\nMis-scoped gate: \u003Cname>\nEvidence: \u003Ccommand, result, elapsed time, or explicit missing proof>\nCorrection: \u003Cprofile split or rule change>\nVerification: \u003Cbefore\u002Fafter commands and result>\nResidual risk: \u003Cwhat remains intentionally gated and where>\n```\n\n## Gotchas\n\n- A fresh evaluator is an independence control, not a release-signing check.\n- A VM can be a reusable execution environment without forcing release-identity checks into every VM smoke.\n- A green fast gate does not prove release readiness; a red release-only gate does not invalidate a staging smoke unless the staging claim depends on it.\n- Do not replace a misplaced gate with retries, sleeps, or a bypass marker.\n- Do not infer overload from one slow run; distinguish an environment failure from a profile-contract error.\n\n## Troubleshooting\n\n| Symptom | Likely cause | Action |\n|---|---|---|\n| Staging smoke asks for signing | Release gate leaked into staging profile | split `release-attestation` and run the smoke on the unsigned staging artifact |\n| Security proof blocks on a production VM | Runtime environment and release identity are coupled | keep the VM, remove release-only assertions from the security profile |\n| Same gate fails repeatedly | Wrong scope, flaky boundary, or missing fixture | classify the failure and add a focused reproducer; never silently retry |\n| Agent says \"tests passed\" with no profile | Evidence contract is incomplete | require the report fields above and the exact command\u002Fresult |\n| Fix removes a safety check | Causal ownership was not traced | restore the check, document the narrower boundary, and re-verify it there |\n\n## Relationship to other modules\n\n- Use `harness-audit` for a holistic scorecard of a project's agent-working conventions; use this module for one specific reported overload signal.\n- Use `harness-design` when the underlying generator\u002Fevaluator split itself needs redesigning, not just re-scoping.\n- Use `proof-verify` for the frozen-acceptance-criteria verification cycle that a corrected profile still has to satisfy.\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","skills\u002Fdevelopment\u002Fharness-feedback\u002FSKILL.md","AnastasiyaW\u002Fclaude-code-config","main","07d02526f424fc814f8350d6b0b728e81576603d","hermes\u002Fskills\u002Fharness-feedback",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 harness-feedback",{"tool":43,"command":44},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill harness-feedback",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill harness-feedback","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fharness-feedback\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",[],[]]