[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AVFZ5PVMMA2F127C2TMJT":3,"skill-same:01M78AVFZ5PVMMA2F127C2TMJT":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},"01M78AVFZ5PVMMA2F127C2TMJT","activity-journal-and-state-registry",null,"Maintain an append-only activity journal and a verified current-state registry for shared resources without activating enforcement hooks.","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\u002Factivity-journal-and-state-registry\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: activity-journal-and-state-registry\ndescription: \"Maintain an append-only activity journal and a verified current-state registry for shared resources without activating enforcement hooks.\"\nversion: 0.1.0\nlicense: MIT\nmetadata:\n  hermes_config_kit:\n    source_repo: AnastasiyaW\u002Fclaude-code-config\n    source_path: rules\u002Factivity-journal-and-state-registry.md\n    adapter: hermes-agent-config-kit\n    conversion: adapted\n---\n\n# Activity Journal And State Registry\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Frules\u002Factivity-journal-and-state-registry.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# Activity Journal and State Registry\n\nUpstream source policy combines an activity journal, a current-state registry, and an enforcement mechanism. Hermes adaptation retains the first two as an operator-reviewed convention for shared resources. It does not install, enable, or imply an active hook, validator, daemon, or scheduled protocol.\n\n## Principle\n\nFor multi-session work or a shared resource, make three questions answerable from durable evidence: what is running, who started it, and why.\n\nUse two distinct artefacts:\n\n1. an append-only activity journal for state-changing actions;\n2. a compact current-state registry for verified active work.\n\nThe journal is history. The registry is a snapshot. Neither substitutes for live process, service, queue, or resource telemetry.\n\n## When to use\n\nUse this convention when multiple sessions share a workstation, server, GPU, database, queue, deployment target, long-running job, or another mutable resource. For a single short task, normal command evidence and `session-handoff` are usually sufficient.\n\nChoose a repository-local or resource-local location deliberately. Do not create tracking files in a project or on a shared system without operator confirmation for that target.\n\n## Journal record\n\nAppend one record for a state-changing action that affects the shared scope: starting or stopping a job, restart, deployment, configuration change, delete, resource claim or release, or a material recovery action.\n\nEach record should identify:\n\n```text\ntimestamp | actor\u002Fsession | scope or resource | action | reason | result\u002Fevidence\n```\n\nPrefer append-safe JSONL or uniquely named entries. Do not rewrite prior records; append a correction if the history needs qualification. Read-only inspection does not normally require a journal entry.\n\nDo not record access credentials, private payloads, or raw sensitive command output.\n\n## Current-state registry\n\nKeep a small human-readable snapshot of verified active work:\n\n```text\nRunning now:\n- resource\u002Fjob: \u003Cidentifier>\n  owner: \u003Cactor\u002Fsession>\n  purpose: \u003Cbounded task>\n  started: \u003Ctimestamp>\n  writes\u002Fuses: \u003Cpaths, ports, queues, or resources>\n  verification: \u003Clive telemetry command or result>\n\nConstraints:\n- \u003Crelevant capacity, maintenance, or approval boundary>\n```\n\nUpdate the registry after a relevant state change, then verify its claims against live telemetry where practical. A registry that has not been checked is a hypothesis, not current truth.\n\n## Read-only design protocol\n\nBefore proposing adoption:\n\n1. Identify the shared resource, participants, topology, and existing source of truth.\n2. Decide whether an append-only journal and registry add information not already covered by service telemetry, scheduler records, Git, or `multi-session-coordination`.\n3. Define the smallest location, record fields, retention expectations, and owner.\n4. Specify the read-back command or telemetry that verifies each registry entry.\n5. Identify what remains manual and which write-impacting actions require operator confirmation.\n\nIf the resource has a real scheduler, service manager, or control plane, prefer that system's telemetry as authoritative and link to it from the registry rather than recreating it in prose.\n\n## Boundaries\n\n- This module is guidance, not enforcement.\n- Do not activate shell hooks, validators, background watchers, or scheduled protocols from this convention.\n- A file-based journal or registry coordinates trusted participants; it is not a security boundary.\n- Use `multi-session-coordination` for locks, heartbeats, and verified resource release.\n- Use `session-handoff` for bounded transfer between sessions.\n- Use `coordination-primitives-mapping` when topology or failure modes require a stronger primitive.\n\n## Reporting\n\nReport the resource scope, existing authoritative telemetry, whether the convention is justified, proposed journal and registry locations, required operator confirmation, and the live verification method. For a state-changing action, report both the appended record and the post-action telemetry read-back.\n\nClear state is useful. Pretending a markdown snapshot is a control plane is considerably less so.\n","# Activity Journal And State Registry\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Frules\u002Factivity-journal-and-state-registry.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# Activity Journal and State Registry\n\nUpstream source policy combines an activity journal, a current-state registry, and an enforcement mechanism. Hermes adaptation retains the first two as an operator-reviewed convention for shared resources. It does not install, enable, or imply an active hook, validator, daemon, or scheduled protocol.\n\n## Principle\n\nFor multi-session work or a shared resource, make three questions answerable from durable evidence: what is running, who started it, and why.\n\nUse two distinct artefacts:\n\n1. an append-only activity journal for state-changing actions;\n2. a compact current-state registry for verified active work.\n\nThe journal is history. The registry is a snapshot. Neither substitutes for live process, service, queue, or resource telemetry.\n\n## When to use\n\nUse this convention when multiple sessions share a workstation, server, GPU, database, queue, deployment target, long-running job, or another mutable resource. For a single short task, normal command evidence and `session-handoff` are usually sufficient.\n\nChoose a repository-local or resource-local location deliberately. Do not create tracking files in a project or on a shared system without operator confirmation for that target.\n\n## Journal record\n\nAppend one record for a state-changing action that affects the shared scope: starting or stopping a job, restart, deployment, configuration change, delete, resource claim or release, or a material recovery action.\n\nEach record should identify:\n\n```text\ntimestamp | actor\u002Fsession | scope or resource | action | reason | result\u002Fevidence\n```\n\nPrefer append-safe JSONL or uniquely named entries. Do not rewrite prior records; append a correction if the history needs qualification. Read-only inspection does not normally require a journal entry.\n\nDo not record access credentials, private payloads, or raw sensitive command output.\n\n## Current-state registry\n\nKeep a small human-readable snapshot of verified active work:\n\n```text\nRunning now:\n- resource\u002Fjob: \u003Cidentifier>\n  owner: \u003Cactor\u002Fsession>\n  purpose: \u003Cbounded task>\n  started: \u003Ctimestamp>\n  writes\u002Fuses: \u003Cpaths, ports, queues, or resources>\n  verification: \u003Clive telemetry command or result>\n\nConstraints:\n- \u003Crelevant capacity, maintenance, or approval boundary>\n```\n\nUpdate the registry after a relevant state change, then verify its claims against live telemetry where practical. A registry that has not been checked is a hypothesis, not current truth.\n\n## Read-only design protocol\n\nBefore proposing adoption:\n\n1. Identify the shared resource, participants, topology, and existing source of truth.\n2. Decide whether an append-only journal and registry add information not already covered by service telemetry, scheduler records, Git, or `multi-session-coordination`.\n3. Define the smallest location, record fields, retention expectations, and owner.\n4. Specify the read-back command or telemetry that verifies each registry entry.\n5. Identify what remains manual and which write-impacting actions require operator confirmation.\n\nIf the resource has a real scheduler, service manager, or control plane, prefer that system's telemetry as authoritative and link to it from the registry rather than recreating it in prose.\n\n## Boundaries\n\n- This module is guidance, not enforcement.\n- Do not activate shell hooks, validators, background watchers, or scheduled protocols from this convention.\n- A file-based journal or registry coordinates trusted participants; it is not a security boundary.\n- Use `multi-session-coordination` for locks, heartbeats, and verified resource release.\n- Use `session-handoff` for bounded transfer between sessions.\n- Use `coordination-primitives-mapping` when topology or failure modes require a stronger primitive.\n\n## Reporting\n\nReport the resource scope, existing authoritative telemetry, whether the convention is justified, proposed journal and registry locations, required operator confirmation, and the live verification method. For a state-changing action, report both the appended record and the post-action telemetry read-back.\n\nClear state is useful. Pretending a markdown snapshot is a control plane is considerably less so.\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\u002Factivity-journal-and-state-registry.md","AnastasiyaW\u002Fclaude-code-config","main","07d02526f424fc814f8350d6b0b728e81576603d","hermes\u002Fskills\u002Factivity-journal-and-state-registry",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 activity-journal-and-state-registry",{"tool":43,"command":44},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill activity-journal-and-state-registry",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill activity-journal-and-state-registry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Factivity-journal-and-state-registry\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",[],[]]