[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71TDMVXDFQD5N1FBYY899PP":3,"skill-same:01M71TDMVXDFQD5N1FBYY899PP":76},{"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":22,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":13,"repositoryHtmlUrl":59,"repositoryHomepageUrl":6,"ownerHtmlUrl":60,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M71TDMVXDFQD5N1FBYY899PP","hermes-agent-skill-authoring",null,"Author in-repo SKILL.md: frontmatter, validator, structure.","eliottbusiness\u002FDeptFlow-Agent","eliottbusiness","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263418316?v=4","01M71T5T608RHFA07W6QVC6TYX","01M71T5T6R98RMYZ53PYH851T1",0,"MIT","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"skill authoring","authoring","hermes","agent skill","hermes agent","hermes agent skill authoring","frontmatter","conventions","hermes-agent","structure","review","author","code-review","code","writing","plans","skill-md","repo","validator","2026-11-10 13:02:02",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":47,"license":14,"version":48,"metadata":49,"description":7},"Hermes Agent","1.0.0",{"hermes":50},{"tags":51,"related_skills":53},[52,24,31,30,39],"skills",[54,55],"writing-plans","requesting-code-review","main","3ffb682eba417bd920665a7146fecc206b3bccf8","profile\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent","https:\u002F\u002Fgithub.com\u002Feliottbusiness","2026-05-03 19:19:17",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add eliottbusiness\u002FDeptFlow-Agent --skill hermes-agent-skill-authoring",{"tool":68,"command":69},"bunx","bunx skills add eliottbusiness\u002FDeptFlow-Agent --skill hermes-agent-skill-authoring",{"tool":71,"command":72},"pnpm","pnpm dlx skills add eliottbusiness\u002FDeptFlow-Agent --skill hermes-agent-skill-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fhermes-agent-skill-authoring\u002FSKILL.md",true,[],[77,112,137,153,170,194],{"skillNo":78,"name":54,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":96,"publishedAt":42},"01M71TEDB3XPT9H5R3SH05XWES","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[82,85,88,93],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[37,97,38,98,99,100,101,102,36,103,104,35,33,105,106,107,108,109,110,111],"writing plans","test-driven","test-driven-development","superpowers","design","workflow","tasks","subagent","documentation","write","paths","planning","development","test","implementation",{"skillNo":113,"name":99,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":123,"publishedAt":42},"01M71TEB43BNQKKCRMQZDZ7SAQ","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[117,120],{"categoryNo":118,"categoryName":119,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":121,"categoryName":122,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",[124,109,110,125,126,127,128,100,37,129,36,104,130,131,132,133,134,38,135,136],"test driven development","driven","green","red-green-refactor","testing","debugging","systematic","refactor","systematic-debugging","enforce","tests","tdd","quality",{"skillNo":138,"name":132,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":42},"01M71TE76KV9R1WY1V5XQXMMTJ","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[142],{"categoryNo":121,"categoryName":122,"taxonomyType":20,"taxonomyTypeDesc":21},[144,129,130,98,145,146,99,100,37,104,147,148,109,149,38,150,110,151,152,25],"systematic debugging","problem","problem-solving","phase","bugs","root cause","root-cause","investigation","understand",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":42},"01M71TE2Y2TRFZNT6YRPKQA33R","subagent-driven-development","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[159,160,161],{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":94,"categoryName":95,"taxonomyType":91,"taxonomyTypeDesc":92},[163,104,109,125,98,99,164,165,100,37,102,36,35,33,166,167,38,168,169,110],"subagent driven development","delegate","delegation","subagents","parallel","stage","task",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":42},"01M71TE0E7WRGXY6N0WTMDXY23","spike","Throwaway experiments to validate an idea before build.","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Fspike\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[172,180,181,182,108,109,38,183,184,37,185,186,104,187,188,189,190,191,192,193],"concept","exploration","get","throwaway","shit","proof-of-concept","done","prototype","plan","research","build","sketch","mvp","validate",{"skillNo":195,"name":55,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":201,"publishedAt":42},"01M71TDY3JXZHWSYNF3AZ2XM2D","Pre-commit review: security scan, quality gates, auto-fix.","https:\u002F\u002Fgithub.com\u002Feliottbusiness\u002FDeptFlow-Agent\u002Fblob\u002Fmain\u002Fprofile\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[199,200],{"categoryNo":118,"categoryName":119,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[202,203,36,33,98,99,204,205,100,206,37,207,208,104,35,209,210,109,211,38],"code review","requesting code review","fix","auto-fix","auto","security scan","commit","verification","security","scan"]