skill-standardization
Standardize and validate SKILL.md files to match the project specification. Use when creating new skills, converting existing skills to standard format, or validating skill file structure. Handles section heading conversion, frontmatter standardization, and missing section detection.
What this skill does
# Skill Standardization
## When to use this skill
- Creating new SKILL.md files following the standard template
- Converting existing skills with non-standard section headings
- Validating skill files against the project specification
- Batch processing multiple skill files for consistency
- Ensuring all skills have required sections (Examples, Best practices, References)
## Instructions
### Step 1: Run the conversion script
Execute the main conversion script to standardize all SKILL.md files:
```bash
cd /path/to/.agent-skills
python3 scripts/convert_skills.py
```
This script will:
- Convert Korean section headings to English
- Standardize frontmatter (add missing tags, platforms)
- Add missing required sections with templates
### Step 2: Remove duplicate sections
If files have duplicate sections after conversion:
```bash
python3 scripts/remove_duplicates.py
```
### Step 3: Final cleanup
For any remaining non-standard headings:
```bash
python3 scripts/final_cleanup.py
```
## Available Scripts
| Script | Purpose |
|--------|---------|
| `convert_skills.py` | Main conversion script - handles section headings, frontmatter, missing sections |
| `remove_duplicates.py` | Removes duplicate Examples, Best practices, References sections |
| `final_cleanup.py` | Direct string replacement for remaining Korean headings |
## Section Heading Conversions
| Legacy heading | Standard heading |
|--------|---------|
| `## Purpose (legacy)` | `## Purpose` |
| `## When to Use (legacy)` | `## When to use this skill` |
| `## Procedure (legacy)` | `## Instructions` |
| `## Examples (legacy)` | `## Examples` |
| `## Best Practices (legacy)` | `## Best practices` |
| `## References (legacy)` | `## References` |
| `## Output Format (legacy)` | `## Output format` |
| `## Constraints (legacy)` | `## Constraints` |
| `## Metadata (legacy)` | `## Metadata` |
| `### Step N (legacy):` | `### Step N:` |
## Standard SKILL.md Structure
```markdown
---
name: skill-name
description: Clear description (max 1024 chars)
tags: [tag1, tag2]
platforms: [Claude, ChatGPT, Gemini]
---
# Skill Title
## When to use this skill
- Scenario 1
- Scenario 2
## Instructions
### Step 1: [Action]
Content...
### Step 2: [Action]
Content...
## Examples
### Example 1: [Scenario]
Content...
## Best practices
1. Practice 1
2. Practice 2
## References
- [Link](url)
```
## Examples
### Example 1: Convert a single file manually
```python
from pathlib import Path
import re
filepath = Path('backend/new-skill/SKILL.md')
content = filepath.read_text()
# Normalize legacy headings to standard
content = content.replace('## Best Practices', '## Best practices')
content = content.replace('## Reference', '## References')
content = re.sub(r'### Step (\d+):', r'### Step \1:', content)
filepath.write_text(content)
```
### Example 2: Validate a skill file
```bash
# Check for required sections
grep -E "^## (When to use|Instructions|Examples|Best practices|References)" SKILL.md
```
## Best practices
1. **Run all three scripts in sequence** for complete standardization
2. **Review changes** before committing to ensure content wasn't lost
3. **Keep section content** - only headings are converted, not content
4. **Test with one file first** when making script modifications
## References
- [README.md](../../README.md) - Repository overview and SKILL.md conventions
- [.agent-skills/README.md](../README.md) - Skill repository structure and examples
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".