Agent Skills

A collection of production-ready skills for Claude Code and other AI coding assistants.

Available Skills

Skill	Description
blog-editor	Brutal content editor for blog posts and articles
contrarian-thought-partner	Adversarial critique for stress-testing ideas
docs-auditor	Audit documentation against codebase for accuracy
folk-crm	Folk CRM integration with ID handling and tool guidance
pdfco	PDF.co integration for HTML-to-PDF and document manipulation
qa-tester	Comprehensive QA engineer for test design and edge cases
seo-optimizer	SEO analysis and optimization for content
skill-author	Create new skills from natural language descriptions
strategic-thought-partner	Collaborative strategic thinking for decision-makers
whitepaper-editor	Technical white paper review with source verification
zoom	Zoom meeting creation with proper calendar integration

Installation

Using mpak CLI

# Install a skill
mpak skill install @nimblebraininc/blog-editor

# List available skills
mpak skill search

Manual Installation

Copy the skill folder to your project's .claude/skills/ directory:

cp -r blog-editor /path/to/project/.claude/skills/

Usage

Once installed, skills are automatically available in Claude Code. Invoke them by:

1. Using the Skill tool directly
2. Triggering with natural language (e.g., "review this draft" triggers blog-editor)

Creating Your Own Skills

Use the skill-author skill to create new skills:

Build me a skill that reviews PRs for security issues

Or follow the Agent Skills Specification.

Versioning

Each skill versions independently using release-please with conventional commits.

See CLAUDE.md for detailed workflow documentation.

Contributing

1. Fork this repository
2. Create a new skill in its own directory
3. Include a SKILL.md with proper frontmatter
4. Submit a pull request

Skill Requirements

Each skill must have:

• A directory named after the skill (kebab-case)
• A SKILL.md file with YAML frontmatter containing:
  • name (must match directory name)
  • description (what it does and when to use it)
  • metadata.version (semver)
• A version.txt file with the current version

Example structure:

my-skill/
├── SKILL.md
└── version.txt

Example SKILL.md:

---
name: my-skill
description: Does X when Y. Use when Z. Triggers include "phrase 1", "phrase 2".
metadata:
  version: 1.0.0
  category: development
  tags:
    - tag1
    - tag2
---

# My Skill

[Skill content...]

License

MIT