<h1 align="center">Agent Skills</h1>

<p align="center"> <strong>Production-grade capability skills for AI agents.</strong><br/> DNS migration, AWS migration, deep research, and viral image generation — battle-tested in production, portable across runtimes. </p>

<p align="center"> <a href="https://github.com/ravidsrk/agent-skills/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="MIT License"></a> <a href="https://agentskills.io/specification"><img src="https://img.shields.io/badge/spec-agentskills.io-orange.svg" alt="agentskills.io spec"></a> <a href="https://github.com/ravidsrk/agent-skills/stargazers"><img src="https://img.shields.io/github/stars/ravidsrk/agent-skills.svg?style=flat" alt="Stars"></a> <a href="https://github.com/ravidsrk/agent-skills/commits/main"><img src="https://img.shields.io/github/last-commit/ravidsrk/agent-skills.svg" alt="Last commit"></a> </p>

<p align="center"> <img src="assets/banner.jpg" alt="agent-skills — production-grade skills for AI agents" width="100%"> </p>

<p align="center">_{↑ Generated by Nano Banana Pro via OpenRouter. Prompt: <a href="scripts/banner/banner-prompt.txt">scripts/banner/banner-prompt.txt</a>}</p>

What's inside

5 skills, organized by what they do — not by SDLC phase. These are discrete capabilities an agent reaches for when the task fits, not lifecycle steps that fire in sequence.

🌐 Infrastructure

🔍 Research

🎨 Creative

Quick Start

<details> <summary><b>🟢 Claude Code (recommended)</b></summary>

git clone https://github.com/ravidsrk/agent-skills.git
cd agent-skills

mkdir -p ~/.claude/skills
for s in skills/*/; do
  name=$(basename "$s")
  ln -sf "$(pwd)/$s" "$HOME/.claude/skills/$name"
done

✅ All 5 skills are now available. Symlinks mean git pull keeps them up to date.

📖 Full guide: docs/claude-code-setup.md

</details>

<details> <summary><b>🟢 Mogra</b></summary>

cd /workspace
git clone https://github.com/ravidsrk/agent-skills.git

mkdir -p /workspace/.mogra/skills
for s in agent-skills/skills/*/; do
  name=$(basename "$s")
  ln -sf "$(pwd)/$s" "/workspace/.mogra/skills/$name"
done

Restart your Mogra session and the skills appear.

📖 Full guide: docs/mogra-setup.md

</details>

<details> <summary><b>🟡 Cursor</b></summary>

Per-project install — copy SKILL.md into .cursor/rules/:

mkdir -p .cursor/rules
cp /path/to/agent-skills/skills/cloudflare-dns/SKILL.md .cursor/rules/cloudflare-dns.md

📖 Full guide: docs/cursor-setup.md

</details>

<details> <summary><b>🟡 OpenCode</b></summary>

OpenCode reads AGENTS.md and the skills/ directory automatically:

git clone https://github.com/ravidsrk/agent-skills.git ~/.opencode/agent-skills
ln -s ~/.opencode/agent-skills/skills ~/.opencode/skills

📖 Full guide: docs/opencode-setup.md

</details>

<details> <summary><b>🟡 Codex / GitHub Copilot / any other agent</b></summary>

Skills are plain Markdown — they work with any agent that accepts system prompts or instruction files.

For Copilot, concatenate skills into .github/copilot-instructions.md:

cat skills/cloudflare-dns/SKILL.md \
    skills/namecheap-dns/SKILL.md \
    > .github/copilot-instructions.md

📖 Full guide: docs/generic-setup.md

</details>

Set the env vars

Each skill needs different secrets. Set them in your shell — never paste into prompts.

# cloudflare-dns
export CLOUDFLARE_API_KEY=cfat_...
export CLOUDFLARE_GLOBAL_API_KEY=...    # only for new-zone creation
export [email protected]

# namecheap-dns
export NAMECHEAP_API_KEY=...
export NAMECHEAP_API_USER=your-account

# fly-to-aws-migration
export AWS_PROFILE=migration
export FLY_API_TOKEN=...
# (also uses CLOUDFLARE_API_KEY for the DNS cutover phase)

# deep-research
export MONID_API_KEY=...

# terminal-poster
export OPENROUTER_API_KEY=...

🔴 All skills read env vars at runtime — they're never written to disk. Don't commit .env files.

Try it

Skills auto-activate based on the description field in their SKILL.md. Just ask the agent for what you want.

💬 "Move example.com's DNS to Cloudflare" → activates cloudflare-dns

>

💬 "Add a CNAME for docs.example.com pointing at my Fly app" → activates namecheap-dns

>

💬 "Migrate my Fly project to AWS" → activates fly-to-aws-migration

>

💬 "Do a deep dive on AI agent harness engineering" → activates deep-research

>

💬 "Generate a terminal-style poster for our deployment pipeline" → activates terminal-poster

Preview gallery

<a href="skills/terminal-poster/README.md#live-examples"> <img src="skills/terminal-poster/assets/examples/cluster-c2-walkbot.jpg" alt="Cluster C2 example — WalkBot" width="240"> <img src="skills/terminal-poster/assets/examples/cluster-a-stack.png" alt="Cluster A example — agent stack" width="240"> <img src="skills/terminal-poster/assets/examples/cluster-b-maturity.png" alt="Cluster B example — maturity ladder" width="240"> </a>

Three real first-generation outputs from terminal-poster. Audit scores + how to reproduce →

How skills work

Every skill follows the same anatomy:

┌─────────────────────────────────────────────────┐
│  SKILL.md                                       │
│                                                 │
│  ┌─ Frontmatter ─────────────────────────────┐  │
│  │ name: lowercase-hyphen-name               │  │
│  │ description: Does X. Use when…            │  │
│  │ compatibility: needs $ENV_VAR, bash, curl │  │
│  └───────────────────────────────────────────┘  │
│                                                 │
│  Overview         → What this skill does        │
│  When to use      → Triggering conditions       │
│  Setup            → Env vars + dependencies     │
│  Workflow         → Step-by-step process        │
│  Gotchas          → Known traps + fixes         │
└─────────────────────────────────────────────────┘

Key design choices:

• 🟢 Process, not prose. Skills are workflows agents follow, not reference docs they read.
• 🟢 Spec-compliant. Every skill validates against the agentskills.io format.
• 🟢 Battle-tested. These are the actual tools used in production, not theoretical patterns.
• 🟢 Progressive disclosure. SKILL.md is the entry point. References load on demand to keep token usage low.
• 🟢 Capability-first, not SDLC-first. Unlike skill packs that map to DEFINE → PLAN → BUILD → SHIP, these are discrete tools. Pick what you need.

📖 Full spec: docs/skill-anatomy.md

Project Structure

agent-skills/
├── README.md                     ← You are here
├── AGENTS.md                     ← Runtime-agnostic agent guidance
├── CLAUDE.md                     ← Claude Code session context
├── CONTRIBUTING.md               ← How to add a skill
├── LICENSE                       ← MIT
├── plugin.json                   ← Claude Code plugin manifest
├── assets/
│   └── banner.png                ← Hero image (generated by terminal-poster)
├── docs/                         ← Per-runtime setup + format spec
│   ├── getting-started.md
│   ├── skill-anatomy.md
│   ├── claude-code-setup.md
│   ├── mogra-setup.md
│   ├── cursor-setup.md
│   ├── opencode-setup.md
│   └── generic-setup.md
├── scripts/
│   └── validate-skills.py        ← Validates SKILL.md against the spec
└── skills/
    ├── cloudflare-dns/           ← 🌐 DNS migration + zone hardening
    ├── namecheap-dns/            ← 🌐 Namecheap XML API wrapper
    ├── fly-to-aws-migration/     ← 🌐 Fly → AWS playbook (7 phases)
    ├── deep-research/            ← 🔍 8-source parallel research
    └── terminal-poster/          ← 🎨 Retro-cyberpunk image posters

Each skill folder contains:

• SKILL.md — Agent-facing manifest (frontmatter + workflow)
• README.md — Human install + usage docs
• scripts/ — Runnable helpers (optional)
• references/ — Long-form docs loaded on demand (optional)
• templates/ — Boilerplate users copy into their projects (optional)
• assets/ — Example outputs, fixtures (optional)

Validation

Every push runs the validator. Run it locally before committing:

python3 scripts/validate-skills.py

Output:

✅ cloudflare-dns
✅ deep-research
✅ fly-to-aws-migration
✅ namecheap-dns
✅ terminal-poster

🟢 All 5 skills valid against agentskills.io spec.

The validator enforces the spec rules (frontmatter shape, name/directory matching, description length). Non-zero exit code if any skill fails — perfect for CI.

Why this repo exists

Most agent skill packs are shaped like a software lifecycle — DEFINE → PLAN → BUILD → SHIP. That's useful for skills that encode process discipline (writing specs, doing TDD, reviewing code).

This repo is shaped differently. These are capability skills — tools the agent reaches for when the task fits. You don't migrate to AWS as part of a SDLC phase; you migrate when you migrate. You don't run deep research because the workflow says so; you run it when you need evidence.

The two styles are complementary. For SDLC discipline, addyosmani/agent-skills is excellent. For real-world infrastructure and content tooling, this repo is what I reach for.

The shared bet: portable, public, spec-compliant skills make agents better.

Contributing

PRs welcome — new skills, fixes to existing ones, better docs. Quality bar:

• 🟢 Specific: actionable steps, not vague advice
• 🟢 Verifiable: clear exit criteria with evidence requirements
• 🟢 Battle-tested: based on real workflows you've shipped
• 🟢 Minimal: only what's needed to guide the agent

📖 See CONTRIBUTING.md and docs/skill-anatomy.md.

TL;DR: create skills/<your-skill>/SKILL.md + README.md, run python3 scripts/validate-skills.py, update the skills table, open a PR.

Credits

• 🏗️ Repo structure — inspired by addyosmani/agent-skills. The plugin manifest pattern, multi-runtime setup docs, expandable installs, and AGENTS.md conventions came from there.
• 🎨 `terminal-poster` — visual pattern reverse-engineered from public posts by @shannholmberg on X. The skill makes the look reproducible across topics; Shann designed the look itself.
• 🔍 `deep-research` — originally inspired by mvanhorn/last30days-skill. The 30-day default window came from that upstream; the 8-source fan-out and monid routing were rebuilt from scratch.

License

MIT © @ravidsrk

If you build something with these skills, I'd love to see it — tag me on X or open an issue.