[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74K5WD7CZR78PRBQQB64VR8":3,"skill-same:01M74K5WD7CZR78PRBQQB64VR8":56},{"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":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M74K5WD7CZR78PRBQQB64VR8","hermes-agent-skill-authoring",null,"Author in-repo SKILL.md: frontmatter, validator, structure.","LyrikNilpferd71\u002FHermes-Backup","LyrikNilpferd71","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F187173780?v=4","01M727S8GPB77P0S9ECRRMZT58","01M727S8HF63B0MD53F496MK1V",0,"MIT","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-06-21T14-01-19+0200\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: hermes-agent-skill-authoring\ndescription: \"Author in-repo SKILL.md: frontmatter, validator, structure.\"\nversion: 1.0.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [skills, authoring, hermes-agent, conventions, skill-md]\n    related_skills: [writing-plans, 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):** `\u002Fhome\u002Fbb\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 `\u002Fhome\u002Fbb\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.0.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## 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**:\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. **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- [ ] `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):** `\u002Fhome\u002Fbb\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 `\u002Fhome\u002Fbb\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.0.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## 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**:\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. **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- [ ] `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,"description":7},"Hermes Agent","1.0.0",{"hermes":26},{"tags":27,"related_skills":33},[28,29,30,31,32],"skills","authoring","hermes-agent","conventions","skill-md",[34,35],"writing-plans","requesting-code-review","main","404fd33aabef3b6bc1cc913117ba2160ade62625","snapshots\u002F2026-06-21T14-01-19+0200\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71","2026-11-08 20:00:57",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add LyrikNilpferd71\u002FHermes-Backup --skill hermes-agent-skill-authoring",{"tool":48,"command":49},"bunx","bunx skills add LyrikNilpferd71\u002FHermes-Backup --skill hermes-agent-skill-authoring",{"tool":51,"command":52},"pnpm","pnpm dlx skills add LyrikNilpferd71\u002FHermes-Backup --skill hermes-agent-skill-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-06-21T14-01-19+0200\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",true,[],[57,64,71,78,85,91],{"skillNo":58,"name":34,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":63},"01M76BBCCNA7WQ82Q8QNZH8PBK","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":63},"01M76BB8YS41CA3NKW0YMSSB88","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":63},"01M76BB680FPNT998E1GM2QW10","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"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":63},"01M76BB3C4ZB9S4RWPMM8MX0YB","plan","Write a markdown plan to .hermes\u002Fplans\u002F; no execution.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],{"skillNo":86,"name":5,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":63},"01M76BB0NK28KMP51YDB5R3EXA","Author in-repo SKILL.md files: frontmatter and structure.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":63},"01M76BAYV58H0CKNSTZE3ZH4NY","debugging-hermes-tui-commands","Debug Hermes TUI slash commands: Python, gateway, Ink UI.","https:\u002F\u002Fgithub.com\u002FLyrikNilpferd71\u002FHermes-Backup\u002Fblob\u002Fmain\u002Fsnapshots\u002F2026-11-08T13-00-51+0100\u002Fskills\u002Fsoftware-development\u002Fdebugging-hermes-tui-commands\u002FSKILL.md",[],[]]