Welcome to the Claude Content Skills documentation.
- Installation Guide - Step-by-step installation
- Configuration - Setting up credentials and options
- Troubleshooting - Common issues and solutions
- SEO WordPress Manager - Batch Yoast SEO updates
- Astro CTA Injector - Intelligent CTA placement
- Link Analyzer - Comprehensive link analysis
- Why These Skills - The problems we're solving
- ADD Framework Integration - How cognitive alignment shaped development
Claude Code skills are a mechanism for extending Claude's capabilities in specific domains. Unlike slash commands (which require explicit user invocation), skills are model-invoked - Claude automatically detects when to use them based on conversation context.
Each skill follows this structure:
skill-name/
├── SKILL.md # Required: Skill definition with YAML frontmatter
├── reference.md # Optional: Detailed reference documentation
├── config.example.json # Optional: Configuration template
└── scripts/ # Optional: Supporting scripts
The SKILL.md file is the entry point:
---
name: skill-name
description: Description that helps Claude know when to use this skill.
Include trigger phrases and use cases.
---
# Skill Documentation
Detailed instructions for Claude when this skill is active...- User makes a request
- Claude scans available skills' descriptions
- If a skill matches the request context, Claude activates it
- Claude follows the skill's documentation to respond appropriately
- Claude uses the skill's scripts and tools as needed
These skills were developed with the Assess-Decide-Do (ADD) Framework, which influenced several design decisions:
Each skill includes preview/dry-run modes because the ADD framework emphasizes thorough assessment before action. You always see what will happen before it happens.
Skills present explicit choices (batch size, thresholds, placement strategies) rather than making assumptions. This respects the user's decision-making authority.
Once in "Do" mode, skills include progress tracking, backups, and resume capability. Completing tasks matters, and interruptions shouldn't mean starting over.
Documentation improvements are always welcome. When contributing:
- Match the existing tone (direct, practical, no fluff)
- Include real examples where possible
- Document edge cases you discover
- Keep the ADD framework principles in mind
Part of Claude Content Skills