Turn any workflow into reusable AI agent skills that install on 14+ tools — Clau
Find a file
francylisboacharuto 96e546ffdd feat: Clarity principles, edge case coverage, auto-install, clean README
- Embed clarity principles in Stage 1 (self-guided, no external dependency)
- Add refactoring guidance for growing skills (architecture-guide)
- Add cross-component communication patterns for suites (architecture-guide)
- Add versioning strategy with semver rules (architecture-guide)
- Add suite orchestration patterns with routing logic (multi-agent-guide)
- Add dependency management framework — stdlib first (quality-standards)
- Add testing strategy with patterns and fixtures (quality-standards)
- Add auto-install step in Phase 5 — detect platform, install, show next steps
- Rewrite README for broader audience — 788 to 318 lines, no jargon

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-27 04:03:13 -03:00
exports chore: Remove non-essential files — lean working set 2026-02-27 02:42:11 -03:00
references feat: Clarity principles, edge case coverage, auto-install, clean README 2026-02-27 04:03:13 -03:00
registry docs: Update registry workflow for corporate teams 2026-02-26 16:19:34 -03:00
scripts feat: Add git-based shared skill registry for team skill management 2026-02-26 15:52:19 -03:00
.gitignore chore: Remove non-essential files — lean working set 2026-02-27 02:42:11 -03:00
README.md feat: Clarity principles, edge case coverage, auto-install, clean README 2026-02-27 04:03:13 -03:00
SKILL.md feat: Clarity principles, edge case coverage, auto-install, clean README 2026-02-27 04:03:13 -03:00

Agent Skill Creator

Turn any workflow into reusable AI agent software — no spec writing, no prompt engineering, no coding required.

Agent Skills Open Standard Version License: MIT


The Problem

Every AI agent (Claude Code, GitHub Copilot, Cursor, Windsurf, Codex, Gemini) starts from zero. It doesn't know your company's processes, data sources, or compliance requirements. So every person re-explains the same workflows in every conversation. Knowledge stays in individual chat histories. New hires start from scratch.

Agent skills fix this. A skill is structured knowledge your agent loads automatically — like installing an app. Once installed, anyone on your team can invoke it and get consistent results, every time, on any platform.

The catch: building a proper skill requires understanding the spec format, writing clear prompt instructions, designing how information loads progressively, writing functional code, and getting activation keywords right. Even simple skills take multiple rounds of iteration to get right.

Agent Skill Creator removes that barrier entirely. You pass in whatever you have — messy docs, links, code, PDFs, transcripts, vague descriptions — and it produces a validated, security-scanned skill ready to install and share. You describe what you do; it builds the software.


Quick Start

1. Install (one command)

# Claude Code
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git ~/.claude/skills/agent-skill-creator

# VS Code with GitHub Copilot
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .github/skills/agent-skill-creator

# Cursor
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .cursor/rules/agent-skill-creator

Other platforms: see full list below.

2. Use it

Open your agent and type /agent-skill-creator followed by whatever you have:

/agent-skill-creator Every week I pull sales data from our CRM, clean
duplicate entries, calculate regional totals, and generate a PDF report.

You can pass anything — plain English, documentation links, existing code, API docs, PDFs, database schemas, transcripts. Combine multiple sources in one message. The more context, the better the result.

/agent-skill-creator Based on our deployment runbook: https://wiki.internal/deploy-process
/agent-skill-creator See scripts/invoice_processor.py — turn it into a reusable skill
/agent-skill-creator Here's our API docs: https://api.internal/docs
Create a skill that queries stock levels and generates reorder reports.

3. What comes out

A complete skill, automatically installed on your platform:

Skill installed successfully.

To use it, open a new session and type:

  /sales-report-builder Generate the weekly report for the West region

Installed at: ~/.claude/skills/sales-report-builder

The agent detects your platform (Claude Code, Cursor, Copilot, etc.), installs the skill to the right location, and tells you exactly how to invoke it. No manual steps.

The generated skill directory looks like this:

sales-report-builder/
├── SKILL.md          # Skill definition (activates with /sales-report-builder)
├── scripts/          # Functional Python code
├── references/       # Detailed documentation
├── assets/           # Templates, configs
├── install.sh        # Cross-platform installer (for sharing with others)
└── README.md         # Installation instructions (for sharing with others)

Your team installs it the same way they installed agent-skill-creator — one git clone — and invokes it with /sales-report-builder. The included install.sh auto-detects their platform too.


How It Works

You don't need to understand any of this to use it. But if you're curious:

The agent doesn't just follow your description literally. Humans describe what they do, not what they need. "I pull sales data and make a report" hides a dozen implicit requirements — who reads the report, what format, what happens when data is missing. The agent reads all your material, uncovers these implicit requirements, and generates its own internal specification before writing any code. It builds from that deeper understanding, not from your surface description.

UNDERSTAND    Read all material → uncover real intent → generate internal spec
BUILD         Structure directory → write code and docs → craft activation keywords
VERIFY        Spec validation → security scan → block delivery if either fails

Every skill is automatically validated (correct structure, naming, metadata) and security-scanned (no hardcoded keys, no credential exposure, no injection risks) before delivery. Skills that fail these checks are blocked.


Share Skills Across Your Team

Once a skill is created, publish it so everyone can use it.

Publish

python3 scripts/skill_registry.py publish ./sales-report-builder/ --tags sales,reports,crm
git add registry/ && git commit -m "Add sales-report-builder skill" && git push

Discover

git pull
python3 scripts/skill_registry.py list

# NAME                    VERSION  AUTHOR        TAGS
# sales-report-builder    1.2.0    sales-team    sales, reports, crm
# deploy-checklist        2.1.0    engineering   deploy, ci, checklist
# quarterly-compliance    1.0.0    legal-team    compliance, audit

python3 scripts/skill_registry.py search "sales"
python3 scripts/skill_registry.py info sales-report-builder

Install

python3 scripts/skill_registry.py install sales-report-builder

Auto-detects your platform (Claude Code, Cursor, etc.) and installs to the right location.

The result over time

Each team contributes skills from their domain. Operations teams capture runbooks. Data teams capture analysis pipelines. Finance teams capture reporting workflows. Engineering teams capture deployment processes. The organization builds a living library of operational knowledge that every agent can access.


All Platforms

Works in IDEs and CLI tools. Same install, same invocation, same results.

IDEs

# VS Code with GitHub Copilot
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .github/skills/agent-skill-creator

# Cursor
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .cursor/rules/agent-skill-creator

# Windsurf
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .windsurf/skills/agent-skill-creator

# Cline (VS Code Extension)
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .clinerules/agent-skill-creator

CLI Tools

# Claude Code (personal — available in all projects)
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git ~/.claude/skills/agent-skill-creator

# Claude Code (per-project)
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .claude/skills/agent-skill-creator

# GitHub Copilot CLI
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .github/skills/agent-skill-creator

# OpenAI Codex CLI
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .codex/skills/agent-skill-creator

# Gemini CLI
git clone https://github.com/FrancyJGLisboa/agent-skill-creator.git .gemini/skills/agent-skill-creator

Claude Desktop / claude.ai

python3 scripts/export_utils.py ./agent-skill-creator/ --variant desktop
# Then: Settings > Skills > Upload the generated .zip

Update

cd ~/.claude/skills/agent-skill-creator && git pull

Quality Gates

Every skill goes through automated checks before delivery and on every publish:

Gate What It Checks
Spec Validation SKILL.md structure, frontmatter format, naming rules, file references
Security Scan No hardcoded API keys, no credentials, no injection patterns

Run them independently anytime:

python3 scripts/validate.py ./my-skill/
python3 scripts/security_scan.py ./my-skill/

Skills that fail validation cannot be published. Skills with high-severity security issues are blocked.


Tools Reference

Registry Commands

python3 scripts/skill_registry.py init --name "Acme Corp Skills"     # First-time setup
python3 scripts/skill_registry.py publish ./skill/ --tags t1,t2      # Publish a skill
python3 scripts/skill_registry.py list                                # Browse all skills
python3 scripts/skill_registry.py search "query"                     # Search skills
python3 scripts/skill_registry.py info skill-name                    # Skill details
python3 scripts/skill_registry.py install skill-name                 # Install a skill
python3 scripts/skill_registry.py remove skill-name --force          # Remove a skill

Validation and Security

python3 scripts/validate.py ./skill/               # Spec compliance
python3 scripts/validate.py ./skill/ --json         # Machine-readable output
python3 scripts/security_scan.py ./skill/           # Security audit
python3 scripts/security_scan.py ./skill/ --json    # Machine-readable output

Export

python3 scripts/export_utils.py ./skill/ --variant desktop    # For Claude Desktop
python3 scripts/export_utils.py ./skill/ --variant api        # For Claude API

All commands use exit code 0 for success, 1 for errors. All support --json for CI/CD integration.


Troubleshooting

Skill not activating: Check that the SKILL.md description field contains keywords matching your query. The description is how the agent decides when to activate the skill.

Validation fails on name: Names must be lowercase, use hyphens between words, 1-64 characters. Examples: sales-report-builder, deploy-checklist.

SKILL.md too long: Move detailed content to references/ files and link from the main SKILL.md.

Platform not auto-detected: Use --platform cursor (or copilot, windsurf, etc.) to specify explicitly.


Project Structure

agent-skill-creator/
  SKILL.md                      # The skill definition (what the agent reads)
  README.md                     # This file
  scripts/
    validate.py                 # Spec compliance checker
    security_scan.py            # Security scanner
    export_utils.py             # Cross-platform export
    skill_registry.py           # Team skill registry
    install-template.sh         # Template for generated installers
  references/                   # Detailed docs (loaded by the agent on demand)
    pipeline-phases.md          # Full creation pipeline
    architecture-guide.md       # Skill structure decisions
    quality-standards.md        # Code and documentation standards
    multi-agent-guide.md        # Multi-skill suite creation
    cross-platform-guide.md     # Platform compatibility
    export-guide.md             # Export documentation
    templates-guide.md          # Template system
    interactive-mode.md         # Interactive wizard
    agentdb-integration.md      # Learning system
    phase1-discovery.md         # Phase 1 deep dive
    phase2-design.md            # Phase 2 deep dive
    phase3-architecture.md      # Phase 3 deep dive
    phase4-detection.md         # Phase 4 deep dive
    phase5-implementation.md    # Phase 5 deep dive
    templates/                  # Skill templates
    examples/stock-analyzer/    # Example skill
  registry/                     # Shared skill catalog
    registry.json
    skills/
  exports/                      # Export output

Contributing

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Run python3 scripts/validate.py ./ and python3 scripts/security_scan.py ./
  5. Submit a pull request

License

MIT