Agent skill

Skill Creator

by aiskillstore in aiskillstore/marketplace

This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities.

Apache-2.0Auto-check passedAgent Workflows

Install Skill Creator

skills CLI
$ npx skills add aiskillstore/marketplace --skill skill-creator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aiskillstore/marketplace skill-creator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aiskillstore/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sickn33/skill-creator .claude/skills/skill-creator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
skill-creator
GitHub stars
430
Used in
4 other repos
Token cost
~4.6k tokens
SKILL.md length
922 words
Files
9 (incl. scripts, references)
Skills in repo
1,108
Repo updated
First seen
Licence
Apache-2.0

At a glance

This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities.

  • Asks to create a new skill
  • SKILL.md covers Purpose, When to Use This Skill, Core Capabilities and Step 0: Discovery, plus 6 more sections
  • Runs Python scripts from its folder; calls git and gh
  • Make a custom skill

What it does

Skill Creator is an agent skill from aiskillstore/marketplace. This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `README.md`, `references/output-patterns.md` and `references/workflows.md`).

It sits in Agent Workflows, covering Skill authoring and Brainstorming. The repository describes itself as: Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified. The licence is Apache-2.0.

When your agent uses it

  • Asks to create a new skill
  • Make a custom skill
  • Develop a CLI skill
  • Wants to extend the CLI with new capabilities

Example prompts

  • “/skill-creator”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit ad8daf7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Skill Creator loads about 4.6k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 922 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from aiskillstore/marketplace at commit ad8daf7, republished under its Apache-2.0 licence (© aiskillstore). 922 words, ~4,613 tokens.

Download SKILL.mdSave it as .claude/skills/skill-creator/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
skill-creator
description
This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Automates the entire skill creation workflow from brainstorming to installation.
version
1.3.0
author
Eric Andrade
created
2025-02-01
updated
2026-02-04
platforms
github-copilot-cli, claude-code, codex
category
meta
tags
automation, scaffolding, skill-creation, meta-skill
risk
safe

skill-creator

Purpose

To create new CLI skills following Anthropic's official best practices with zero manual configuration. This skill automates brainstorming, template application, validation, and installation processes while maintaining progressive disclosure patterns and writing style standards.

When to Use This Skill

This skill should be used when:

  • User wants to extend CLI functionality with custom capabilities
  • User needs to create a skill following official standards
  • User wants to automate repetitive CLI tasks with a reusable skill
  • User needs to package domain knowledge into a skill format
  • User wants both local and global skill installation options

Core Capabilities

  1. Interactive Brainstorming - Collaborative session to define skill purpose and scope
  2. Prompt Enhancement - Optional integration with prompt-engineer skill for refinement
  3. Template Application - Automatic file generation from standardized templates
  4. Validation - YAML, content, and style checks against Anthropic standards
  5. Installation - Local repository or global installation with symlinks
  6. Progress Tracking - Visual gauge showing completion status at each step

Step 0: Discovery

Before starting skill creation, gather runtime information:

bash
# Detect available platforms
COPILOT_INSTALLED=false
CLAUDE_INSTALLED=false
CODEX_INSTALLED=false

if command -v gh &>/dev/null && gh copilot --version &>/dev/null 2>&1; then
    COPILOT_INSTALLED=true
fi

if [[ -d "$HOME/.claude" ]]; then
    CLAUDE_INSTALLED=true
fi

if [[ -d "$HOME/.codex" ]]; then
    CODEX_INSTALLED=true
fi

# Determine working directory
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)
SKILLS_REPO="$REPO_ROOT"

# Check if in cli-ai-skills repository
if [[ ! -d "$SKILLS_REPO/.github/skills" ]]; then
    echo "⚠️  Not in cli-ai-skills repository. Creating standalone skill."
    STANDALONE=true
fi

# Get user info from git config
AUTHOR=$(git config user.name || echo "Unknown")
EMAIL=$(git config user.email || echo "")

Key Information Needed:

  • Which platforms to target (Copilot, Claude, Codex, or all three)
  • Installation preference (local, global, or both)
  • Skill name and purpose
  • Skill type (general, code, documentation, analysis)

Main Workflow

Progress Tracking Guidelines

Throughout the workflow, display a visual progress bar before starting each phase to keep the user informed. The progress bar format is:

[████████████░░░░░░] 60% - Step 3/5: Creating SKILL.md

Format specifications:

  • 20 characters wide (use █ for filled, ░ for empty)
  • Percentage based on current step (Step 1=20%, Step 2=40%, Step 3=60%, Step 4=80%, Step 5=100%)
  • Step counter showing current/total (e.g., "Step 3/5")
  • Brief description of current phase

Display the progress bar using:

bash
echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"
Phase 1: Brainstorming & Planning

Progress: Display before starting this phase:

bash
echo "[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning"

Display progress:

╔══════════════════════════════════════════════════════════════╗
║     🛠️  SKILL CREATOR - Creating New Skill                  ║
╠══════════════════════════════════════════════════════════════╣
║ → Phase 1: Brainstorming                 [10%]               ║
║ ○ Phase 2: Prompt Refinement                                 ║
║ ○ Phase 3: File Generation                                   ║
║ ○ Phase 4: Validation                                        ║
║ ○ Phase 5: Installation                                      ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ███░░░░░░░░░░░░░░░░░░░░░░░░░░░  10%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user:

  1. What should this skill do? (Free-form description)

    • Example: "Help users debug Python code by analyzing stack traces"
  2. When should it trigger? (Provide 3-5 trigger phrases)

    • Example: "debug Python error", "analyze stack trace", "fix Python exception"
  3. What type of skill is this?

    • General purpose (default template)
    • Code generation/modification
    • Documentation creation/maintenance
    • Analysis/investigation
  4. Which platforms should support this skill?

    • GitHub Copilot CLI
    • Claude Code
    • Codex
    • All three (recommended)
  5. Provide a one-sentence description (will appear in metadata)

    • Example: "Analyzes Python stack traces and suggests fixes"

Capture responses and prepare for next phase.

Phase 2: Prompt Enhancement (Optional)

Progress: Display before starting this phase:

bash
echo "[████████░░░░░░░░░░] 40% - Step 2/5: Prompt Enhancement"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 1: Brainstorming                                     ║
║ → Phase 2: Prompt Refinement             [30%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: █████████░░░░░░░░░░░░░░░░░░░░░  30%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user: "Would you like to refine the skill description using the prompt-engineer skill?"

  • Yes - Use prompt-engineer to enhance clarity and structure
  • No - Proceed with current description

If Yes:

  1. Check if prompt-engineer skill is available
  2. Invoke with current description as input
  3. Review enhanced output with user
  4. Ask: "Accept enhanced version or keep original?"

If No or prompt-engineer unavailable:

  • Proceed with original user input
Phase 3: File Generation

Progress: Display before starting this phase:

bash
echo "[████████████░░░░░░] 60% - Step 3/5: File Generation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 1: Brainstorming                                     ║
║ ✓ Phase 2: Prompt Refinement                                 ║
║ → Phase 3: File Generation               [50%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ███████████████░░░░░░░░░░░░░░░  50%              ║
╚══════════════════════════════════════════════════════════════╝

Generate skill structure:

bash
# Convert skill name to kebab-case
SKILL_NAME=$(echo "$USER_INPUT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-')

# Create directories
if [[ "$PLATFORM" =~ "copilot" ]]; then
    mkdir -p ".github/skills/$SKILL_NAME"/{references,examples,scripts}
fi

if [[ "$PLATFORM" =~ "claude" ]]; then
    mkdir -p ".claude/skills/$SKILL_NAME"/{references,examples,scripts}
fi

if [[ "$PLATFORM" =~ "codex" ]]; then
    mkdir -p ".codex/skills/$SKILL_NAME"/{references,examples,scripts}
fi

Apply templates:

  1. SKILL.md - Use appropriate template:

    • skill-template-copilot.md, skill-template-claude.md, or skill-template-codex.md
    • Substitute placeholders:
      • {{SKILL_NAME}} → kebab-case name
      • {{DESCRIPTION}} → one-line description
      • {{TRIGGERS}} → comma-separated trigger phrases
      • {{PURPOSE}} → detailed purpose from brainstorming
      • {{AUTHOR}} → from git config
      • {{DATE}} → current date (YYYY-MM-DD)
      • {{VERSION}} → "1.0.0"
  2. README.md - Use readme-template.md:

    • User-facing documentation (300-500 words)
    • Include installation instructions
    • Add usage examples
  3. References/ (optional but recommended):

    • Create detailed-guide.md for extended documentation (2k-5k words)
    • Move lengthy content here to keep SKILL.md under 2k words

File creation commands:

bash
# Apply template with substitution
sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
     s/{{DESCRIPTION}}/$DESCRIPTION/g; \
     s/{{AUTHOR}}/$AUTHOR/g; \
     s/{{DATE}}/$(date +%Y-%m-%d)/g" \
    resources/templates/skill-template-copilot.md \
    > ".github/skills/$SKILL_NAME/SKILL.md"

# Create README
sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
    resources/templates/readme-template.md \
    > ".github/skills/$SKILL_NAME/README.md"

# Apply template for Codex if selected
if [[ "$PLATFORM" =~ "codex" ]]; then
    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g; \
         s/{{DESCRIPTION}}/$DESCRIPTION/g; \
         s/{{AUTHOR}}/$AUTHOR/g; \
         s/{{DATE}}/$(date +%Y-%m-%d)/g" \
        resources/templates/skill-template-codex.md \
        > ".codex/skills/$SKILL_NAME/SKILL.md"
    
    sed "s/{{SKILL_NAME}}/$SKILL_NAME/g" \
        resources/templates/readme-template.md \
        > ".codex/skills/$SKILL_NAME/README.md"
fi

Display created structure:

✅ Created:
   .github/skills/your-skill-name/ (if Copilot selected)
   .claude/skills/your-skill-name/ (if Claude selected)
   .codex/skills/your-skill-name/ (if Codex selected)
   ├── SKILL.md (832 lines)
   ├── README.md (347 lines)
   ├── references/
   ├── examples/
   └── scripts/
Show full SKILL.md (374 more words)Show less
Phase 4: Validation

Progress: Display before starting this phase:

bash
echo "[████████████████░░] 80% - Step 4/5: Validation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 3: File Generation                                   ║
║ → Phase 4: Validation                    [70%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: █████████████████████░░░░░░░░░  70%              ║
╚══════════════════════════════════════════════════════════════╝

Run validation scripts:

bash
# Validate YAML frontmatter
scripts/validate-skill-yaml.sh ".github/skills/$SKILL_NAME"

# Validate content quality
scripts/validate-skill-content.sh ".github/skills/$SKILL_NAME"

Expected output:

🔍 Validating YAML frontmatter...
✅ YAML frontmatter valid!

🔍 Validating content...
✅ Word count excellent: 1847 words
✅ Content validation complete!

If validation fails:

  • Display specific errors
  • Offer to fix automatically (common issues)
  • Ask user to manually correct complex issues

Common auto-fixes:

  • Convert second-person to imperative form
  • Reformat description to third-person
  • Add missing required fields
Phase 5: Installation

Progress: Display before starting this phase:

bash
echo "[████████████████████] 100% - Step 5/5: Installation"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 4: Validation                                        ║
║ → Phase 5: Installation                  [90%]               ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████░░░░░  90%              ║
╚══════════════════════════════════════════════════════════════╝

Ask the user: "How would you like to install this skill?"

  • Repository only - Files created in .github/skills/ (works when in repo)
  • Global installation - Create symlinks in ~/.copilot/skills/ (works everywhere)
  • Both - Repository + global symlinks (recommended, auto-updates with git pull)
  • Skip installation - Just create files

If global installation selected:

bash
# Detect which platforms to install for
INSTALL_TARGETS=()

if [[ "$COPILOT_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "copilot" ]]; then
    INSTALL_TARGETS+=("copilot")
fi

if [[ "$CLAUDE_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "claude" ]]; then
    INSTALL_TARGETS+=("claude")
fi

if [[ "$CODEX_INSTALLED" == "true" ]] && [[ "$PLATFORM" =~ "codex" ]]; then
    INSTALL_TARGETS+=("codex")
fi

# Ask user to confirm detected platforms
echo "Detected platforms: ${INSTALL_TARGETS[*]}"
echo "Install for these platforms? [Y/n]"

Installation process:

bash
# GitHub Copilot CLI
if [[ " ${INSTALL_TARGETS[*]} " =~ " copilot " ]]; then
    ln -sf "$SKILLS_REPO/.github/skills/$SKILL_NAME" \
           "$HOME/.copilot/skills/$SKILL_NAME"
    echo "✅ Installed for GitHub Copilot CLI"
fi

# Claude Code
if [[ " ${INSTALL_TARGETS[*]} " =~ " claude " ]]; then
    ln -sf "$SKILLS_REPO/.claude/skills/$SKILL_NAME" \
           "$HOME/.claude/skills/$SKILL_NAME"
    echo "✅ Installed for Claude Code"
fi

# Codex
if [[ " ${INSTALL_TARGETS[*]} " =~ " codex " ]]; then
    ln -sf "$SKILLS_REPO/.codex/skills/$SKILL_NAME" \
           "$HOME/.codex/skills/$SKILL_NAME"
    echo "✅ Installed for Codex"
fi

Verify installation:

bash
# Check symlinks
ls -la ~/.copilot/skills/$SKILL_NAME 2>/dev/null
ls -la ~/.claude/skills/$SKILL_NAME 2>/dev/null
ls -la ~/.codex/skills/$SKILL_NAME 2>/dev/null
Phase 6: Completion

Progress: Display completion message:

bash
echo "[████████████████████] 100% - ✓ Skill created successfully!"

Update progress:

╔══════════════════════════════════════════════════════════════╗
║ ✓ Phase 5: Installation                                      ║
║ ✅ SKILL CREATION COMPLETE!                                  ║
╠══════════════════════════════════════════════════════════════╣
║ Progress: ██████████████████████████████  100%              ║
╚══════════════════════════════════════════════════════════════╝

Display summary:

🎉 Skill created successfully!

📦 Skill Name: your-skill-name
📁 Location: .github/skills/your-skill-name/
🔗 Installed: Global (Copilot + Claude)

📋 Files Created:
   ✅ SKILL.md (1,847 words)
   ✅ README.md (423 words)
   ✅ references/ (empty, ready for extended docs)
   ✅ examples/ (empty, ready for code samples)
   ✅ scripts/ (empty, ready for utilities)

🚀 Next Steps:
   1. Test the skill: Try trigger phrases in CLI
   2. Add examples: Create working code samples in examples/
   3. Extend docs: Add detailed guides to references/
   4. Commit changes: git add .github/skills/your-skill-name && git commit
   5. Share: Push to repository for team use

💡 Pro Tips:
   - Keep SKILL.md under 2,000 words (currently: 1,847)
   - Move detailed content to references/ folder
   - Add executable scripts to scripts/ folder
   - Update README.md with real usage examples
   - Run validation before committing: scripts/validate-skill-yaml.sh

Error Handling

Platform Detection Issues

If platforms cannot be detected:

⚠️  Unable to detect GitHub Copilot CLI or Claude Code
    
Would you like to:
1. Install for repository only (works when in repo)
2. Specify platform manually
3. Skip installation
Template Not Found

If templates are missing:

❌ Error: Template not found at resources/templates/

This skill requires the cli-ai-skills repository structure.

Options:
1. Clone cli-ai-skills: git clone <repo-url>
2. Create minimal skill structure manually
3. Exit and set up templates first
Validation Failures

If content doesn't meet standards:

⚠️  Validation Issues Found:

1. YAML: Description not in third-person format
   Expected: "This skill should be used when..."
   Found: "Use this skill when..."
   
2. Content: Word count too high (5,342 words, max 5,000)
   Suggestion: Move detailed sections to references/

Fix automatically? [Y/n]
Installation Conflicts

If symlink already exists:

⚠️  Skill already installed at ~/.copilot/skills/your-skill-name

Options:
1. Overwrite existing installation
2. Rename new skill
3. Skip installation
4. Install to different location

Bundled Resources

This skill includes additional resources in subdirectories:

references/

Detailed documentation loaded when needed:

  • anthropic-best-practices.md - Official Anthropic skill development guidelines
  • writing-style-guide.md - Writing standards and examples
  • progressive-disclosure.md - Content organization patterns
  • validation-checklist.md - Pre-commit quality checks
examples/

Working examples demonstrating skill usage:

  • basic-skill-creation.md - Simple skill creation walkthrough
  • advanced-skill-bundled-resources.md - Complex skill with references/
  • global-installation.md - Installing skills system-wide
scripts/

Executable utilities for skill maintenance:

  • validate-all-skills.sh - Batch validation of all skills in repository
  • update-skill-version.sh - Bump version and update changelog
  • generate-skill-index.sh - Auto-generate skills catalog

Technical Implementation Notes

Template Substitution:

  • Use sed for simple replacements
  • Preserve YAML formatting exactly
  • Handle multi-line descriptions with proper escaping

Symlink Strategy:

  • Always use absolute paths: ln -sf /full/path/to/source ~/.copilot/skills/name
  • Verify symlink before considering installation complete
  • Benefits: Auto-updates when repository is pulled

Validation Integration:

  • Run validation before installation
  • Block installation if critical errors found
  • Warnings are informational only

Git Integration:

  • Extract author from git config user.name
  • Use repository root detection: git rev-parse --show-toplevel
  • Respect .gitignore patterns

Quality Standards

SKILL.md Requirements:

  • 1,500-2,000 words (ideal)
  • Under 5,000 words (maximum)
  • Third-person description format
  • Imperative/infinitive writing style
  • Progressive disclosure pattern

README.md Requirements:

  • 300-500 words
  • User-facing language
  • Clear installation instructions
  • Practical usage examples

Validation Checks:

  • YAML frontmatter completeness
  • Description format (third-person)
  • Word count limits
  • Writing style (no second-person)
  • Required fields present

References

© aiskillstore, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (scripts, references) in skills/sickn33/skill-creator of aiskillstore/marketplace.

  • SKILL.md
  • LICENSE.txt
  • README.md
  • references/output-patterns.md
  • references/workflows.md
  • scripts/init_skill.py
  • scripts/package_skill.py
  • scripts/quick_validate.py
  • skill-report.json

Open the folder on GitHubat commit ad8daf7

Used in 4 other repositories

We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in aiskillstore/marketplace, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Skill Creator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Skill Creator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skill Creator this skillaiskillstore/marketplace4304 repos~4.6kAutomated safety check: PassApache-2.0
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Brainstormingxpinjection/test-driven-spring-boot11254 repos~2.6kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official38k10 repos~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Brainstorming

    xpinjection/test-driven-spring-boot

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

    112 GitHub starsUsed in 54 repos~2.6k tokens
    Agent WorkflowsAuto-check passed
  • Darwin Skill Optimizer

    alchaincyf/darwin-skill

    Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    38k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed

More from aiskillstore/marketplace

All 1,108 skills in this repo
  • Code Stats

    aiskillstore/marketplace

    Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs).

    430 GitHub starsUsed in 2 repos~697 tokens
    Auto-check: notes
  • File Search

    aiskillstore/marketplace

    Modern file and content search using fd, ripgrep (rg), and fzf.

    430 GitHub starsUsed in 2 repos~598 tokens
    Auto-check: notes
  • Data Processing

    aiskillstore/marketplace

    Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.

    430 GitHub starsUsed in 1 repo~720 tokens
    Auto-check: notes
  • Doc Scanner

    aiskillstore/marketplace

    Scans for project documentation files (AGENTS.md, CLAUDE.md, GEMINI.md, COPILOT.md, CURSOR.md, WARP.md, and 15+ other formats) and synthesizes guidance.

    430 GitHub starsUsed in 1 repo~644 tokens
    Auto-check: notes
  • Find Replace

    aiskillstore/marketplace

    Modern find-and-replace using sd (simpler than sed) and batch replacement patterns.

    430 GitHub starsUsed in 1 repo~527 tokens
    Auto-check: notes
  • Investigating Codebases

    aiskillstore/marketplace

    Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y…

    430 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check: notes

Categories

Questions about Skill Creator

What does Skill Creator do?

This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities. Skill Creator is an agent skill from aiskillstore/marketplace. This skill should be used when the user asks to create a new skill, build a skill, make a custom skill, develop a CLI skill, or wants to extend the CLI with new capabilities.

When should I use Skill Creator?

Skill Creator fits situations like: asks to create a new skill; make a custom skill; develop a CLI skill; wants to extend the CLI with new capabilities.

How do I install Skill Creator in Claude Code?

Run `npx skills add aiskillstore/marketplace --skill skill-creator -a claude-code`. Or copy the skill folder (skills/sickn33/skill-creator in aiskillstore/marketplace) into .claude/skills/skill-creator in your project. Claude Code loads it when a task matches its description.

How do I install Skill Creator in Codex?

Run `npx skills add aiskillstore/marketplace --skill skill-creator -a codex`. Or copy the skill folder (skills/sickn33/skill-creator in aiskillstore/marketplace) into .agents/skills/skill-creator in your project. Codex loads it when a task matches its description.

Can I use Skill Creator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiskillstore/marketplace --skill skill-creator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-creator, .gemini/skills/skill-creator, .github/skills/skill-creator and .opencode/skills/skill-creator in your project.

What does Skill Creator need to run?

Going by SKILL.md and its folder, Skill Creator needs Python for the scripts in its folder and the command-line tools its instructions call (git and gh). Our summary lists: Python 3.

Does Skill Creator access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Skill Creator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Skill Creator use?

Skill Creator is published under the Apache-2.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skill Creator use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 658 tokens, read only when the agent opens those files.

What are the alternatives to Skill Creator?

Skills that share tags, products or a category with Skill Creator: Skill Creator (Azure/azqr, 795 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Brainstorming (xpinjection/test-driven-spring-boot, 112 stars) and Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skill Creator?

aiskillstore (a GitHub organization) maintains it in aiskillstore/marketplace, which has 430 GitHub stars. The repository holds 1,108 skills in this directory. The repository was last updated on October 7, 2026.

Source: aiskillstore/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.