skillpack harvest

Other Community v0.33.0

Skill notes

Contract

A harvest is "properly done" when: The host skill is mature (used in production, recent routing-eval cases pass). The editorial genericization in Phase 3 has scrubbed every fork-specific reference (names, real entities, internal channels).

Output Format

This skill produces three artifacts in gbrain's working tree: skills/<harvested-slug>/SKILL.md (and any sibling files like routing-eval.jsonl) Paired source files at their mirror paths (e.g. src/commands/<slug>.ts) when the host SKILL.md declared them

Anti-Patterns

Skipping the dry-run. Always preview first. Files land in gbrain's working tree; cleanup is a git checkout away, but you shouldn't need to. Trusting the linter alone. The default regex set catches the common cases. It doesn't catch every proper noun. Phase 3 (the

When to invoke

The user developed a skill in their host fork (Wintermute, Neuromancer, Zion, etc.) and wants other gbrain clients to be able to use it A skill has proven itself in production and is ready to generalize The user explicitly asks to "harvest" or "publish" a skill upstream Do NOT invoke when:

Preconditions

Before running this skill, confirm: The skill is mature. Recent routing-eval.jsonl cases pass; the skill has been used in production at least a few times. The skill is generalizable. Strip-test in your head: replace every fork-specific name. Does it still make sense as a skill?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v0.33.0 · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1 — Plan

Ask the user: What slug should the harvested skill have? (Slugs must be kebab-case, globally unique in the gbrain bundle.) Which host repo is the source? (Path to repo root, not to the skill directory — e.g. `~/git/wintermute`, not `~/git/wintermute/skills/foo`.)

02
Phase 2 — Dry-run + privacy-lint preview

Run the CLI with `--dry-run`: The output shows: Which files would land in gbrain's tree Whether paired sources are included (Implicit) The skill's frontmatter triggers — read them and check

03
Phase 3 — Genericization checklist (the editorial pass)

Before running the real harvest, walk the host's `skills/<slug>/` files and apply this checklist. If anything matches, edit the host file FIRST, then run harvest. Fork-specific names → generic phrasing `Wintermute` → `your OpenClaw` (or `OpenClaw deployment`)

04
Phase 4 — Real harvest

Once Phase 3 is complete, run the real harvest: Default behavior: Path-confinement + symlink rejection at file copy Privacy linter runs against `~/.gbrain/harvest-private-patterns.txt` (plus built-in defaults: `\bWintermute\b`, email, Slack channels)

05
Phase 5 — Verify in gbrain

After a successful harvest: `bun test test/skills-conformance.test.ts` — confirms the new SKILL.md meets the frontmatter contract. `gbrain skillpack check --strict` — confirms no drift between bundle and gbrain's own checkout.

06
Phase 6 — Downstream announcement (optional)

If other gbrain clients should pick up the new skill: Note it in `CHANGELOG.md` under "Skills added" for the next release Tag the user / contributor in the PR if the skill came from someone outside the core team

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.