skillpack-harvest

Copies a proven host skill into the gbrain bundle with privacy linting and editorial genericization.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill skillpack-harvest-amc-jtc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skillpack-harvest
Source: https://github.com/AMC-JTC/gbrain-1/tree/main/skills/skillpack-harvest
Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill skillpack-harvest-amc-jtc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving a skill that matured inside a private host fork (like an OpenClaw deployment) back into the shared gbrain bundle is risky: real names, internal channels, and fork-specific conventions leak easily, and manual copying skips validation. This Skill drives the judgment-heavy editorial workflow so harvested skills are generic, linted, and conformant before they land. ## Core Features & Use Cases - Dry-run preview and privacy lint: Previews the file set with gbrain skillpack harvest --dry-run, then runs a real harvest with a privacy linter that rolls back on any match. - Editorial genericization checklist: A six-point Phase 3 pass that scrubs personal names, real entities, internal channels, fork-specific triggers, and routing-eval examples before copying. - Conformance verification: Validates the result with bun test test/skills-conformance.test.ts, gbrain skillpack check --strict, and a sorted openclaw.plugin.json update. - Use Case: You built a meeting-notes skill in your OpenClaw fork that has run in production for weeks. Use this Skill to scrub your name and company references, harvest it into gbrain, and let every other client scaffold it. ## Quick Start Ask the agent to harvest your mature fork skill into the gbrain bundle, starting with a dry-run preview and the genericization checklist.

Frequently Asked Questions about skillpack-harvest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a skill from my OpenClaw fork to gbrain?

Run gbrain skillpack harvest <slug> --from <host-repo-root> after a dry-run preview and an editorial pass that scrubs private names. The CLI copies the skill files, runs a privacy linter, and adds the slug to openclaw.plugin.json.

What does the skillpack harvest privacy linter check?

The linter matches built-in defaults plus patterns from ~/.gbrain/harvest-private-patterns.txt, covering the private fork name, email addresses, and Slack channels. On any match it rolls back the copied files and exits non-zero.

Can I harvest multiple skills into gbrain at once?

No, batch harvest is intentionally unsupported. Each skill requires its own editorial genericization review, so harvest processes one skill at a time to keep that review tractable.

When should I not harvest a skill upstream?

Skip harvesting when the skill is still in flux locally, references private content that cannot be generalized, or is a one-off draft better shared as a gist. Wait until routing-eval cases pass and the skill has production usage.

What happens if the harvest slug already exists in gbrain?

The harvest returns a slug_collision outcome and stops. Either choose a different kebab-case slug or pass --overwrite-local if you intentionally want to replace the existing skill.