Skip to content

borghei/Claude-Skills / engineering/write-a-skill

write-a-skill

Verified

Author, lint, and publish skill packages that satisfy the library authoring standard. Use when creating a new skill, reviewing a skill PR, or fixing one that never activates.

assets/sample_skill_spec.json

View on GitHub
{
  "name": "release-notes-writer",
  "title": "Release Notes Writer",
  "description": "Turn merged PRs and commit history into audience-segmented release notes. Use when cutting a release, writing changelog entries, or preparing a customer-facing what's-new post.",
  "category": "engineering",
  "domain": "developer-experience",
  "version": "1.0.0",
  "author": "borghei",
  "updated": "2026-07-21",
  "generative": true,
  "tags": ["release", "changelog", "communication", "versioning", "developer-experience"],
  "use_when": [
    "Cutting a versioned release and needing notes in under an hour",
    "Translating engineering commits into customer-readable value statements",
    "Splitting one release into developer, admin, and end-user notes",
    "Auditing a draft changelog for missing breaking-change callouts",
    "Backfilling notes for releases that shipped undocumented"
  ],
  "inputs": [
    "Version range or tag boundary (e.g. v2.3.0..v2.4.0)",
    "Audience segments the notes must serve",
    "Product vocabulary — the names customers actually use",
    "Breaking-change and deprecation policy"
  ],
  "scripts": ["commit_classifier.py", "notes_generator.py", "breaking_change_auditor.py"]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall