[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MMN1EM46A2NFSHG61D37J":3,"skill-same:01M77MMN1EM46A2NFSHG61D37J":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":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M77MMN1EM46A2NFSHG61D37J","skill-authoring",null,"Author SKILL.md skills: frontmatter, validator limits, structure.","pan-hh\u002Fmateclaw-hybrid","pan-hh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F244917262?v=4","01M77MGAQE06HNBEHKYN7180V6","01M77MGARJ7JXWZYKA9RMM968R",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fskill-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-authoring\ndescription: 'Author SKILL.md skills: frontmatter, validator limits, structure.'\nversion: 1.0.0\ntags:\n- skills\n- authoring\n- skill-md\n- conventions\n- meta\nauthor: ported\n---\n# Authoring MateClaw Skills\n\n## Overview\n\nA skill is a `SKILL.md` file — YAML frontmatter plus a markdown body of reusable instructions. There are two places a SKILL.md can live, and they have different creation paths:\n\n1. **Builtin (in-repo):** `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cname>\u002FSKILL.md` — committed, shipped inside the server JAR. On every startup `BuiltinSkillSeedService` scans `classpath*:skills\u002F*\u002FSKILL.md`, parses each frontmatter, and upserts a row into `mate_skill` keyed by `name`. The SKILL.md is the single source of truth — no SQL seed entry is required.\n2. **Custom (runtime):** created by an agent or user through the `skill_manage` tool. Stored as a `mate_skill` row with `skill_type=custom` and exported to the workspace at `~\u002F.mateclaw\u002Fskills\u002F\u003Cname>\u002F`. Not committed; lives per-installation.\n\nThis skill covers both. Note that `skill_manage` does NOT write into the in-repo `skills\u002F` tree — builtin skills are authored by writing the file directly and restarting.\n\n## When to Use\n\n- You're adding a reusable workflow that should ship with MateClaw → builtin.\n- You're editing an existing builtin skill under `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F`.\n- An agent finished a complex task and wants to persist the approach → custom, via `skill_manage`.\n- You're reviewing a SKILL.md for correct frontmatter and structure.\n\n**Don't use for:** recording a one-off tip discovered while *using* a skill (that belongs in `record_lesson` \u002F a per-skill LESSONS.md) or cross-skill memory notes (`remember`). This skill is about writing the skill document itself.\n\n## Required Frontmatter\n\nThe frontmatter is parsed by `SkillFrontmatterParser`: a regex (`^---\\s*\\n(.*?)\\n---\\s*\\n(.*)$`) splits the fenced block, then SnakeYAML loads it as a mapping. Hard requirements:\n\n- Starts with `---` as the **first bytes** — no leading blank line, no BOM.\n- A closing `---` line follows, then the body. The body must be non-empty.\n- The block between the fences parses as a YAML mapping.\n- `name` is present — it is the upsert key. `BuiltinSkillSeedService` skips any SKILL.md with no `name`.\n- `description` is present — a single line.\n\nIf the frontmatter regex fails to match, the parser treats the whole file as body with an empty `name`, and a builtin skill is silently skipped at seed time. A loadable skill ALWAYS has well-formed frontmatter.\n\n## Size & Naming Limits\n\n- **Skill content:** ≤ 100,000 chars (`MAX_CONTENT_CHARS`, ~25k tokens) — enforced by `skill_manage` for custom skills. Builtin skills aren't hard-checked but should obey the same ceiling.\n- **Name:** must match `^[a-z0-9][a-z0-9._-]{0,63}$` — lowercase letters and digits plus `-` `_` `.`, starting with a letter or digit, ≤ 64 chars. `skill_manage` lowercases the name before validating.\n- **Description:** keep it to one line. Peer skills run 40-70 chars — a tight trigger phrase, not a paragraph.\n- **Peer skills** in `resources\u002Fskills\u002F` sit at 6-15k chars. Aim for that range; past ~20k, split detail into `references\u002F*.md`.\n\n## Peer-Matched Frontmatter\n\nEvery shipped skill follows this shape:\n\n```yaml\n---\nname: my-skill-name\ndescription: 'One line: what it does and when it fires.'\nversion: 1.0.0\ntags:\n- short\n- descriptive\n- tags\nauthor: ported\n---\n```\n\nFields `BuiltinSkillSeedService` projects onto the `mate_skill` row:\n\n| Field | Effect | Default if absent |\n|---|---|---|\n| `name` | upsert key, skill identity | — (required) |\n| `description` | shown in skill lists | empty |\n| `version` | `mate_skill.version` | `1.0.0` |\n| `icon` | emoji, or a `\u002Fskill-assets\u002F...` path | `🛠️` |\n| `author` | attribution | `MateClaw` |\n| `tags` | YAML list or CSV string | skill name |\n| `nameZh` \u002F `nameEn` | bilingual display names | none |\n| `optional: true` | seeds the skill **disabled** — user opts in from the Skills page | `false` (enabled) |\n| `dependencies.tools` | required tool ids → `config_json.requiredTools` | none |\n| `platforms` | e.g. `[linux, macos, windows]` | none |\n\n`version` \u002F `author` \u002F `tags` are not validator-enforced, but every peer carries them — omitting makes the skill look half-finished. Use `optional: true` for heavyweight skills (paid CLI dependencies, external OAuth, niche integrations) so they ship dark and the user activates them deliberately.\n\n## Skill Structure\n\nShipped skills follow roughly:\n\n```\n# \u003CTitle>\n\n## Overview          — one or two paragraphs: what and why.\n## When to Use       — bulleted triggers, plus a \"Don't use for:\" counter-trigger.\n## \u003CTopic sections>  — quick-reference tables, exact commands, concrete recipes\n                       (mvn test, paths under mateclaw-server\u002F, etc.).\n## Common Pitfalls   — numbered mistakes paired with their fixes.\n## Verification Checklist — checkbox list of post-action checks.\n```\n\nNot every section is mandatory, but `Overview` + `When to Use` + an actionable body + `Common Pitfalls` is the minimum for the skill to read like a peer.\n\n## Directory Placement\n\n```\nmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\nThe `skills\u002F` tree is **flat** — no category subdirectories. The seed glob `classpath*:skills\u002F*\u002FSKILL.md` matches exactly one level deep, so a skill nested under a category directory would never be scanned. The directory name SHOULD equal the frontmatter `name`. Supporting files go in `references\u002F` and `scripts\u002F` subdirectories (see below).\n\n## Builtin Workflow (in-repo)\n\n1. **Survey peers:** `ls mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F` and read 2-3 SKILL.md files close to your topic — match tone and structure.\n2. **Create** `skills\u002F\u003Cname>\u002FSKILL.md` with the file tools.\n3. **Validate** that the frontmatter parses — see the checklist below.\n4. **Restart the server.** `BuiltinSkillSeedService` seeds the new row only at startup; a running server will not see it. The service also skips re-seeding when no SKILL.md's size\u002Fmtime changed, so rebuilding the JAR is what makes a change land.\n5. **Commit** the new `skills\u002F\u003Cname>\u002F` directory. No SQL seed change is needed — the SKILL.md is the source of truth and obsoletes per-skill `INSERT INTO mate_skill`.\n\n## Custom Workflow (skill_manage)\n\nAgents and users create runtime skills with the `skill_manage` tool — actions `create | edit | patch | delete`:\n\n- `create` — a new skill from full SKILL.md content. Rejects a duplicate name.\n- `edit` — a full-content rewrite of a custom skill.\n- `patch` — find-and-replace one section (`oldText` → `newText`).\n- `delete` — uninstall (logical delete plus workspace archive).\n\nNotes:\n\n- Every write is **security-scanned** (`SkillSecurityService`) before saving — dangerous patterns are rejected with the reason. Builtin SKILL.md files are NOT scanned; they are trusted committed source.\n- `edit` \u002F `patch` \u002F `delete` **refuse builtin skills** (\"cannot edit builtin skill\"). To change a builtin skill, edit the resource file and restart.\n- A custom skill is live immediately — the tool re-runs the resolver pipeline — so no restart is needed.\n\n## Supporting Files\n\nBeyond `SKILL.md`, a skill directory may carry:\n\n- `references\u002F*.md` — long-form material the body links to. Use this to keep SKILL.md under ~20k chars.\n- `scripts\u002F*` — executable helpers a skill invokes.\n- `templates\u002F`, `assets\u002F` — used by some bundled skills (HTML templates, images, etc.).\n\n`SkillFileAccessPolicy` only resolves runtime paths under `references\u002F` and `scripts\u002F`, and rejects `..` traversal or absolute paths — keep runtime-read files in those two directories.\n\n## Common Pitfalls\n\n1. **Leading whitespace before `---`.** The frontmatter regex anchors on `^---`; a blank line or BOM makes the whole file parse as body with an empty `name`, and a builtin skill is silently skipped.\n2. **Expecting a running server to see a new builtin skill.** `BuiltinSkillSeedService` seeds only at startup. Restart — or, for a quick iteration, create a custom skill via `skill_manage`, which is live immediately.\n3. **Trying to `skill_manage edit` a builtin skill.** It is refused. Builtin skills are committed source — edit the file and restart.\n4. **Adding an `INSERT INTO mate_skill` for a new builtin skill.** Unnecessary and discouraged — the SKILL.md is the source of truth and the seed service upserts by `name`.\n5. **Generic description.** \"Debug things\" is weak. A peer description names the *trigger* — \"4-phase root cause debugging: understand bugs before fixing.\" beats \"Debug things.\"\n6. **Naming an external project or internal RFC in the skill body.** Describe the function objectively. Shipped content states *what* it does, not where the idea came from — `author: ported` is the neutral attribution for an adapted skill.\n7. **Skill content over 100k chars.** `skill_manage` rejects it outright; split detail into `references\u002F`.\n8. **Mismatched directory and `name`.** The upsert keys on the frontmatter `name`, but a directory that disagrees confuses everyone reading the tree. Keep them equal.\n\n## Verification Checklist\n\n- [ ] File at `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (builtin); the directory name equals the frontmatter `name`\n- [ ] Frontmatter starts at byte 0 with `---`, closes with a `---` line, and the body is non-empty\n- [ ] `name` matches `^[a-z0-9][a-z0-9._-]{0,63}$`; `description` is a single line\n- [ ] `version`, `tags`, `author` present (peer-matched shape)\n- [ ] Total file ≤ 100,000 chars (aim 6-15k; split into `references\u002F` past ~20k)\n- [ ] Structure: `# Title` → `## Overview` → `## When to Use` → actionable body → `## Common Pitfalls` → `## Verification Checklist`\n- [ ] No external project names or RFC numbers in the body\n- [ ] Builtin: server restarted so `BuiltinSkillSeedService` seeds the row; the new `skills\u002F\u003Cname>\u002F` directory is committed\n- [ ] Custom: created via `skill_manage`, security scan reported PASSED\n","# Authoring MateClaw Skills\n\n## Overview\n\nA skill is a `SKILL.md` file — YAML frontmatter plus a markdown body of reusable instructions. There are two places a SKILL.md can live, and they have different creation paths:\n\n1. **Builtin (in-repo):** `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cname>\u002FSKILL.md` — committed, shipped inside the server JAR. On every startup `BuiltinSkillSeedService` scans `classpath*:skills\u002F*\u002FSKILL.md`, parses each frontmatter, and upserts a row into `mate_skill` keyed by `name`. The SKILL.md is the single source of truth — no SQL seed entry is required.\n2. **Custom (runtime):** created by an agent or user through the `skill_manage` tool. Stored as a `mate_skill` row with `skill_type=custom` and exported to the workspace at `~\u002F.mateclaw\u002Fskills\u002F\u003Cname>\u002F`. Not committed; lives per-installation.\n\nThis skill covers both. Note that `skill_manage` does NOT write into the in-repo `skills\u002F` tree — builtin skills are authored by writing the file directly and restarting.\n\n## When to Use\n\n- You're adding a reusable workflow that should ship with MateClaw → builtin.\n- You're editing an existing builtin skill under `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F`.\n- An agent finished a complex task and wants to persist the approach → custom, via `skill_manage`.\n- You're reviewing a SKILL.md for correct frontmatter and structure.\n\n**Don't use for:** recording a one-off tip discovered while *using* a skill (that belongs in `record_lesson` \u002F a per-skill LESSONS.md) or cross-skill memory notes (`remember`). This skill is about writing the skill document itself.\n\n## Required Frontmatter\n\nThe frontmatter is parsed by `SkillFrontmatterParser`: a regex (`^---\\s*\\n(.*?)\\n---\\s*\\n(.*)$`) splits the fenced block, then SnakeYAML loads it as a mapping. Hard requirements:\n\n- Starts with `---` as the **first bytes** — no leading blank line, no BOM.\n- A closing `---` line follows, then the body. The body must be non-empty.\n- The block between the fences parses as a YAML mapping.\n- `name` is present — it is the upsert key. `BuiltinSkillSeedService` skips any SKILL.md with no `name`.\n- `description` is present — a single line.\n\nIf the frontmatter regex fails to match, the parser treats the whole file as body with an empty `name`, and a builtin skill is silently skipped at seed time. A loadable skill ALWAYS has well-formed frontmatter.\n\n## Size & Naming Limits\n\n- **Skill content:** ≤ 100,000 chars (`MAX_CONTENT_CHARS`, ~25k tokens) — enforced by `skill_manage` for custom skills. Builtin skills aren't hard-checked but should obey the same ceiling.\n- **Name:** must match `^[a-z0-9][a-z0-9._-]{0,63}$` — lowercase letters and digits plus `-` `_` `.`, starting with a letter or digit, ≤ 64 chars. `skill_manage` lowercases the name before validating.\n- **Description:** keep it to one line. Peer skills run 40-70 chars — a tight trigger phrase, not a paragraph.\n- **Peer skills** in `resources\u002Fskills\u002F` sit at 6-15k chars. Aim for that range; past ~20k, split detail into `references\u002F*.md`.\n\n## Peer-Matched Frontmatter\n\nEvery shipped skill follows this shape:\n\n```yaml\n---\nname: my-skill-name\ndescription: 'One line: what it does and when it fires.'\nversion: 1.0.0\ntags:\n- short\n- descriptive\n- tags\nauthor: ported\n---\n```\n\nFields `BuiltinSkillSeedService` projects onto the `mate_skill` row:\n\n| Field | Effect | Default if absent |\n|---|---|---|\n| `name` | upsert key, skill identity | — (required) |\n| `description` | shown in skill lists | empty |\n| `version` | `mate_skill.version` | `1.0.0` |\n| `icon` | emoji, or a `\u002Fskill-assets\u002F...` path | `🛠️` |\n| `author` | attribution | `MateClaw` |\n| `tags` | YAML list or CSV string | skill name |\n| `nameZh` \u002F `nameEn` | bilingual display names | none |\n| `optional: true` | seeds the skill **disabled** — user opts in from the Skills page | `false` (enabled) |\n| `dependencies.tools` | required tool ids → `config_json.requiredTools` | none |\n| `platforms` | e.g. `[linux, macos, windows]` | none |\n\n`version` \u002F `author` \u002F `tags` are not validator-enforced, but every peer carries them — omitting makes the skill look half-finished. Use `optional: true` for heavyweight skills (paid CLI dependencies, external OAuth, niche integrations) so they ship dark and the user activates them deliberately.\n\n## Skill Structure\n\nShipped skills follow roughly:\n\n```\n# \u003CTitle>\n\n## Overview          — one or two paragraphs: what and why.\n## When to Use       — bulleted triggers, plus a \"Don't use for:\" counter-trigger.\n## \u003CTopic sections>  — quick-reference tables, exact commands, concrete recipes\n                       (mvn test, paths under mateclaw-server\u002F, etc.).\n## Common Pitfalls   — numbered mistakes paired with their fixes.\n## Verification Checklist — checkbox list of post-action checks.\n```\n\nNot every section is mandatory, but `Overview` + `When to Use` + an actionable body + `Common Pitfalls` is the minimum for the skill to read like a peer.\n\n## Directory Placement\n\n```\nmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cskill-name>\u002FSKILL.md\n```\n\nThe `skills\u002F` tree is **flat** — no category subdirectories. The seed glob `classpath*:skills\u002F*\u002FSKILL.md` matches exactly one level deep, so a skill nested under a category directory would never be scanned. The directory name SHOULD equal the frontmatter `name`. Supporting files go in `references\u002F` and `scripts\u002F` subdirectories (see below).\n\n## Builtin Workflow (in-repo)\n\n1. **Survey peers:** `ls mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F` and read 2-3 SKILL.md files close to your topic — match tone and structure.\n2. **Create** `skills\u002F\u003Cname>\u002FSKILL.md` with the file tools.\n3. **Validate** that the frontmatter parses — see the checklist below.\n4. **Restart the server.** `BuiltinSkillSeedService` seeds the new row only at startup; a running server will not see it. The service also skips re-seeding when no SKILL.md's size\u002Fmtime changed, so rebuilding the JAR is what makes a change land.\n5. **Commit** the new `skills\u002F\u003Cname>\u002F` directory. No SQL seed change is needed — the SKILL.md is the source of truth and obsoletes per-skill `INSERT INTO mate_skill`.\n\n## Custom Workflow (skill_manage)\n\nAgents and users create runtime skills with the `skill_manage` tool — actions `create | edit | patch | delete`:\n\n- `create` — a new skill from full SKILL.md content. Rejects a duplicate name.\n- `edit` — a full-content rewrite of a custom skill.\n- `patch` — find-and-replace one section (`oldText` → `newText`).\n- `delete` — uninstall (logical delete plus workspace archive).\n\nNotes:\n\n- Every write is **security-scanned** (`SkillSecurityService`) before saving — dangerous patterns are rejected with the reason. Builtin SKILL.md files are NOT scanned; they are trusted committed source.\n- `edit` \u002F `patch` \u002F `delete` **refuse builtin skills** (\"cannot edit builtin skill\"). To change a builtin skill, edit the resource file and restart.\n- A custom skill is live immediately — the tool re-runs the resolver pipeline — so no restart is needed.\n\n## Supporting Files\n\nBeyond `SKILL.md`, a skill directory may carry:\n\n- `references\u002F*.md` — long-form material the body links to. Use this to keep SKILL.md under ~20k chars.\n- `scripts\u002F*` — executable helpers a skill invokes.\n- `templates\u002F`, `assets\u002F` — used by some bundled skills (HTML templates, images, etc.).\n\n`SkillFileAccessPolicy` only resolves runtime paths under `references\u002F` and `scripts\u002F`, and rejects `..` traversal or absolute paths — keep runtime-read files in those two directories.\n\n## Common Pitfalls\n\n1. **Leading whitespace before `---`.** The frontmatter regex anchors on `^---`; a blank line or BOM makes the whole file parse as body with an empty `name`, and a builtin skill is silently skipped.\n2. **Expecting a running server to see a new builtin skill.** `BuiltinSkillSeedService` seeds only at startup. Restart — or, for a quick iteration, create a custom skill via `skill_manage`, which is live immediately.\n3. **Trying to `skill_manage edit` a builtin skill.** It is refused. Builtin skills are committed source — edit the file and restart.\n4. **Adding an `INSERT INTO mate_skill` for a new builtin skill.** Unnecessary and discouraged — the SKILL.md is the source of truth and the seed service upserts by `name`.\n5. **Generic description.** \"Debug things\" is weak. A peer description names the *trigger* — \"4-phase root cause debugging: understand bugs before fixing.\" beats \"Debug things.\"\n6. **Naming an external project or internal RFC in the skill body.** Describe the function objectively. Shipped content states *what* it does, not where the idea came from — `author: ported` is the neutral attribution for an adapted skill.\n7. **Skill content over 100k chars.** `skill_manage` rejects it outright; split detail into `references\u002F`.\n8. **Mismatched directory and `name`.** The upsert keys on the frontmatter `name`, but a directory that disagrees confuses everyone reading the tree. Keep them equal.\n\n## Verification Checklist\n\n- [ ] File at `mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002F\u003Cname>\u002FSKILL.md` (builtin); the directory name equals the frontmatter `name`\n- [ ] Frontmatter starts at byte 0 with `---`, closes with a `---` line, and the body is non-empty\n- [ ] `name` matches `^[a-z0-9][a-z0-9._-]{0,63}$`; `description` is a single line\n- [ ] `version`, `tags`, `author` present (peer-matched shape)\n- [ ] Total file ≤ 100,000 chars (aim 6-15k; split into `references\u002F` past ~20k)\n- [ ] Structure: `# Title` → `## Overview` → `## When to Use` → actionable body → `## Common Pitfalls` → `## Verification Checklist`\n- [ ] No external project names or RFC numbers in the body\n- [ ] Builtin: server restarted so `BuiltinSkillSeedService` seeds the row; the new `skills\u002F\u003Cname>\u002F` directory is committed\n- [ ] Custom: created via `skill_manage`, security scan reported PASSED\n",{"name":5,"tags":23,"author":29,"version":30,"description":7},[24,25,26,27,28],"skills","authoring","skill-md","conventions","meta","ported","1.0.0","dev","26b960a788645da1daf5b6c1c8c7ffe1a78ab755","mateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fskill-authoring","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid","https:\u002F\u002Fgithub.com\u002Fpan-hh","2026-06-25 12:43:25",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add pan-hh\u002Fmateclaw-hybrid --skill skill-authoring",{"tool":43,"command":44},"bunx","bunx skills add pan-hh\u002Fmateclaw-hybrid --skill skill-authoring",{"tool":46,"command":47},"pnpm","pnpm dlx skills add pan-hh\u002Fmateclaw-hybrid --skill skill-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fskill-authoring\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M77MNZW6PYRTH5KM9121RYAK","sample","Test fixture for SkillBundleMaterializer.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Ftest\u002Fresources\u002Ftest-bundles\u002Fsample\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M77MNNA8HYFP854EHAEGZ838","x_intel","Read X (Twitter) posts, search, timelines and user profiles via the official xurl CLI.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fx_intel\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M77MNJRFN8KNSY1PXRFBV97S","writing-plans","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77MNF0PF06YCNA9TWK85PE9","webhook-subscriptions","Webhook subscriptions: event-driven agent runs.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fwebhook-subscriptions\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77MNATFKP03KPE7HM7W29MC","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M77MN78ZK5EKN7HT2ZKYDPKM","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002Fpan-hh\u002Fmateclaw-hybrid\u002Fblob\u002Fdev\u002Fmateclaw-server\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]