Registry
This page lists everything published in the default registry: metapackages first, then every skill.
To add a skill or metapackage to a project, run the command shown on its entry, then run skm install to link it into your agents.
The entries come from registries.default: [email protected]:skills-yaml/registry.git, and this page is regenerated from the registry on every deploy.
A metapackage adds a set of skills in one step. Open one to see its scope and every skill it contains.
skills-yaml/authoring-toolkit
2 skills from the skills-yaml scope, each pinned to an exact version: skill-creator, skill-reviewer.
skm add skills-yaml/authoring-toolkit --kind bundle --yes
workspace/all-workspace-skills
22 skills from the workspace scope, each pinned to an exact version: address-review-feedback, adopt-workspace-structure, analyze-repository, coordinate-multi-agent-development, design-domain-model, fix-bug, and 16 more.
skm add workspace/all-workspace-skills --kind bundle --yes
Each skill is a versioned package with its own entry, showing its releases, what it ships and the command that adds it.
skills-yaml/skill-creator
Author a new skill package for a skills-yaml registry so it passes the registry gates on the first attempt. Use when adding a skill, packaging an existing prompt or workflow as a skill, publishing a new version of one, or fixing a package that CI rejected for structure, frontmatter, symlink or payload errors.
skm add skills-yaml/skill-creator
skills-yaml/skill-reviewer
Review a skill package before it is published or installed, for compliance with the registry contract and for unsafe or malicious behavior in its scripts and instructions. Use when reviewing a contributed skill, auditing one from an untrusted registry, deciding whether to install a third-party skill, or checking a package after CI passed but before release.
skm add skills-yaml/skill-reviewer
software-development/spec
Write clear, reviewable software specs with a Symphony-style structure: problem, goals, non-goals, design, alternatives, rollout, risks, and open questions. Use this when drafting a spec, RFC, design doc, or implementation plan that should be easy for humans and agents to review.
skm add software-development/spec
system/devops-manager
Manage services, health, security and updates on a Debian host running Docker. Use when the user needs to inspect Docker containers, read system logs, apply updates, or check core services such as Nginx or PostgreSQL.
skm add system/devops-manager
system/gcp-debug
Debug GCP services using logs and interrogate status of Cloud Run, Cloud Functions, GKE, and Compute Engine.
skm add system/gcp-debug
workspace/address-review-feedback
Triage and implement selected actionable feedback from a pull request, branch review, or review report. Use when the user asks to address review comments, requested changes, or unresolved threads and authorizes the corresponding code or documentation edits.
skm add workspace/address-review-feedback
workspace/adopt-workspace-structure
Adopt, upgrade, repair, or assess workspace documentation with guided architecture and technology decisions. Use for workspace initialization, version migration, conformance repair, or adoption planning; involve the user in material choices and turn agreed deferred improvements into actionable specs.
skm add workspace/adopt-workspace-structure
workspace/analyze-repository
Analyze a repository without modifying it, producing an evidence-backed account of its purpose, structure, technology stack, development lifecycle, policies, documentation state, active work, risks, and evidence gaps. Use when a repository needs assessment, onboarding context, or current-state discovery before planning work.
skm add workspace/analyze-repository
workspace/coordinate-multi-agent-development
Let peer agents coordinate on one machine through atomic task and version claims, self-created detached worktrees, shared file scopes, independent review, serialized integration, and lossless recovery. No coordinator agent is required.
skm add workspace/coordinate-multi-agent-development
workspace/design-domain-model
Assess, design or review business-domain models, logical data models and database/API/event schemas with explicit invariants, ownership, representation mappings and compatibility evidence. Use for new domain concepts, lifecycle or consistency rules, and schema evolution; scale simple CRUD changes to a concise model delta.
skm add workspace/design-domain-model
workspace/fix-bug
Reproduce, isolate, and fix a reported software defect with regression coverage. Use when observed behavior differs from a requirement or established contract and the user authorizes a focused implementation change.
skm add workspace/fix-bug
workspace/fix-ci
Diagnose and fix failing continuous-integration checks with the smallest verified change. Use when CI or pull-request checks are failing and the user authorizes implementation, including log inspection, local reproduction, regression coverage, and rerun monitoring.
skm add workspace/fix-ci
workspace/implement-spec
Implement an approved development specification through validated, reviewable changes. Use when a spec is active in development and the request authorizes code or documentation changes, including required tests, compatibility work, lifecycle reconciliation, and memory-impact completion.
skm add workspace/implement-spec
workspace/maintain-project-docs
Create, update, reconcile, or review human-facing project documentation within repository-declared documentation roots. Use when project reference, architecture, operational, onboarding, or work documentation must reflect current repository behavior without changing governed agent instructions.
skm add workspace/maintain-project-docs
workspace/monitor-ci
Monitor a continuous-integration run or pull-request checks through a terminal outcome and report meaningful transitions. Use when the user asks to watch, babysit, follow, or wait for CI without changing code or workflow configuration.
skm add workspace/monitor-ci
workspace/plan-implementation
Build an ordered, evidence-backed implementation plan from an approved development specification. Use when a feature, migration, or refactor has an active spec and needs dependency ordering, concrete file areas, validation strategy, compatibility handling, and completion gates before code changes begin.
skm add workspace/plan-implementation
workspace/report-repository-status
Report repo status, project status or spec status, including local changes, worktrees, local/remote branches and linked specs. Recommend merge, discard candidate or keep/finish from evidence; reporting stays read-only.
skm add workspace/report-repository-status
workspace/review-changes
Review a working tree, branch, commit range, or pull request for correctness, regressions, and missing validation. Use when the user asks for a code review, branch review, pull-request review, or an evidence-backed assessment of proposed changes without implementation.
skm add workspace/review-changes
workspace/review-security
Perform a threat-focused review of code, configuration, dependencies, or proposed changes. Use when a change affects authentication, authorization, secrets, untrusted input, file or network access, supply chain, execution boundaries, sensitive data, or when the user requests a security review.
skm add workspace/review-security
workspace/wk-adopt
Run the wk.adopt lifecycle facade to assess, adopt, repair, or upgrade a repository's Workspace structure through the focused adoption workflow. Invoke explicitly when the user requests Workspace adoption or migration.
skm add workspace/wk-adopt
workspace/wk-analyze
Run the wk.analyze lifecycle facade to produce a read-only, evidence-backed repository assessment. Invoke explicitly when the user wants repository structure, stack, SDLC, policy, documentation, active-work, risk, and gap analysis.
skm add workspace/wk-analyze
workspace/wk-deliver
Run the wk.deliver lifecycle facade to implement, validate, review, remediate, and advance an approved development specification through the repository's authorized delivery workflow. Invoke explicitly for end-to-end delivery rather than read-only review.
skm add workspace/wk-deliver
workspace/wk-document
Run the wk.document lifecycle facade to create or maintain human-facing project documentation within repository ownership boundaries. Invoke explicitly when documentation must be reconciled with current behavior and validated.
skm add workspace/wk-document
workspace/wk-plan
Run the wk.plan lifecycle facade to validate or create an active specification and produce an executable implementation plan. Invoke explicitly when approved work needs ordered steps, affected files, migration handling, validation, rollback, and completion gates.
skm add workspace/wk-plan
workspace/wk-review
Run the wk.review lifecycle facade for a read-only correctness and applicable security review of a working tree, branch, commit range, or pull request. Invoke explicitly when findings and validation gaps are needed without remediation.
skm add workspace/wk-review
workspace/wk-spec
Run the wk.spec lifecycle facade to turn an accepted request into a complete, categorized, lifecycle-managed development specification. Invoke explicitly when implementation needs scope, acceptance criteria, affected areas, validation, risks, and memory impact.
skm add workspace/wk-spec
workspace/write-spec
Turn an accepted problem or feature request into a lifecycle-managed development specification. Use when work needs explicit scope, acceptance criteria, affected areas, validation gates, risks, migration considerations, and memory impact before implementation begins.
skm add workspace/write-spec
Nothing matches that. Clear the search, or contribute the one you need.