How do I install the Skillset Dev Schema skill?

Run npx skillmds@latest add outfitter-dev/skillset-dev-schema-2 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 Schema safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skillset Dev Schema?

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 Schema free to use?

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

Who published Skillset Dev Schema?

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

Skillset Dev Schema by outfitter-dev

Name: Skillset Dev Schema
Author: outfitter-dev

Skillset Dev Schema

Change or review Skillset workspace config, source frontmatter, shared metadata fields, structural validation, examples, and generated schema artifacts. Use whenever adding, removing, renaming, validating, or documenting a key shared by compiler and authoring surfaces.

outfitter-dev Updated Sep 21, 2026

File contents

Skillset Schema Development

Keep One Contract Owner

Read docs/project/tenets.md, relevant ADRs, and docs/development/schema-contracts.md.
Confirm the field represents a real adaptive source meaning. Keep provider-only contracts under explicit provider blocks.
Change packages/schema/src/contracts.ts and shared value contracts before teaching compiler, Workbench, CLI, or documentation another shape.
Add structural diagnostics in packages/schema/src/validate.ts; keep path resolution, destination policy, graph semantics, and rendering behavior in Core.
Route all consumers through @skillset/schema instead of maintaining parallel allowed-key lists.

Read references/contract-workflow.md for the artifact, validation, example, and release checklist.

Verify The Contract

Extend schema descriptor, validation, and maximal-example coverage.
Run bun run schema:generate, inspect generated schemas and examples, then run bun run schema:check.
Run focused schema and affected-consumer tests with bun run test:focused -- <test-files...>.
Add a package Changeset for package-facing schema changes and a Skillset change entry when the self-hosted source contract or generated-output promise changes.
Rebuild and check self-hosted output when canonical .skillset/ source changes.
Run bun run typecheck and bun run check before handoff.

Do not document a field that the schema package does not own, hand-edit generated schema artifacts, or use provider spelling as a second portable key for the same meaning.

Frequently asked questions