This is a one-time documentation snapshot for comparing Blume and Nimbus. Source: Skillset 24800e02ed4e, copied November 2, 2026. Snapshot manifest · MIT license.
Choose the question you are trying to answer. Each linked page states what it owns; exhaustive command and support facts come from generated reference rather than duplicated prose.
I am new to Skillset
- Why Skillset explains the problem, the source-first model, and when the compiler is a good fit.
- Install Skillset compares the native global, Homebrew, GitHub asset, Bun, CI, local dependency, and contributor routes.
- Start with Skillset routes from installation into a first build, adoption, daily work, and deliberate shipping workflows.
- Build versus activation explains what Skillset writes and what remains a separate user or provider decision.
I need to look something up
- Generated reference routes to contract-owned CLI commands, feature support, schemas, and examples.
- Configuration explains workspace settings, source frontmatter, target overrides, and tools policy.
- Source reference documents the canonical workspace layout, rules, and preprocessing.
- CLI reference lists every public command and its generated route pages.
- Feature reference defines exact authoring, output, error, example, and caveat contracts by feature or workflow.
- Feature support matrix shows registry-owned support across canonical provider targets.
- Glossary defines the source, build, destination, provider, and activation vocabulary.
Something failed
- Troubleshooting starts from source, drift, import, recovery, watch, CI, and activation symptoms.
I need to ship or distribute work
- Continuous integration adds branch-aware readiness checks and bounds automatic generated-output repair.
- Publishing separates workspace releases, downstream distribution planning, and npm package publication.
- Marketplaces verifies curated plugin entries and writes supported provider catalog indexes deliberately.
- Generated-state rebuild gives the owner-reviewed, recoverable path from pre-v4 locks to current projection roles.
I am contributing
- Contributing covers setup, checks, source ownership, Changesets, and review expectations.
- Development documentation routes maintainers to documentation, schema, package, feature-system, and evidence guidance.
- Project documentation routes to the design tenets and active or archived plans.
- Documentation system defines authored and generated ownership, validation, migrations, and review.
- Security policy gives the private vulnerability-reporting path.
Detailed guides
These pages cover common author and maintainer workflows:
- Build Your First Skill walks through the current first-author scaffold and build.
- Import Existing Work separates whole-repository adoption from one explicit source import.
- Development Loop covers preview, write, watch, reconciliation, and recovery.
- Interactive CLI defines prompt eligibility and controlled-terminal behavior.
- Package ownership explains the compiler package boundaries used by maintainers.
Generated output does not grant runtime authority. Skillset renders files. It does not install, trust, activate, symlink, or mutate user-level provider configuration. See Build Versus Activation.