[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78AXGGQ66PTYTW2TG89A54J":3,"skill-same:01M78AXGGQ66PTYTW2TG89A54J":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},"01M78AXGGQ66PTYTW2TG89A54J","article-structure-review",null,"Review a completed article's macro-structure, evidence balance, genre fit, stated limitations, section load, and appropriate use of visuals without rewriting prose or publishing content.","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\u002Farticle-structure-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: article-structure-review\ndescription: \"Review a completed article's macro-structure, evidence balance, genre fit, stated limitations, section load, and appropriate use of visuals without rewriting prose or publishing content.\"\nversion: 0.1.0\nlicense: MIT\nmetadata:\n  hermes_config_kit:\n    source_repo: AnastasiyaW\u002Fclaude-code-config\n    source_path: skills\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md\n    adapter: hermes-agent-config-kit\n    conversion: adapted\n---\n\n# Article Structure Review\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fwriting\u002Farticle-structure-review\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# Article structure review\n\nUse this module after a complete draft exists and before sentence-level editing or\npublication. It is a read-only editorial protocol for macro-structure: the relation\nbetween claims and their support, genre and reader expectations, declared limitations,\nsection load, and whether a visual would communicate structure more clearly than prose.\n\n## Boundary and overlap\n\nUse `humanize-russian` for Russian-language phrasing, register, cadence, and factual\npreservation. Use the installed `humanizer` module for a general scan of generic\nAI-writing patterns. This module does not prescribe wording, simulate a human voice,\nconceal authorship, invent evidence, or bypass publication, disclosure, or editorial\nreview requirements.\n\nTreat numerical ratios and paragraph-count heuristics as optional diagnostic signals,\nnot publication gates. A claim may be supported by a concrete example, a sourced\nfact, a reproducible method, a clearly bounded case, or an explicit uncertainty; the\nappropriate balance depends on the article's genre and audience.\n\n## Read-only review protocol\n\n1. **Set the editorial brief.** Identify the intended audience, primary genre,\n   publication context, central question, factual constraints, and any required\n   disclosure. If the article is stored in a file, inspect it before proposing changes.\n2. **Check claim and support balance.** For each major section, mark its important\n   claims and the evidence or reasoning that supports them. Flag unsupported assertions,\n   evidence that arrives too late, and sections that accumulate conclusions without\n   showing how the reader can assess them. Propose the smallest repair: qualify a\n   claim, add available evidence, move support nearer to the claim, or narrow scope.\n3. **Check genre and narrative contract.** Confirm that the title, opening, section\n   sequence, and conclusion serve one primary genre such as analysis, tutorial,\n   reference, opinion, or experience report. A deliberate genre shift is acceptable\n   when it is signposted and has a clear purpose; an accidental one should be clarified\n   or separated.\n4. **Make limitations visible.** For articles that present a tool, approach, result,\n   or recommendation, locate where assumptions, trade-offs, untested conditions, and\n   known failure modes are stated. Recommend a bounded limitations section when their\n   absence could cause readers to overgeneralise. Do not manufacture caveats or\n   personal experience that the author cannot support.\n5. **Review section load.** Compare the conceptual load of opening, middle, and final\n   sections. Flag a dense section that introduces many new ideas without transitions,\n   examples, or staging. Suggest splitting, reordering, summarising, or moving detail\n   to a separately scoped article only when it improves the reader's path.\n6. **Choose visual or prose deliberately.** When a section explains relationships,\n   hierarchy, architecture, comparison, categories, or a timeline, ask whether a\n   table, diagram, or other visual would make the structure clearer. Use prose for\n   reasoning, sequence, nuance, and narrative. A visual is a proposal, not a required\n   deliverable.\n7. **Read back the structure.** Read the title, opening, headings, first paragraphs,\n   transitions, and conclusion as a reader would. Record the supported thesis, genre,\n   limitations, structural risks, and proposed edits separately from any actual write.\n\n## Output shape\n\nReturn a compact structural review with: editorial brief; claim\u002Fsupport observations;\ngenre and reader-path assessment; limitations and uncertainty; section-load and\nvisual\u002Fprose recommendations; retained facts; and any operator confirmation required\nbefore changing a file or publishing. Preserve the author's evidence and make the\nscope of uncertainty visible rather than polishing it away.\n","# Article Structure Review\n\nSource: `AnastasiyaW\u002Fclaude-code-config\u002Fskills\u002Fwriting\u002Farticle-structure-review\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# Article structure review\n\nUse this module after a complete draft exists and before sentence-level editing or\npublication. It is a read-only editorial protocol for macro-structure: the relation\nbetween claims and their support, genre and reader expectations, declared limitations,\nsection load, and whether a visual would communicate structure more clearly than prose.\n\n## Boundary and overlap\n\nUse `humanize-russian` for Russian-language phrasing, register, cadence, and factual\npreservation. Use the installed `humanizer` module for a general scan of generic\nAI-writing patterns. This module does not prescribe wording, simulate a human voice,\nconceal authorship, invent evidence, or bypass publication, disclosure, or editorial\nreview requirements.\n\nTreat numerical ratios and paragraph-count heuristics as optional diagnostic signals,\nnot publication gates. A claim may be supported by a concrete example, a sourced\nfact, a reproducible method, a clearly bounded case, or an explicit uncertainty; the\nappropriate balance depends on the article's genre and audience.\n\n## Read-only review protocol\n\n1. **Set the editorial brief.** Identify the intended audience, primary genre,\n   publication context, central question, factual constraints, and any required\n   disclosure. If the article is stored in a file, inspect it before proposing changes.\n2. **Check claim and support balance.** For each major section, mark its important\n   claims and the evidence or reasoning that supports them. Flag unsupported assertions,\n   evidence that arrives too late, and sections that accumulate conclusions without\n   showing how the reader can assess them. Propose the smallest repair: qualify a\n   claim, add available evidence, move support nearer to the claim, or narrow scope.\n3. **Check genre and narrative contract.** Confirm that the title, opening, section\n   sequence, and conclusion serve one primary genre such as analysis, tutorial,\n   reference, opinion, or experience report. A deliberate genre shift is acceptable\n   when it is signposted and has a clear purpose; an accidental one should be clarified\n   or separated.\n4. **Make limitations visible.** For articles that present a tool, approach, result,\n   or recommendation, locate where assumptions, trade-offs, untested conditions, and\n   known failure modes are stated. Recommend a bounded limitations section when their\n   absence could cause readers to overgeneralise. Do not manufacture caveats or\n   personal experience that the author cannot support.\n5. **Review section load.** Compare the conceptual load of opening, middle, and final\n   sections. Flag a dense section that introduces many new ideas without transitions,\n   examples, or staging. Suggest splitting, reordering, summarising, or moving detail\n   to a separately scoped article only when it improves the reader's path.\n6. **Choose visual or prose deliberately.** When a section explains relationships,\n   hierarchy, architecture, comparison, categories, or a timeline, ask whether a\n   table, diagram, or other visual would make the structure clearer. Use prose for\n   reasoning, sequence, nuance, and narrative. A visual is a proposal, not a required\n   deliverable.\n7. **Read back the structure.** Read the title, opening, headings, first paragraphs,\n   transitions, and conclusion as a reader would. Record the supported thesis, genre,\n   limitations, structural risks, and proposed edits separately from any actual write.\n\n## Output shape\n\nReturn a compact structural review with: editorial brief; claim\u002Fsupport observations;\ngenre and reader-path assessment; limitations and uncertainty; section-load and\nvisual\u002Fprose recommendations; retained facts; and any operator confirmation required\nbefore changing a file or publishing. Preserve the author's evidence and make the\nscope of uncertainty visible rather than polishing it away.\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\u002Fwriting\u002Farticle-structure-review\u002FSKILL.md","AnastasiyaW\u002Fclaude-code-config","main","07d02526f424fc814f8350d6b0b728e81576603d","hermes\u002Fskills\u002Farticle-structure-review",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 article-structure-review",{"tool":43,"command":44},"bunx","bunx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill article-structure-review",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hermes-jarvis-bot\u002Fhermes-agent-config-kit --skill article-structure-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhermes-jarvis-bot\u002Fhermes-agent-config-kit\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Farticle-structure-review\u002FSKILL.md",true,[],[52,58,65,72,79,85],{"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":5,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M78BGY0JTMTW3J3YE5RQTHCK","Проверить структуру технической статьи после черновика: задача читателя, жанр,\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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]