How do I install the Skillset Dev Compiler skill?

Run npx skillmds@latest add outfitter-dev/skillset-dev-compiler in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skillset Dev Compiler safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skillset Dev Compiler?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skillset Dev Compiler free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skillset Dev Compiler?

outfitter-dev (@outfitter-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skillset Dev Compiler by outfitter-dev

Name: Skillset Dev Compiler
Author: outfitter-dev

Skillset Dev Compiler

Implement or review Skillset compiler behavior, package ownership, rendering, command composition, operation results, and generated-output semantics. Use for changes under apps/skillset or packages/core, registry, lint, transforms, toolkit, or workbench that are not primarily shared schema-contract changes.

outfitter-dev 06fb947 2 files · 4.4 KB Updated Sep 17, 2026

File contents

Skillset Compiler Development

Work From The Owner

Read docs/project/tenets.md, the relevant ADRs, and docs/development/package-ownership.md.
Inspect the closest implementation, its package-root API, and focused tests before editing.
Place provider-neutral compiler facts and write semantics in @skillset/core; keep CLI parsing, presentation, prompts, and exit mapping in apps/skillset.
Keep provider evidence in @skillset/registry, shared source shape in @skillset/schema, authoring diagnostics in @skillset/workbench, and reusable lint or transform behavior in their owning packages.
Return structured diagnostics and operation facts from compiler layers. Do not hide writes, call process.exit, or make core behavior depend on terminal presentation.

Read references/package-map.md when choosing an owner, changing a large implementation anchor, or deciding whether an internal should become a package-root export.

Implement And Verify

Add focused tests for each behavior change and run them with bun run test:focused -- <test-files...>.
Run bun run typecheck for TypeScript or package changes.
Run the relevant deterministic or adapter conformance lane for rendering, destination, provider, or structured-result changes.
If self-hosted source or generated-output promises change, run bun run skillset:build, inspect the generated diff, then run bun run skillset:check and bun run skillset:check:outputs.
Add the required package Changeset and Skillset change entry when the release or source-change contracts require them.
Run bun run check before handoff.

Do not publish, install generated artifacts, mutate user-level provider configuration, or turn provider-specific behavior into fake portable behavior.

---name: skillset-dev-compilerdescription: Implement or review Skillset compiler behavior, package ownership, rendering, command composition, operation results, and generated-output semantics. Use for changes under apps/skillset or packages/core, registry, lint, transforms, toolkit, or workbench that are not primarily shared schema-contract changes.---# Skillset Compiler Development## Work From The Owner1. Read `docs/project/tenets.md`, the relevant ADRs, and `docs/development/package-ownership.md`.2. Inspect the closest implementation, its package-root API, and focused tests before editing.3. Place provider-neutral compiler facts and write semantics in `@skillset/core`; keep CLI parsing, presentation, prompts, and exit mapping in `apps/skillset`.4. Keep provider evidence in `@skillset/registry`, shared source shape in `@skillset/schema`, authoring diagnostics in `@skillset/workbench`, and reusable lint or transform behavior in their owning packages.5. Return structured diagnostics and operation facts from compiler layers. Do not hide writes, call `process.exit`, or make core behavior depend on terminal presentation.Read [references/package-map.md](references/package-map.md) when choosing an owner, changing a large implementation anchor, or deciding whether an internal should become a package-root export.## Implement And Verify- Add focused tests for each behavior change and run them with `bun run test:focused -- <test-files...>`.- Run `bun run typecheck` for TypeScript or package changes.- Run the relevant deterministic or adapter conformance lane for rendering, destination, provider, or structured-result changes.- If self-hosted source or generated-output promises change, run `bun run skillset:build`, inspect the generated diff, then run `bun run skillset:check` and `bun run skillset:check:outputs`.- Add the required package Changeset and Skillset change entry when the release or source-change contracts require them.- Run `bun run check` before handoff.Do not publish, install generated artifacts, mutate user-level provider configuration, or turn provider-specific behavior into fake portable behavior.

Frequently asked questions