[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F55TP3W4ZMBAP25M1QK17Y":3,"skill-same:01M7F55TP3W4ZMBAP25M1QK17Y":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":61},"01M7F55TP3W4ZMBAP25M1QK17Y","skillpack-harvest",null,"Lift a proven skill from a host repo (e.g. your OpenClaw fork) back into\ngbrain's bundle so other clients can scaffold it. Editorial workflow:\nthe CLI does the file copy + privacy lint; this skill drives the\njudgment-heavy genericization (scrub real names, generalize triggers,\nlift fork-specific conventions to references).","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskillpack-harvest\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: skillpack-harvest\nversion: 0.33.0\ndescription: |\n  Lift a proven skill from a host repo (e.g. your OpenClaw fork) back into\n  gbrain's bundle so other clients can scaffold it. Editorial workflow:\n  the CLI does the file copy + privacy lint; this skill drives the\n  judgment-heavy genericization (scrub real names, generalize triggers,\n  lift fork-specific conventions to references).\ntriggers:\n  - \"harvest this skill\"\n  - \"harvest my skill\"\n  - \"publish this skill to gbrain\"\n  - \"lift this skill\"\n  - \"share this skill\"\n  - \"promote this skill\"\n  - \"promote my skill\"\n  - \"skill upstream\"\n  - \"into the gbrain core\"\n  - \"gbrain bundle\"\nmutating: true\nwrites_pages: false\nwrites_to:\n  - skills\u002F\u003Charvested-slug>\u002F\n  - openclaw.plugin.json\n---\n\n# skillpack-harvest — Editorial workflow for lifting host skills into gbrain\n\n> **Convention:** see [_brain-filing-rules.md](..\u002F_brain-filing-rules.md) for\n> file placement rules. This skill writes into gbrain's own tree, not the\n> brain repo's notes.\n\nThis skill is the inverse of `gbrain skillpack scaffold`. Scaffold ships\nskills downstream (gbrain → host). Harvest lifts proven patterns\nupstream (host → gbrain) so they become references every other client\ncan scaffold.\n\n## Contract\n\nA harvest is \"properly done\" when:\n\n1. The host skill is mature (used in production, recent routing-eval\n   cases pass).\n2. The editorial genericization in Phase 3 has scrubbed every\n   fork-specific reference (names, real entities, internal channels).\n3. `gbrain skillpack harvest --dry-run` previewed the file set.\n4. The real `gbrain skillpack harvest \u003Cslug> --from \u003Chost>` succeeded\n   with `status: harvested` (no privacy-lint hits).\n5. `bun test test\u002Fskills-conformance.test.ts` passes on the new\n   `skills\u002F\u003Cslug>\u002FSKILL.md`.\n6. The user has reviewed the diff in gbrain and explicitly approved\n   the commit.\n\nIf any of these is incomplete, the skill is NOT yet harvested — the\nfiles may sit in gbrain's working tree, but they're not landed.\n\n## Output Format\n\nThis skill produces three artifacts in gbrain's working tree:\n\n1. `skills\u002F\u003Charvested-slug>\u002FSKILL.md` (and any sibling files like\n   `routing-eval.jsonl`)\n2. Paired source files at their mirror paths (e.g.\n   `src\u002Fcommands\u002F\u003Cslug>.ts`) when the host SKILL.md declared them\n   in frontmatter `sources:`\n3. An updated `openclaw.plugin.json` with the new slug added to\n   `skills:` (sorted)\n\nThe session output to the user is a one-line success summary plus\na list of files written. JSON mode (`--json`) returns the full\n`HarvestResult` shape for machine consumption.\n\n## Anti-Patterns\n\n- **Skipping the dry-run.** Always preview first. Files land in\n  gbrain's working tree; cleanup is a `git checkout` away, but you\n  shouldn't need to.\n- **Trusting the linter alone.** The default regex set catches the\n  common cases. It doesn't catch every proper noun. Phase 3 (the\n  editorial pass) is the primary defense.\n- **Harvesting `--no-lint` without justification.** The lint exists\n  for a reason. If you bypass it, document why in the commit.\n- **Harvesting a skill that's still in flux.** Wait until the host\n  version stabilizes. Otherwise you'll harvest, then re-harvest,\n  then re-harvest, and that churns gbrain's bundle for no benefit.\n- **Moving files instead of copying.** Harvest is a copy. The host\n  retains its skill. Don't `rm -rf` the source after harvesting.\n- **Harvesting batch (multiple skills at once).** Not supported, and\n  for good reason — the editorial review per skill is real work.\n\n## When to invoke\n\n- The user developed a skill in their host fork (your OpenClaw or any\n  private downstream fork) and wants other gbrain clients to be able to use it\n- A skill has proven itself in production and is ready to generalize\n- The user explicitly asks to \"harvest\" or \"publish\" a skill upstream\n\nDo NOT invoke when:\n- The skill is still in flux locally — let it stabilize first\n- The skill references private content that can't be generalized\n- The user just wants to share a one-off draft (use a gist instead)\n\n## Preconditions\n\nBefore running this skill, confirm:\n\n1. **The skill is mature.** Recent `routing-eval.jsonl` cases pass; the\n   skill has been used in production at least a few times.\n\n2. **The skill is generalizable.** Strip-test in your head: replace\n   every fork-specific name. Does it still make sense as a skill?\n\n3. **The user owns the gbrain checkout.** The harvest writes into\n   gbrain's working tree. They'll review and commit. Don't harvest\n   into a checkout the user doesn't intend to commit from.\n\n## Workflow\n\n### Phase 1 — Plan\n\nAsk the user:\n- What slug should the harvested skill have? (Slugs must be kebab-case,\n  globally unique in the gbrain bundle.)\n- Which host repo is the source? (Path to repo root, not to the skill\n  directory — e.g. `~\u002Fgit\u002Fagent-fork`, not `~\u002Fgit\u002Fagent-fork\u002Fskills\u002Ffoo`.)\n- Should paired source files come along? (Check the host SKILL.md's\n  frontmatter `sources:` array.)\n\n### Phase 2 — Dry-run + privacy-lint preview\n\nRun the CLI with `--dry-run`:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root> --dry-run\n```\n\nThe output shows:\n- Which files would land in gbrain's tree\n- Whether paired sources are included\n- (Implicit) The skill's frontmatter triggers — read them and check\n  they generalize\n\nDo **not** skip the dry-run. The privacy linter only runs on a real\nharvest, but the dry-run preview lets you see the files before they\nland. Spot-check the SKILL.md and any paired source for things the\nlinter might miss (proper nouns, internal project names, etc.).\n\n### Phase 3 — Genericization checklist (the editorial pass)\n\nBefore running the real harvest, walk the host's `skills\u002F\u003Cslug>\u002F`\nfiles and apply this checklist. If anything matches, edit the host\nfile FIRST, then run harvest.\n\n1. **Fork-specific names → generic phrasing**\n   - `\u003Cpersonal-fork-name>` → `your OpenClaw` (or `OpenClaw deployment`);\n     any pet name for the user's private agent gets the same treatment\n   - Personal first names (`garry`, `jane`, etc.) → `the user` \u002F\n     `you` \u002F a generic placeholder\n\n2. **Real entities → placeholders**\n   - Real people, companies, deals, funds → placeholder slugs\n     (`alice-example`, `acme-example`, `fund-a`, etc.)\n   - Email addresses → strip entirely OR use `example@example.com`\n   - Internal Slack channels → `#some-channel` or strip\n   - Specific tracker IDs \u002F Linear ticket numbers → strip\n\n3. **Fork-specific conventions → references**\n   - Mentions of `\u003Chost-repo>\u002Fdocs\u002F...` files → either lift the doc\n     into gbrain OR replace with a generic placeholder explanation\n   - Mentions of `\u003Chost-repo>\u002Fskills\u002F\u003Cother-fork-only-skill>` → either\n     decide to harvest that one too, or replace with a generic\n     pattern reference\n\n4. **Triggers array generalizes**\n   - Read every entry in frontmatter `triggers:`. None should\n     reference the user's name, fork name, or internal tools.\n   - \"Have garry sign off on it\" → \"have the user sign off on it\"\n\n5. **routing-eval.jsonl examples are scrubbed**\n   - Open `skills\u002F\u003Cslug>\u002Frouting-eval.jsonl`. Every `intent` field\n     gets the same scrub as `triggers:`.\n\n6. **Code comments + log strings**\n   - If a paired source is going to be harvested, walk it for the\n     same private-pattern leaks. Comments are the most common\n     hiding spot.\n\n### Phase 4 — Real harvest\n\nOnce Phase 3 is complete, run the real harvest:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root>\n```\n\nDefault behavior:\n- Path-confinement + symlink rejection at file copy\n- Privacy linter runs against `~\u002F.gbrain\u002Fharvest-private-patterns.txt`\n  (plus built-in defaults — the canonical private fork name, email\n  addresses, Slack channels; see `src\u002Fcore\u002Fskillpack\u002Fharvest-lint.ts`)\n- On any match → rollback (delete the harvested files) + exit non-zero\n- `openclaw.plugin.json` updated to add the slug, sorted\n\nOutcomes:\n- `harvested` — success, manifest updated, files in gbrain's tree\n- `lint_failed` — privacy linter caught something. Go back to Phase 3,\n  scrub the host file, retry.\n- `slug_collision` — gbrain already has a skill at that slug. Either\n  use a different slug, or pass `--overwrite-local` if you really\n  mean to replace.\n\n### Phase 5 — Verify in gbrain\n\nAfter a successful harvest:\n\n1. `bun test test\u002Fskills-conformance.test.ts` — confirms the new\n   SKILL.md meets the frontmatter contract.\n2. `gbrain skillpack check --strict` — confirms no drift between\n   bundle and gbrain's own checkout.\n3. `gbrain skillpack list` — confirms the slug shows up in the bundle.\n4. Review the diff: `cd \u003CgbrainRoot> && git diff -- skills\u002F\u003Cslug>\u002F`\n5. Commit the additions in gbrain (do NOT commit any leftover files\n   in the host repo — harvest is a copy, not a move).\n\n### Phase 6 — Downstream announcement (optional)\n\nIf other gbrain clients should pick up the new skill:\n- Note it in `CHANGELOG.md` under \"Skills added\" for the next release\n- Tag the user \u002F contributor in the PR if the skill came from\n  someone outside the core team\n\n## Bypass: `--no-lint`\n\nThe privacy linter is the safety net. The editorial pass is the\nprimary defense. If you've completed Phase 3 thoroughly and the\nlinter is still firing on a false positive, use `--no-lint`:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root> --no-lint\n```\n\n**Document the bypass in the commit message.** Future maintainers\nshould be able to see WHY the lint was bypassed (e.g. \"the fork name\nappears in a citation, not a real reference — verified manually\").\n\nNever bypass the linter on a casual basis. The whole point of the\ndefault-on lint is that real names occasionally slip through the\neditorial pass.\n\n## What harvest does NOT do\n\n- It does NOT move files (it copies). The host's `skills\u002F\u003Cslug>\u002F`\n  stays in place.\n- It does NOT auto-scrub names. The editorial pass is human-driven.\n- It does NOT publish to npm or a remote bundle. It writes to\n  gbrain's working tree; the user commits + ships via the normal\n  gbrain release process.\n- It does NOT support `--all` (no batch harvest). One skill at a\n  time keeps the editorial review tractable.\n\n## Files this skill touches\n\n- gbrain's `skills\u002F\u003Cslug>\u002F` — every file in the host skill dir\n  (copy)\n- gbrain's mirror path for declared paired sources\n  (e.g. `src\u002Fcommands\u002F\u003Cslug>.ts` if the host SKILL.md declares it\n  in frontmatter)\n- gbrain's `openclaw.plugin.json` — adds the slug to `skills:`\n  array, sorted alphabetically, without removing OpenClaw-native plugin fields\n  like `id`, `configSchema`, or `contracts`\n","# skillpack-harvest — Editorial workflow for lifting host skills into gbrain\n\n> **Convention:** see [_brain-filing-rules.md](..\u002F_brain-filing-rules.md) for\n> file placement rules. This skill writes into gbrain's own tree, not the\n> brain repo's notes.\n\nThis skill is the inverse of `gbrain skillpack scaffold`. Scaffold ships\nskills downstream (gbrain → host). Harvest lifts proven patterns\nupstream (host → gbrain) so they become references every other client\ncan scaffold.\n\n## Contract\n\nA harvest is \"properly done\" when:\n\n1. The host skill is mature (used in production, recent routing-eval\n   cases pass).\n2. The editorial genericization in Phase 3 has scrubbed every\n   fork-specific reference (names, real entities, internal channels).\n3. `gbrain skillpack harvest --dry-run` previewed the file set.\n4. The real `gbrain skillpack harvest \u003Cslug> --from \u003Chost>` succeeded\n   with `status: harvested` (no privacy-lint hits).\n5. `bun test test\u002Fskills-conformance.test.ts` passes on the new\n   `skills\u002F\u003Cslug>\u002FSKILL.md`.\n6. The user has reviewed the diff in gbrain and explicitly approved\n   the commit.\n\nIf any of these is incomplete, the skill is NOT yet harvested — the\nfiles may sit in gbrain's working tree, but they're not landed.\n\n## Output Format\n\nThis skill produces three artifacts in gbrain's working tree:\n\n1. `skills\u002F\u003Charvested-slug>\u002FSKILL.md` (and any sibling files like\n   `routing-eval.jsonl`)\n2. Paired source files at their mirror paths (e.g.\n   `src\u002Fcommands\u002F\u003Cslug>.ts`) when the host SKILL.md declared them\n   in frontmatter `sources:`\n3. An updated `openclaw.plugin.json` with the new slug added to\n   `skills:` (sorted)\n\nThe session output to the user is a one-line success summary plus\na list of files written. JSON mode (`--json`) returns the full\n`HarvestResult` shape for machine consumption.\n\n## Anti-Patterns\n\n- **Skipping the dry-run.** Always preview first. Files land in\n  gbrain's working tree; cleanup is a `git checkout` away, but you\n  shouldn't need to.\n- **Trusting the linter alone.** The default regex set catches the\n  common cases. It doesn't catch every proper noun. Phase 3 (the\n  editorial pass) is the primary defense.\n- **Harvesting `--no-lint` without justification.** The lint exists\n  for a reason. If you bypass it, document why in the commit.\n- **Harvesting a skill that's still in flux.** Wait until the host\n  version stabilizes. Otherwise you'll harvest, then re-harvest,\n  then re-harvest, and that churns gbrain's bundle for no benefit.\n- **Moving files instead of copying.** Harvest is a copy. The host\n  retains its skill. Don't `rm -rf` the source after harvesting.\n- **Harvesting batch (multiple skills at once).** Not supported, and\n  for good reason — the editorial review per skill is real work.\n\n## When to invoke\n\n- The user developed a skill in their host fork (your OpenClaw or any\n  private downstream fork) and wants other gbrain clients to be able to use it\n- A skill has proven itself in production and is ready to generalize\n- The user explicitly asks to \"harvest\" or \"publish\" a skill upstream\n\nDo NOT invoke when:\n- The skill is still in flux locally — let it stabilize first\n- The skill references private content that can't be generalized\n- The user just wants to share a one-off draft (use a gist instead)\n\n## Preconditions\n\nBefore running this skill, confirm:\n\n1. **The skill is mature.** Recent `routing-eval.jsonl` cases pass; the\n   skill has been used in production at least a few times.\n\n2. **The skill is generalizable.** Strip-test in your head: replace\n   every fork-specific name. Does it still make sense as a skill?\n\n3. **The user owns the gbrain checkout.** The harvest writes into\n   gbrain's working tree. They'll review and commit. Don't harvest\n   into a checkout the user doesn't intend to commit from.\n\n## Workflow\n\n### Phase 1 — Plan\n\nAsk the user:\n- What slug should the harvested skill have? (Slugs must be kebab-case,\n  globally unique in the gbrain bundle.)\n- Which host repo is the source? (Path to repo root, not to the skill\n  directory — e.g. `~\u002Fgit\u002Fagent-fork`, not `~\u002Fgit\u002Fagent-fork\u002Fskills\u002Ffoo`.)\n- Should paired source files come along? (Check the host SKILL.md's\n  frontmatter `sources:` array.)\n\n### Phase 2 — Dry-run + privacy-lint preview\n\nRun the CLI with `--dry-run`:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root> --dry-run\n```\n\nThe output shows:\n- Which files would land in gbrain's tree\n- Whether paired sources are included\n- (Implicit) The skill's frontmatter triggers — read them and check\n  they generalize\n\nDo **not** skip the dry-run. The privacy linter only runs on a real\nharvest, but the dry-run preview lets you see the files before they\nland. Spot-check the SKILL.md and any paired source for things the\nlinter might miss (proper nouns, internal project names, etc.).\n\n### Phase 3 — Genericization checklist (the editorial pass)\n\nBefore running the real harvest, walk the host's `skills\u002F\u003Cslug>\u002F`\nfiles and apply this checklist. If anything matches, edit the host\nfile FIRST, then run harvest.\n\n1. **Fork-specific names → generic phrasing**\n   - `\u003Cpersonal-fork-name>` → `your OpenClaw` (or `OpenClaw deployment`);\n     any pet name for the user's private agent gets the same treatment\n   - Personal first names (`garry`, `jane`, etc.) → `the user` \u002F\n     `you` \u002F a generic placeholder\n\n2. **Real entities → placeholders**\n   - Real people, companies, deals, funds → placeholder slugs\n     (`alice-example`, `acme-example`, `fund-a`, etc.)\n   - Email addresses → strip entirely OR use `example@example.com`\n   - Internal Slack channels → `#some-channel` or strip\n   - Specific tracker IDs \u002F Linear ticket numbers → strip\n\n3. **Fork-specific conventions → references**\n   - Mentions of `\u003Chost-repo>\u002Fdocs\u002F...` files → either lift the doc\n     into gbrain OR replace with a generic placeholder explanation\n   - Mentions of `\u003Chost-repo>\u002Fskills\u002F\u003Cother-fork-only-skill>` → either\n     decide to harvest that one too, or replace with a generic\n     pattern reference\n\n4. **Triggers array generalizes**\n   - Read every entry in frontmatter `triggers:`. None should\n     reference the user's name, fork name, or internal tools.\n   - \"Have garry sign off on it\" → \"have the user sign off on it\"\n\n5. **routing-eval.jsonl examples are scrubbed**\n   - Open `skills\u002F\u003Cslug>\u002Frouting-eval.jsonl`. Every `intent` field\n     gets the same scrub as `triggers:`.\n\n6. **Code comments + log strings**\n   - If a paired source is going to be harvested, walk it for the\n     same private-pattern leaks. Comments are the most common\n     hiding spot.\n\n### Phase 4 — Real harvest\n\nOnce Phase 3 is complete, run the real harvest:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root>\n```\n\nDefault behavior:\n- Path-confinement + symlink rejection at file copy\n- Privacy linter runs against `~\u002F.gbrain\u002Fharvest-private-patterns.txt`\n  (plus built-in defaults — the canonical private fork name, email\n  addresses, Slack channels; see `src\u002Fcore\u002Fskillpack\u002Fharvest-lint.ts`)\n- On any match → rollback (delete the harvested files) + exit non-zero\n- `openclaw.plugin.json` updated to add the slug, sorted\n\nOutcomes:\n- `harvested` — success, manifest updated, files in gbrain's tree\n- `lint_failed` — privacy linter caught something. Go back to Phase 3,\n  scrub the host file, retry.\n- `slug_collision` — gbrain already has a skill at that slug. Either\n  use a different slug, or pass `--overwrite-local` if you really\n  mean to replace.\n\n### Phase 5 — Verify in gbrain\n\nAfter a successful harvest:\n\n1. `bun test test\u002Fskills-conformance.test.ts` — confirms the new\n   SKILL.md meets the frontmatter contract.\n2. `gbrain skillpack check --strict` — confirms no drift between\n   bundle and gbrain's own checkout.\n3. `gbrain skillpack list` — confirms the slug shows up in the bundle.\n4. Review the diff: `cd \u003CgbrainRoot> && git diff -- skills\u002F\u003Cslug>\u002F`\n5. Commit the additions in gbrain (do NOT commit any leftover files\n   in the host repo — harvest is a copy, not a move).\n\n### Phase 6 — Downstream announcement (optional)\n\nIf other gbrain clients should pick up the new skill:\n- Note it in `CHANGELOG.md` under \"Skills added\" for the next release\n- Tag the user \u002F contributor in the PR if the skill came from\n  someone outside the core team\n\n## Bypass: `--no-lint`\n\nThe privacy linter is the safety net. The editorial pass is the\nprimary defense. If you've completed Phase 3 thoroughly and the\nlinter is still firing on a false positive, use `--no-lint`:\n\n```bash\ngbrain skillpack harvest \u003Cslug> --from \u003Chost-repo-root> --no-lint\n```\n\n**Document the bypass in the commit message.** Future maintainers\nshould be able to see WHY the lint was bypassed (e.g. \"the fork name\nappears in a citation, not a real reference — verified manually\").\n\nNever bypass the linter on a casual basis. The whole point of the\ndefault-on lint is that real names occasionally slip through the\neditorial pass.\n\n## What harvest does NOT do\n\n- It does NOT move files (it copies). The host's `skills\u002F\u003Cslug>\u002F`\n  stays in place.\n- It does NOT auto-scrub names. The editorial pass is human-driven.\n- It does NOT publish to npm or a remote bundle. It writes to\n  gbrain's working tree; the user commits + ships via the normal\n  gbrain release process.\n- It does NOT support `--all` (no batch harvest). One skill at a\n  time keeps the editorial review tractable.\n\n## Files this skill touches\n\n- gbrain's `skills\u002F\u003Cslug>\u002F` — every file in the host skill dir\n  (copy)\n- gbrain's mirror path for declared paired sources\n  (e.g. `src\u002Fcommands\u002F\u003Cslug>.ts` if the host SKILL.md declares it\n  in frontmatter)\n- gbrain's `openclaw.plugin.json` — adds the slug to `skills:`\n  array, sorted alphabetically, without removing OpenClaw-native plugin fields\n  like `id`, `configSchema`, or `contracts`\n",{"name":5,"version":24,"mutating":25,"triggers":26,"writes_to":37,"description":40,"writes_pages":20},"0.33.0",true,[27,28,29,30,31,32,33,34,35,36],"harvest this skill","harvest my skill","publish this skill to gbrain","lift this skill","share this skill","promote this skill","promote my skill","skill upstream","into the gbrain core","gbrain bundle",[38,39],"skills\u002F\u003Charvested-slug>\u002F","openclaw.plugin.json","Lift a proven skill from a host repo (e.g. your OpenClaw fork) back into\ngbrain's bundle so other clients can scaffold it. Editorial workflow:\nthe CLI does the file copy + privacy lint; this skill drives the\njudgment-heavy genericization (scrub real names, generalize triggers,\nlift fork-specific conventions to references).\n","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fskillpack-harvest",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":25},[51,54,57],{"tool":52,"command":53},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill skillpack-harvest",{"tool":55,"command":56},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill skillpack-harvest",{"tool":58,"command":59},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill skillpack-harvest","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskillpack-harvest\u002FSKILL.md",[],[63,70,75,82,89,96],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]