✨ What are Skills?

Skills are packaged instructions and resources that extend AI agent capabilities. Think of them as plugins for your AI assistant — they teach your agent new workflows, patterns, and specialized knowledge.

skills/
  spec-driven-dev/
    SKILL.md          ← Main instructions
    templates/        ← File templates
    references/       ← On-demand documentation

🚀 Quick Start

Install Skills in Your Project

npx @tech-leads-club/agent-skills

This launches an interactive wizard with 5 steps:

1. Browse categories — Filter skills by category or select "All"
2. Select skills — Choose which skills to install
3. Choose agents — Pick target agents (Cursor, Claude Code, etc.)
4. Installation method — Symlink (recommended) or Copy
5. Scope — Global (user home) or Local (project only)

Each step shows a ← Back option to return to the previous step and revise your choices. A confirmation summary is shown before installation.

CLI Options

# Interactive mode (default)
npx @tech-leads-club/agent-skills

# Install globally (to ~/.gemini/antigravity/global_skills, ~/.claude/skills, etc.)
npx @tech-leads-club/agent-skills install -g

# List available skills
npx @tech-leads-club/agent-skills list

# Install a specific skill
npx @tech-leads-club/agent-skills install -s spec-driven-dev

# Install to specific agents
npx @tech-leads-club/agent-skills install -a antigravity cursor

# Use copy instead of symlink
npx @tech-leads-club/agent-skills install --copy

# Remove skills (interactive)
npx @tech-leads-club/agent-skills remove

# Remove a specific skill
npx @tech-leads-club/agent-skills remove -s spec-driven-dev

# Remove from global installation
npx @tech-leads-club/agent-skills remove -g -s spec-driven-dev

# Show help
npx @tech-leads-club/agent-skills --help
npx @tech-leads-club/agent-skills install --help
npx @tech-leads-club/agent-skills remove --help

📦 Available Skills

Skills are organized by category for easier navigation.

🔧 Development

| Skill | Description | | ------------------- | ------------------------------------------------------------------------------------------------------ | | spec-driven-dev | Specification-driven development workflow with 4 phases: specify → design → tasks → implement+validate |

🛠 Skill & Agent Creation

| Skill | Description | | --------------------------- | ----------------------------------------------------------- | | skill-creator | Meta-skill for creating new skills following best practices | | subagent-creator | Create specialized subagents for complex tasks | | cursor-skill-creator | Cursor-specific skill creation | | cursor-subagent-creator | Cursor-specific subagent creation |

🛠 For Contributors

Prerequisites

• Node.js ≥ 22
• npm (comes with Node.js)

Setup

# Clone the repository
git clone https://github.com/tech-leads-club/agent-skills.git
cd agent-skills

# Install dependencies
npm ci

# Build all packages
npm run build

Development Commands

| Command | Description | | --------------------- | ---------------------------------- | | npm run start:dev | Run CLI locally (interactive mode) | | npm run g <name> | Generate a new skill | | npm run build | Build all packages | | npm run test | Run all tests | | npm run lint | Lint codebase | | npm run lint:fix | Fix lint issues | | npm run format | Format code with Prettier | | npm run release:dry | Preview release (dry-run) |

Creating a New Skill

Use the NX generator:

# Basic usage (will prompt for category)
nx g @tech-leads-club/skill-plugin:skill my-awesome-skill

# With category specified
nx g @tech-leads-club/skill-plugin:skill my-awesome-skill --category=development

# With all options
nx g @tech-leads-club/skill-plugin:skill my-skill \
  --description="What my skill does" \
  --category=development

The generator will:

• Create skills/my-skill/SKILL.md with the correct template structure
• Assign the skill to the specified category (creating it if needed)
• If no category is specified, the skill will appear as "Uncategorized"

Skill Structure

skills/my-skill/
├── SKILL.md              # Required: main instructions
├── scripts/              # Optional: executable scripts
├── references/           # Optional: on-demand documentation
├── templates/            # Optional: file templates
└── assets/               # Optional: images, files

Skill Categories

Skills are organized into categories for better navigation in the CLI. Categories are defined in skills/categories.json.

Adding a Skill to a Category

Edit skills/categories.json and add your skill to the skills map:

{
  "categories": [
    { "id": "development", "name": "Development", "priority": 1 },
    { "id": "creation", "name": "Skill & Agent Creation", "priority": 2 }
  ],
  "skills": {
    "my-new-skill": "development"
  }
}

Creating a New Category

Add a new entry to the categories array:

{
  "id": "my-category",
  "name": "My Category",
  "description": "Optional description",
  "priority": 3
}

• id: Unique identifier (kebab-case)
• name: Display name in the CLI
• description: Optional description
• priority: Display order (lower = first)

SKILL.md Format

---
name: my-skill
description: What this skill does. Use when user says "trigger phrase".
---

# My Skill

Brief description.

## Process

1. Step one
2. Step two
3. ...

Best Practices

• Keep SKILL.md under 500 lines — use references/ for detailed docs
• Write specific descriptions — include trigger phrases
• Assume the agent is smart — only add what it doesn't already know
• Prefer scripts over inline code — reduces context window usage

📁 Project Structure

agent-skills/
├── packages/
│   └── cli/                    # @tech-leads-club/agent-skills CLI package
├── tools/
│   └── skill-plugin/           # NX generator plugin
├── skills/                     # Skill definitions
│   ├── categories.json         # Skill category mappings
│   └── [skill-name]/           # Individual skill folders
├── .github/
│   └── workflows/
│       ├── ci.yml              # CI: lint, test, build
│       └── release.yml         # Release: version, publish
├── nx.json                     # NX configuration
└── package.json                # Root package.json

🔄 Release Process

This project uses NX Release with Conventional Commits for automated versioning:

| Commit Prefix | Version Bump | Example | | ------------- | ------------- | ---------------------------- | | feat: | Minor (0.X.0) | feat: add new skill | | fix: | Patch (0.0.X) | fix: correct symlink path | | feat!: | Major (X.0.0) | feat!: breaking API change | | docs: | No bump | docs: update README | | chore: | No bump | chore: update deps |

Releases are automated via GitHub Actions when merging to main.

🤝 Contributing

1. Fork the repository
2. Create a feature branch (git checkout -b feat/amazing-skill)
3. Commit with conventional commits (git commit -m "feat: add amazing skill")
4. Push to your fork (git push origin feat/amazing-skill)
5. Open a Pull Request

📄 License

MIT © Tech Leads Club