phrazzld/seed
skills/seed/SKILL.md
Vendor the system-wide Harness Kit catalog into the current repo when a project needs checked-in local copies instead of relying on global bootstrap symlinks. Copies first-party skills and agents into a repo-local shared skill layer, then bridges harness-specific entrypoints back to that shared copy. Use when: "seed this repo", "vendor harness kit here", "initialize the agent here", "set me up offline". Trigger: /seed.
$ install --global
skillsauthnpx skillsauth add phrazzld/spellbook seedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 6:27 AM212.0s1 file scanned
SKILL.md
- name:
- seed
- description:
- |
- shared copy. Use when:
- seed this repo", "vendor harness kit here",
- Trigger:
- /seed.
/seed
Vendor Harness Kit into this repo. Most repos should rely on system-wide
bootstrap instead; use /seed only when the repo needs checked-in local
copies for offline work, review, or repository-specific persistence.
What to do
-
Find the Harness Kit root:
readlink -fthis SKILL.md, walk up until you seeskills/+agents/+harnesses/. -
Resolve the repo-local shared skill root. Use
.agents/skills/. If a repo already has legacy.agent/skills/, stop and ask whether to migrate it. The shared root is the canonical storage for vendored Harness Kit skills;.claude/skills/,.codex/skills/, and.pi/skills/are bridges. -
Copy every skill in
<harness-kit-root>/skills/into the shared skill root, preserving each skill's full directory (references/,scripts/,evals/, everything). Skipseeditself; it lives globally. -
Ensure
.claude/skills/<name>,.codex/skills/<name>, and.pi/skills/<name>point at each shared skill when those harness dirs exist. Do not duplicate skill contents into harness-specific dirs. -
Copy every agent in
<harness-kit-root>/agents/into the repo's existing agent directory. In most repos today that is.claude/agents/. Do not invent a second copy of agents unless the repo already has a documented shared-agent convention. -
Copy
<harness-kit-root>/harnesses/shared/AGENTS.mdto./AGENTS.mdonly if one doesn't already exist. -
Print what you installed.
Invariants
- Never modify the Harness Kit root or
~/.claude/~/.codex/~/.pi. Writes only to the current repo. - Shared skill root first. Harness Kit-distributed skills live in the
repo-local shared skill layer;
.claude/skills/is only a bridge. - Don't clobber existing shared skill roots,
.claude/, orAGENTS.md— ask first. - Don't filter, don't judge, don't specialize. Global bootstrap already
installs all first-party skills;
/seedexists only for repo-local vendoring.
Typical time: seconds. Typical cost: zero LLM tokens beyond the skill body — just file copies.
Related Skills
phrazzld/compound
testing
VerifiedTrustedCommunity
Capture one compounding repo-technical learning while a solved problem is still fresh. Use when: after a bug fix, diagnosis, delivery, review, or incident reveals a reusable pattern worth adding to `docs/solutions/`. Trigger: /compound, /capture-learning, /learning.
13SKILL.mdUpdated Jul 5, 2026
phrazzld/factory-apps
testing
VerifiedTrustedCommunity
Route Misty Step factory application capabilities. Use when choosing, auditing, integrating, or operating Canary, Powder, Landmark, Aesthetic, or Bitterblossom: production observability, incidents, health checks, error logging, backlog/work-card state, release intelligence, UI/UX system adoption, or supervised/unsupervised agent dispatch. Trigger: /factory-apps, /factory-stack.
13SKILL.mdUpdated Jul 4, 2026
phrazzld/skill-eval
testing
VerifiedTrustedCommunity
Prove a skill beats no-skill with a falsifiable A/B eval, or retire it. Design, generate, run, and maintain a skill-specific eval: name the one claim the skill must earn, run it skill-on vs raw same-model, grade blind with objective checks first, return a keep/adapt/cut verdict. Use when: "eval this skill", "does this skill help", "prove the skill beats no skill", "write an eval for", "benchmark a skill", "is this skill worth it", "skill A/B", "skill regression test", "generate skill evals". Trigger: /skill-eval, /eval-skill, /prove-skill.
13SKILL.mdUpdated Jul 2, 2026
phrazzld/skills/harness-engineering/templates/repo-local-skill
tools
VerifiedTrustedCommunity
> Template. Copy to `<target-repo>/.agents/skills/<repo>-<domain>/SKILL.md` > and fill every bracketed placeholder from the live target repo. Delete this > line and every other `> ` guidance line before committing. See > `../../references/repo-local-skill-generation.md` for the full process. --- name: <repo>-<domain> description: | [One paragraph: what this skill verifies/runs/operates for <repo>, stated in terms of the repo's real shape (service/CLI/library/etc.), not generic process. En
13SKILL.mdUpdated Jul 2, 2026