dm-skill-creator

Create and maintain shared skills in the darkmatter/skills repository.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill dm-skill-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dm-skill-creator
Source: https://github.com/darkmatter/skills/tree/main/skills/dm-skill-creator
Command: npx skills add https://github.com/darkmatter/skills --skill dm-skill-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps turn a recurring team workflow into a reusable darkmatter skill that lives in the shared catalog, follows repo conventions, and can be distributed through the flake and Claude Code plugin without extra setup.

Core Features & Use Cases

  • Skill naming and scaffolding for the darkmatter/skills repository, including the correct directory layout and frontmatter fields.
  • Validation and packaging guidance so the skill passes the repo’s checks and remains self-contained.
  • Catalog and rollout support for skills that need to be shared across multiple darkmatter projects, such as refactoring an existing workflow into a reusable team capability.

Quick Start

Ask me to create or update a shared darkmatter skill for your workflow, and I will scaffold it, draft the instructions, validate it, and prepare the catalog and rollout steps.

Frequently Asked Questions about dm-skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a shared skill for the darkmatter repository?▼

To create a shared darkmatter skill, you scaffold the correct directory layout, draft frontmatter and instructions, and validate it for self-containment. This ensures reusable workflows ship cleanly through the flake and Claude Code plugin without extra setup.

What validation conventions must reusable Claude Code skills follow?▼

Reusable Claude Code skills must follow naming, frontmatter, self-containment, and end-to-end rebuild conventions. Validation enforces these rules so shared skills pass repository checks and remain self-contained across multiple projects.

How do I package a team workflow for distribution through a Nix flake?▼

Packaging a team workflow for Nix flake distribution involves cataloging the workflow as a shared skill and enforcing self-contained validation. This prepares the workflow to ship through the flake and Claude Code plugin across projects.

Does home-manager support shared skills created with this workflow?▼

Home-manager supports shared skills created through this workflow because they ship cleanly via the Nix flake. The workflow enforces self-containment and naming conventions ensuring skills integrate directly with home-manager configurations.

When do I need to refactor a workflow into a cataloged darkmatter skill?▼

You need to refactor a workflow into a cataloged darkmatter skill when a recurring team workflow requires distribution across multiple projects. This process applies validation and cataloging conventions to make the capability reusable team-wide.