Skills for DevRels and Engineers

Claude Code skills for developer advocates and the engineers who write about what they build. They help you ship content that's specific, accurate, and worth watching.

Agents write generic content. They open with "In this video," pad scripts with restating, announce launches with "excited to introduce," and state a default as if it were a limit. Each of these is small. Together they make your content sound like everyone else's.

Each skill here lists those mistakes and tells the agent how to fix them.

Browse the gallery: devrel-skills.vercel.app

Install

One skill, no clone:

curl -fsSL https://raw.githubusercontent.com/SamRome1/devrel-skills/main/install.sh | bash -s -- <skill>

Or clone, so a git pull updates every skill:

git clone https://github.com/SamRome1/devrel-skills.git
cd devrel-skills
./install.sh --list      # see what's available
./install.sh <skill>     # e.g. ./install.sh hook-engineering

Skills install into ~/.claude/skills/. Add --project to install into the current project's ./.claude/skills instead. Restart Claude Code afterward.

Why use it

• Hooks that earn attention. Specific, front-loaded, and backed by the script's real payoff, not clickbait.
• Scripts without filler. Every line gets a keep, sharpen, or cut verdict.
• Claims that hold up. Each technical statement is checked against a real run or the official docs before you publish.
• Demos that don't fail on camera. A shot list, a clean-state checklist, and a stress test before anyone else finds the bug.
• Launches that lead with the developer. What they can do now, with proof attached.

They work best chained.

• Write: content-from-changelog → hook-engineering → review-script
• Verify: fact-check-claims → break-demo
• Ship: demo-recording / tutorial-outline → launch-post

Reference

• break-demo: Stress-tests a demo, sample app, or tutorial from a clean state against bad inputs, version drift, environment differences, and out-of-order steps, then reports each break by severity with a fix.
• content-from-changelog: Turns release notes into a ranked list of content ideas, scored on whether a developer who has never used your product would stop for them, each with an angle and format.
• demo-recording: Plans a screen-recorded demo as a shot list with exact commands, off-camera setup, wait handling, and a one-minute reset.
• fact-check-claims: Extracts every checkable claim from a script, post, or demo, verifies each against a real run, official docs, or source, and returns a pass/fail table with evidence and fixes.
• hook-engineering: Diagnoses the opening hook of a video, short, or post and rewrites it from proven formulas, each backed by the script's real payoff.
• launch-post: Turns a shipped feature or changelog entry into an X post or thread that leads with what the developer can now do, with proof attached.
• review-script: Audits a short-form or long-form script line by line, marks each line keep, sharpen, or cut, and reports the word count and runtime before and after.
• tutorial-outline: Structures a docs page, blog tutorial, or video walkthrough around the shortest path to a working result, with prerequisites, checkpoints, and likely failures at each step.

Share your own skill

It's a normal git contribution — copy template/skill-template, edit SKILL.md, open a PR. See CONTRIBUTING.md.

Repo layout

skills/<name>/SKILL.md   ← a skill (plus any supporting files)
template/skill-template  ← starting point for a new skill
install.sh               ← installer (clone mode + curl mode)
scripts/gen-index.mjs    ← regenerates the table above from frontmatter
.github/workflows/       ← runs the index generator on push
src/, next.config.ts …   ← the optional Next.js gallery (reads skills/) — see below

The web gallery

Live at devrel-skills.vercel.app — a searchable gallery with a web form that opens a prefilled PR to add a skill. It reads this repo's skills/ folder directly, so the git repo stays the single source of truth (no database to keep in sync), and it redeploys automatically on every push to main. The site is optional — everything works from the repo and the installer alone. To run or tweak it locally, see docs/WEBAPP.md.