Harness Kit

skill

skillify

Turn proven agent-session patterns into first-party Harness Kit skills. Use when: "skillify this conversation", "make this into a skill", "generate a skill from current transcript", "extract reusable workflow". Trigger: /skillify.

/skillify

Source: skills/skillify/SKILL.md

What it does

Turn proven agent-session patterns into first-party Harness Kit skills. Use when: "skillify this conversation", "make this into a skill", "generate a skill from current transcript", "extract reusable workflow". Trigger: /skillify.

Workflow role

Support primitive in the Harness Kit operating loop.

Source contract preview

This generated excerpt gives readers the beginning of the live primitive contract before they jump to GitHub.

Convert an agent conversation into a durable skill when the behavior is novel,
repeatable, and portable across harnesses.

## Scope

MVP supports Claude Code JSONL transcripts and `--from-current` style local
transcript extraction. Gemini, Codex batch ingestion, hosted transcript stores,
and automatic publication are future work.

## Delegation Floor

Delegation floor applies for novelty classification, portability critique, and
new skill design: probe the roster first; dispatch two or more providers;
direct solo only for deterministic parser/CRUD commands, emergency
preservation, user-forbidden delegation, or fewer-than-two-providers cases. See
`harnesses/shared/AGENTS.md` (Roster).

Local lane guidance: Use specialized lanes for transcript-pattern mining,
skill-design critique, portability/security review, and generated-skill
validator. Native in-thread subagents may supplement but do not satisfy the
roster floor.

## Workflow

1. Parse the transcript with `scripts/parse-transcript.py`.
2. Classify novelty and repeatability with `scripts/classify-conversation.py`.
   It dispatches two or more roster providers through the existing
   `scripts/dispatch-agent.py` boundary and records delegation receipts.
3. Create or update the candidate skill with `scripts/skill-crud.py`.
4. Validate frontmatter, portability, and generated skill shape before
   bootstrap.
5. Run `./bootstrap.sh` so the first-party skill catalog propagates to active
   harnesses.

## Portability Contract

Generated skills must be filesystem-first and cross-harness. Reject content
that depends on harness-private operations such as `SendUserMessage`, direct
tool names like `Edit`, or raw `bash` instructions without a fallback path.
Use the frontmatter schema in `references/frontmatter-schema.md`.

## Completion Gate
...

What to verify