create-skill

Drafts and version-controls Claude skills via SKILL.md files in a dotfiles repository.

Updated Feb 9, 2025
One-click install
npx skills add https://github.com/carter2099/.dotfiles-homelab --skill create-skill-carter2099
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/carter2099/.dotfiles-homelab/tree/main/.claude/skills/create-skill
Command: npx skills add https://github.com/carter2099/.dotfiles-homelab --skill create-skill-carter2099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines creating and versioning Claude Skills by generating the SKILL.md for a new skill under ~/.claude/skills/ and ensuring it is committed to the dotfiles repository for backup on GitHub.

Core Features & Use Cases

  • Create a new skill directory under ~/.claude/skills/<name>/SKILL.md with required frontmatter.
  • Automatically commit the new skill to the dotfiles repository and push to GitHub to ensure backup.
  • Validate frontmatter fields and keep skills tracked for easy discovery and re-use.

Quick Start

Create a new skill under ~/.claude/skills/<name>/SKILL.md and commit it to the dotfiles repository.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a new Claude skill and back it up to my dotfiles repository?

To create a Claude skill and back it up, draft a SKILL.md file under ~/.claude/skills/<name>/ with required frontmatter, then commit and push it to your dotfiles repository on GitHub for version control and recovery.

What frontmatter fields are required when generating a SKILL.md file for Claude?

When generating a SKILL.md file for Claude, the mandatory frontmatter fields are name and description, ensuring the skill is properly formatted, discoverable, and tracked within the ~/.claude/skills directory structure.

How does versioning Claude skills with dotfiles work for backup and recovery?

Versioning Claude skills with dotfiles works by committing the generated SKILL.md files from the ~/.claude/skills directory directly to your dotfiles repository and pushing them to GitHub, ensuring continuous backup and easy re-use across environments.

Do I need a specific directory structure to add new skills to ~/.claude/skills?

Yes, adding new skills requires a specific directory structure: you must place a mandatory SKILL.md file at the root of a new directory named ~/.claude/skills/<name>/ to ensure proper validation and tracking.

What is the best way to manage Claude skill creation and ensure it is tracked in version control?

The best way to manage Claude skill creation and version control is to enforce a workflow that drafts the SKILL.md file with proper frontmatter and immediately commits and pushes the new skill directory to your dotfiles repository.

Why should I commit my Claude skills to a dotfiles repository instead of keeping them local?

Committing Claude skills to a dotfiles repository ensures your SKILL.md files are backed up on GitHub, keeping your skills tracked, easily discoverable for re-use, and recoverable across different development environments.