[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BJ31TAK2PC0EYA409FBT44":3,"skill-same:01M7BJ31TAK2PC0EYA409FBT44":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7BJ31TAK2PC0EYA409FBT44","hermes-agent-skill-authoring",null,"Author in-repo SKILL.md: frontmatter, validator, structure, and writing-quality principles.","darkmatter\u002Fhermes","darkmatter","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17834193?v=4","01M7BHSAW99WRAMTSSHNHX73V0","01M7BHSAXDR4PY4NA2DY5PN6W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fdevbox\u002Fprofiles\u002Fplanner\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: hermes-agent-skill-authoring\ndescription: \"Author in-repo SKILL.md: frontmatter, validator, structure, and writing-quality principles.\"\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [skills, authoring, hermes-agent, conventions, skill-md]\n    related_skills: [plan, requesting-code-review]\n---\n\n# Authoring Hermes-Agent Skills (in-repo)\n\n## Overview\n\nThere are two places a SKILL.md can live:\n\n1. **User-local:** `~\u002F.hermes\u002Fskills\u002F\u003Cmaybe-category>\u002F\u003Cname>\u002FSKILL.md` — personal, not shared. Created via `skill_manage(action='create')`.\n2. **In-repo (this skill is about this case):** `~\u002Fhermes-agent\u002Fskills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — committed, shipped with the package. Use `write_file` + `git add`. `skill_manage(action='create')` does NOT target this tree.\n\n## When to Use\n\n- User asks you to add a skill \"in this branch \u002F repo \u002F commit\"\n- You're committing a reusable workflow that should ship with hermes-agent\n- You're editing an existing skill under `~\u002Fhermes-agent\u002Fskills\u002F` (use `patch` for small edits, `write_file` for rewrites; `skill_manage` still works for patch on in-repo skills, but not for `create`)\n\n## Required Frontmatter\n\nSource of truth: `tools\u002Fskill_manager_tool.py::_validate_frontmatter`. Hard requirements:\n\n- Starts with `---` as the first bytes (no leading blank line).\n- Closes with `\\n---\\n` before the body.\n- Parses as a YAML mapping.\n- `name` field present.\n- `description` field present, ≤ **1024 chars** (`MAX_DESCRIPTION_LENGTH`).\n- Non-empty body after the closing `---`.\n\nPeer-matched shape used by every skill under `skills\u002Fsoftware-development\u002F`:\n\n```yaml\n---\nname: my-skill-name               # lowercase, hyphens, ≤64 chars (MAX_NAME_LENGTH)\ndescription: Use when \u003Ctrigger>. \u003Cone-line behavior>.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [short, descriptive, tags]\n    related_skills: [other-skill, another-skill]\n---\n```\n\n`version` \u002F `author` \u002F `license` \u002F `metadata` are NOT enforced by the validator, but every peer has them — omit and your skill sticks out.\n\n## Size Limits\n\n- Description: ≤ 1024 chars (enforced).\n- Full SKILL.md: ≤ 100,000 chars (enforced as `MAX_SKILL_CONTENT_CHARS`, ~36k tokens).\n- Peer skills in `software-development\u002F` sit at **8-14k chars**. Aim for that range. If you're pushing past 20k, split into `references\u002F*.md` and reference them from SKILL.md.\n\n## Writing Quality Principles\n\nA skill exists to make the agent's process more predictable. Predictability does **not** mean identical output every run; it means the agent reliably follows the same useful discipline.\n\nUse these quality checks when writing or editing any skill:\n\n1. **Optimize for process predictability.** Ask: what behavior should change when this skill loads? If a line does not change behavior, cut it.\n2. **Choose the right context load.** A model-invoked Hermes skill pays for its description every turn. Keep descriptions focused on trigger classes and the skill's distinctive behavior. Put details in the body or linked references.\n3. **Use an information hierarchy.** Put always-needed steps in `SKILL.md`; put branch-specific or bulky reference material in `references\u002F`, `templates\u002F`, or `scripts\u002F` and point to it only when needed.\n4. **End steps with completion criteria.** Each ordered step should say how the agent knows it is done. Good criteria are checkable and, when it matters, exhaustive: \"every modified file accounted for\" beats \"summarize changes.\"\n5. **Co-locate rules with the concept they govern.** Avoid scattering one idea across the file. Keep definition, caveats, examples, and verification near each other.\n6. **Use strong leading words.** Prefer compact concepts the model already knows — e.g. \"tight loop,\" \"tracer bullet,\" \"root cause,\" \"regression test\" — over long repeated explanations. A good leading word saves tokens and anchors behavior.\n7. **Prune duplication and no-ops.** Keep each meaning in one source of truth. Sentence by sentence, ask whether the sentence changes agent behavior versus the default. If not, delete it rather than polishing it.\n8. **Watch for premature completion.** If agents tend to rush a step, first sharpen that step's completion criterion. Split the sequence only when later steps distract from doing the current step well.\n\nCommon quality failures:\n\n- **Premature completion** — the skill lets the agent move on before the work is genuinely done.\n- **Duplication** — the same rule appears in multiple places and drifts.\n- **Sediment** — stale lines remain because adding felt safer than deleting.\n- **Sprawl** — too much always-visible material; push branch-specific reference behind pointers.\n- **No-op prose** — generic advice the agent would already follow without the skill.\n\n## Peer-Matched Structure\n\nEvery in-repo skill follows roughly:\n\n```\n# \u003CTitle>\n\n## Overview\nOne or two paragraphs: what and why.\n\n## When to Use\n- Bulleted triggers\n- \"Don't use for:\" counter-triggers\n\n## \u003CTopic sections specific to the skill>\n- Quick-reference tables are common\n- Code blocks with exact commands\n- Hermes-specific recipes (tests via scripts\u002Frun_tests.sh, ui-tui paths, etc.)\n\n## Common Pitfalls\nNumbered list of mistakes and their fixes.\n\n## Verification Checklist\n- [ ] Checkbox list of post-action verifications\n\n## One-Shot Recipes (optional)\nNamed scenarios → concrete command sequences.\n```\n\nNot every section is mandatory, but `Overview` + `When to Use` + actionable body + pitfalls are the minimum for the skill to feel like a peer.\n\n## Directory Placement\n\n```\nskills\u002F\u003Ccategory>\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\nCategories currently in repo (confirm with `ls skills\u002F`): `autonomous-ai-agents`, `creative`, `data-science`, `devops`, `dogfood`, `email`, `gaming`, `github`, `leisure`, `mcp`, `media`, `mlops\u002F*`, `note-taking`, `productivity`, `red-teaming`, `research`, `smart-home`, `social-media`, `software-development`.\n\nPick the closest existing category. Don't invent new top-level categories casually.\n\n## Workflow\n\n1. **Survey peers** in the target category:\n   ```\n   ls skills\u002F\u003Ccategory>\u002F\n   ```\n   Read 2-3 peer SKILL.md files to match tone and structure.\n2. **Check validator constraints** in `tools\u002Fskill_manager_tool.py` if unsure.\n3. **Draft** with `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md`.\n4. **Validate locally.** Use the repository\u002FHermes virtualenv interpreter that already provides PyYAML; a host system Python may not include `yaml`. Do not install PyYAML globally just for this check. If the project environment is unavailable, use Hermes's built-in skill loader\u002Fvalidator or a dependency-free parser for the required top-level fields.\n\n   ```python\n   import yaml, re, pathlib\n   content = pathlib.Path(\"skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md\").read_text()\n   assert content.startswith(\"---\")\n   m = re.search(r'\\n---\\s*\\n', content[3:])\n   fm = yaml.safe_load(content[3:m.start()+3])\n   assert \"name\" in fm and \"description\" in fm\n   assert len(fm[\"description\"]) \u003C= 1024\n   assert len(content) \u003C= 100_000\n   ```\n5. **Git add + commit** on the active branch.\n6. **Note:** the CURRENT session's skill loader is cached — `skill_view` \u002F `skills_list` will not see the new skill until a new session. This is expected, not a bug.\n\n## Cross-Referencing Other Skills\n\n`metadata.hermes.related_skills` unions both trees (`skills\u002F` in-repo and `~\u002F.hermes\u002Fskills\u002F`) at load time. You CAN reference a user-local skill from an in-repo skill, but it won't resolve for other users who clone the repo fresh. Prefer referencing only in-repo skills from in-repo skills. If a frequently-referenced skill lives only in `~\u002F.hermes\u002Fskills\u002F`, consider promoting it to the repo.\n\n## Editing Existing In-Repo Skills\n\n- **Small fix (typo, added pitfall, tightened trigger):** `skill_manage(action='patch', name=..., old_string=..., new_string=...)` works fine on in-repo skills.\n- **Major rewrite:** `write_file` the whole SKILL.md. `skill_manage(action='edit')` also works but requires supplying the full new content.\n- **Adding supporting files:** `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002Freferences\u002F\u003Cfile>.md`, `templates\u002F\u003Cfile>`, or `scripts\u002F\u003Cfile>`. `skill_manage(action='write_file')` also works and enforces the references\u002Ftemplates\u002Fscripts\u002Fassets subdir allowlist.\n- **Always commit** the edit — in-repo skills are source, not runtime state.\n\n## Common Pitfalls\n\n1. **Using `skill_manage(action='create')` for an in-repo skill.** It writes to `~\u002F.hermes\u002Fskills\u002F`, not the repo tree. Use `write_file` for in-repo creation.\n\n2. **Leading whitespace before `---`.** The validator checks `content.startswith(\"---\")`; any leading blank line or BOM fails validation.\n\n3. **Description too generic.** Peer descriptions start with \"Use when ...\" and describe the *trigger class*, not the one task. \"Use when debugging X\" > \"Debug X\".\n\n4. **Forgetting the author\u002Flicense\u002Fmetadata block.** Not validator-enforced, but every peer has it; omitting makes the skill look half-finished.\n\n5. **Writing a skill that duplicates a peer.** Before creating, `ls skills\u002F\u003Ccategory>\u002F` and open 2-3 peers. Prefer extending an existing skill to creating a narrow sibling.\n\n6. **Expecting the current session to see the new skill.** It won't. The skill loader is initialized at session start. Verify in a fresh session or via `skill_view` using the exact path.\n\n7. **Letting skills accumulate sediment.** A skill should get shorter or sharper over time. When adding a rule, remove the old wording it replaces; don't layer advice forever.\n\n8. **Writing no-op prose.** \"Be careful,\" \"be thorough,\" and \"use best practices\" rarely change model behavior. Replace with a checkable completion criterion or a stronger leading word.\n\n9. **Linking to skills that don't exist in-repo.** `related_skills: [some-user-local-skill]` works for you but breaks for other clones. Prefer only in-repo links.\n\n## Verification Checklist\n\n- [ ] File is at `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` (not in `~\u002F.hermes\u002Fskills\u002F`)\n- [ ] Frontmatter starts at byte 0 with `---`, closes with `\\n---\\n`\n- [ ] `name`, `description`, `version`, `author`, `license`, `metadata.hermes.{tags, related_skills}` all present\n- [ ] Name ≤ 64 chars, lowercase + hyphens\n- [ ] Description ≤ 1024 chars and starts with \"Use when ...\"\n- [ ] Total file ≤ 100,000 chars (aim for 8-15k)\n- [ ] Structure: `# Title` → `## Overview` → `## When to Use` → body → `## Common Pitfalls` → `## Verification Checklist`\n- [ ] Each ordered step has a checkable completion criterion\n- [ ] Description is trigger-focused and avoids duplicated body content\n- [ ] Bulky or branch-specific reference is progressively disclosed in linked files\n- [ ] No-op prose and duplicated rules removed\n- [ ] `related_skills` references resolve in-repo (or are explicitly OK to be user-local)\n- [ ] `git add skills\u002F\u003Ccategory>\u002F\u003Cname>\u002F && git commit` completed on the intended branch\n","# Authoring Hermes-Agent Skills (in-repo)\n\n## Overview\n\nThere are two places a SKILL.md can live:\n\n1. **User-local:** `~\u002F.hermes\u002Fskills\u002F\u003Cmaybe-category>\u002F\u003Cname>\u002FSKILL.md` — personal, not shared. Created via `skill_manage(action='create')`.\n2. **In-repo (this skill is about this case):** `~\u002Fhermes-agent\u002Fskills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` — committed, shipped with the package. Use `write_file` + `git add`. `skill_manage(action='create')` does NOT target this tree.\n\n## When to Use\n\n- User asks you to add a skill \"in this branch \u002F repo \u002F commit\"\n- You're committing a reusable workflow that should ship with hermes-agent\n- You're editing an existing skill under `~\u002Fhermes-agent\u002Fskills\u002F` (use `patch` for small edits, `write_file` for rewrites; `skill_manage` still works for patch on in-repo skills, but not for `create`)\n\n## Required Frontmatter\n\nSource of truth: `tools\u002Fskill_manager_tool.py::_validate_frontmatter`. Hard requirements:\n\n- Starts with `---` as the first bytes (no leading blank line).\n- Closes with `\\n---\\n` before the body.\n- Parses as a YAML mapping.\n- `name` field present.\n- `description` field present, ≤ **1024 chars** (`MAX_DESCRIPTION_LENGTH`).\n- Non-empty body after the closing `---`.\n\nPeer-matched shape used by every skill under `skills\u002Fsoftware-development\u002F`:\n\n```yaml\n---\nname: my-skill-name               # lowercase, hyphens, ≤64 chars (MAX_NAME_LENGTH)\ndescription: Use when \u003Ctrigger>. \u003Cone-line behavior>.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [short, descriptive, tags]\n    related_skills: [other-skill, another-skill]\n---\n```\n\n`version` \u002F `author` \u002F `license` \u002F `metadata` are NOT enforced by the validator, but every peer has them — omit and your skill sticks out.\n\n## Size Limits\n\n- Description: ≤ 1024 chars (enforced).\n- Full SKILL.md: ≤ 100,000 chars (enforced as `MAX_SKILL_CONTENT_CHARS`, ~36k tokens).\n- Peer skills in `software-development\u002F` sit at **8-14k chars**. Aim for that range. If you're pushing past 20k, split into `references\u002F*.md` and reference them from SKILL.md.\n\n## Writing Quality Principles\n\nA skill exists to make the agent's process more predictable. Predictability does **not** mean identical output every run; it means the agent reliably follows the same useful discipline.\n\nUse these quality checks when writing or editing any skill:\n\n1. **Optimize for process predictability.** Ask: what behavior should change when this skill loads? If a line does not change behavior, cut it.\n2. **Choose the right context load.** A model-invoked Hermes skill pays for its description every turn. Keep descriptions focused on trigger classes and the skill's distinctive behavior. Put details in the body or linked references.\n3. **Use an information hierarchy.** Put always-needed steps in `SKILL.md`; put branch-specific or bulky reference material in `references\u002F`, `templates\u002F`, or `scripts\u002F` and point to it only when needed.\n4. **End steps with completion criteria.** Each ordered step should say how the agent knows it is done. Good criteria are checkable and, when it matters, exhaustive: \"every modified file accounted for\" beats \"summarize changes.\"\n5. **Co-locate rules with the concept they govern.** Avoid scattering one idea across the file. Keep definition, caveats, examples, and verification near each other.\n6. **Use strong leading words.** Prefer compact concepts the model already knows — e.g. \"tight loop,\" \"tracer bullet,\" \"root cause,\" \"regression test\" — over long repeated explanations. A good leading word saves tokens and anchors behavior.\n7. **Prune duplication and no-ops.** Keep each meaning in one source of truth. Sentence by sentence, ask whether the sentence changes agent behavior versus the default. If not, delete it rather than polishing it.\n8. **Watch for premature completion.** If agents tend to rush a step, first sharpen that step's completion criterion. Split the sequence only when later steps distract from doing the current step well.\n\nCommon quality failures:\n\n- **Premature completion** — the skill lets the agent move on before the work is genuinely done.\n- **Duplication** — the same rule appears in multiple places and drifts.\n- **Sediment** — stale lines remain because adding felt safer than deleting.\n- **Sprawl** — too much always-visible material; push branch-specific reference behind pointers.\n- **No-op prose** — generic advice the agent would already follow without the skill.\n\n## Peer-Matched Structure\n\nEvery in-repo skill follows roughly:\n\n```\n# \u003CTitle>\n\n## Overview\nOne or two paragraphs: what and why.\n\n## When to Use\n- Bulleted triggers\n- \"Don't use for:\" counter-triggers\n\n## \u003CTopic sections specific to the skill>\n- Quick-reference tables are common\n- Code blocks with exact commands\n- Hermes-specific recipes (tests via scripts\u002Frun_tests.sh, ui-tui paths, etc.)\n\n## Common Pitfalls\nNumbered list of mistakes and their fixes.\n\n## Verification Checklist\n- [ ] Checkbox list of post-action verifications\n\n## One-Shot Recipes (optional)\nNamed scenarios → concrete command sequences.\n```\n\nNot every section is mandatory, but `Overview` + `When to Use` + actionable body + pitfalls are the minimum for the skill to feel like a peer.\n\n## Directory Placement\n\n```\nskills\u002F\u003Ccategory>\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\nCategories currently in repo (confirm with `ls skills\u002F`): `autonomous-ai-agents`, `creative`, `data-science`, `devops`, `dogfood`, `email`, `gaming`, `github`, `leisure`, `mcp`, `media`, `mlops\u002F*`, `note-taking`, `productivity`, `red-teaming`, `research`, `smart-home`, `social-media`, `software-development`.\n\nPick the closest existing category. Don't invent new top-level categories casually.\n\n## Workflow\n\n1. **Survey peers** in the target category:\n   ```\n   ls skills\u002F\u003Ccategory>\u002F\n   ```\n   Read 2-3 peer SKILL.md files to match tone and structure.\n2. **Check validator constraints** in `tools\u002Fskill_manager_tool.py` if unsure.\n3. **Draft** with `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md`.\n4. **Validate locally.** Use the repository\u002FHermes virtualenv interpreter that already provides PyYAML; a host system Python may not include `yaml`. Do not install PyYAML globally just for this check. If the project environment is unavailable, use Hermes's built-in skill loader\u002Fvalidator or a dependency-free parser for the required top-level fields.\n\n   ```python\n   import yaml, re, pathlib\n   content = pathlib.Path(\"skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md\").read_text()\n   assert content.startswith(\"---\")\n   m = re.search(r'\\n---\\s*\\n', content[3:])\n   fm = yaml.safe_load(content[3:m.start()+3])\n   assert \"name\" in fm and \"description\" in fm\n   assert len(fm[\"description\"]) \u003C= 1024\n   assert len(content) \u003C= 100_000\n   ```\n5. **Git add + commit** on the active branch.\n6. **Note:** the CURRENT session's skill loader is cached — `skill_view` \u002F `skills_list` will not see the new skill until a new session. This is expected, not a bug.\n\n## Cross-Referencing Other Skills\n\n`metadata.hermes.related_skills` unions both trees (`skills\u002F` in-repo and `~\u002F.hermes\u002Fskills\u002F`) at load time. You CAN reference a user-local skill from an in-repo skill, but it won't resolve for other users who clone the repo fresh. Prefer referencing only in-repo skills from in-repo skills. If a frequently-referenced skill lives only in `~\u002F.hermes\u002Fskills\u002F`, consider promoting it to the repo.\n\n## Editing Existing In-Repo Skills\n\n- **Small fix (typo, added pitfall, tightened trigger):** `skill_manage(action='patch', name=..., old_string=..., new_string=...)` works fine on in-repo skills.\n- **Major rewrite:** `write_file` the whole SKILL.md. `skill_manage(action='edit')` also works but requires supplying the full new content.\n- **Adding supporting files:** `write_file` to `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002Freferences\u002F\u003Cfile>.md`, `templates\u002F\u003Cfile>`, or `scripts\u002F\u003Cfile>`. `skill_manage(action='write_file')` also works and enforces the references\u002Ftemplates\u002Fscripts\u002Fassets subdir allowlist.\n- **Always commit** the edit — in-repo skills are source, not runtime state.\n\n## Common Pitfalls\n\n1. **Using `skill_manage(action='create')` for an in-repo skill.** It writes to `~\u002F.hermes\u002Fskills\u002F`, not the repo tree. Use `write_file` for in-repo creation.\n\n2. **Leading whitespace before `---`.** The validator checks `content.startswith(\"---\")`; any leading blank line or BOM fails validation.\n\n3. **Description too generic.** Peer descriptions start with \"Use when ...\" and describe the *trigger class*, not the one task. \"Use when debugging X\" > \"Debug X\".\n\n4. **Forgetting the author\u002Flicense\u002Fmetadata block.** Not validator-enforced, but every peer has it; omitting makes the skill look half-finished.\n\n5. **Writing a skill that duplicates a peer.** Before creating, `ls skills\u002F\u003Ccategory>\u002F` and open 2-3 peers. Prefer extending an existing skill to creating a narrow sibling.\n\n6. **Expecting the current session to see the new skill.** It won't. The skill loader is initialized at session start. Verify in a fresh session or via `skill_view` using the exact path.\n\n7. **Letting skills accumulate sediment.** A skill should get shorter or sharper over time. When adding a rule, remove the old wording it replaces; don't layer advice forever.\n\n8. **Writing no-op prose.** \"Be careful,\" \"be thorough,\" and \"use best practices\" rarely change model behavior. Replace with a checkable completion criterion or a stronger leading word.\n\n9. **Linking to skills that don't exist in-repo.** `related_skills: [some-user-local-skill]` works for you but breaks for other clones. Prefer only in-repo links.\n\n## Verification Checklist\n\n- [ ] File is at `skills\u002F\u003Ccategory>\u002F\u003Cname>\u002FSKILL.md` (not in `~\u002F.hermes\u002Fskills\u002F`)\n- [ ] Frontmatter starts at byte 0 with `---`, closes with `\\n---\\n`\n- [ ] `name`, `description`, `version`, `author`, `license`, `metadata.hermes.{tags, related_skills}` all present\n- [ ] Name ≤ 64 chars, lowercase + hyphens\n- [ ] Description ≤ 1024 chars and starts with \"Use when ...\"\n- [ ] Total file ≤ 100,000 chars (aim for 8-15k)\n- [ ] Structure: `# Title` → `## Overview` → `## When to Use` → body → `## Common Pitfalls` → `## Verification Checklist`\n- [ ] Each ordered step has a checkable completion criterion\n- [ ] Description is trigger-focused and avoids duplicated body content\n- [ ] Bulky or branch-specific reference is progressively disclosed in linked files\n- [ ] No-op prose and duplicated rules removed\n- [ ] `related_skills` references resolve in-repo (or are explicitly OK to be user-local)\n- [ ] `git add skills\u002F\u003Ccategory>\u002F\u003Cname>\u002F && git commit` completed on the intended branch\n",{"name":5,"author":23,"license":14,"version":24,"metadata":25,"platforms":36,"description":7},"Hermes Agent","1.1.0",{"hermes":26},{"tags":27,"related_skills":33},[28,29,30,31,32],"skills","authoring","hermes-agent","conventions","skill-md",[34,35],"plan","requesting-code-review",[37,38,39],"linux","macos","windows","main","81189f70e1089f9b3a944ffc480e6887efd831b9","devbox\u002Fprofiles\u002Fplanner\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes","https:\u002F\u002Fgithub.com\u002Fdarkmatter","dm.sh","2026-09-14 08:11:52",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add darkmatter\u002Fhermes --skill hermes-agent-skill-authoring",{"tool":53,"command":54},"bunx","bunx skills add darkmatter\u002Fhermes --skill hermes-agent-skill-authoring",{"tool":56,"command":57},"pnpm","pnpm dlx skills add darkmatter\u002Fhermes --skill hermes-agent-skill-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fdevbox\u002Fprofiles\u002Fplanner\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",true,[],[62,68,75,82,89,96],{"skillNo":63,"name":34,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7BMC2PYBVXM6FQEZMBQZB4G","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7BMBSEKDVQ09Z666RCWT7BR","monorepo-fleet-sync","Sync docs and configs when a Flue monorepo fleet changes.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Fmonorepo-fleet-sync\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7BMBNWFJT2TJZ2AKA64GEV9","inspecting-hermes-desktop-dom","Read the live Hermes desktop DOM\u002FCSS over CDP.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fsoftware-development\u002Finspecting-hermes-desktop-dom\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7BMAZM4VJ97K7JD0FDN58M8","grounded-citations","Ground answers and documents in cited, verifiable sources.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7BMATPEDZ4BPP67Y4ZS0BMM","competitor-news-monitor","Watch named companies for material news; cited digests.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fcompetitor-news-monitor\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7BMAQZV7YFA2SFPT7HCVCTX","blocked-page-recovery","Recover blocked\u002Fpaywalled\u002FWAF'd pages via fallbacks.","https:\u002F\u002Fgithub.com\u002Fdarkmatter\u002Fhermes\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fblocked-page-recovery\u002FSKILL.md",[],[]]