product-to-agent-skilllisted

Write the agent-skill for the product you just built, so a coding agent can drive it. Reads the product's own API surface — Next.js route handlers, an OpenAPI spec, or an eve agent's tools — and produces a distributable `skills/<slug>/SKILL.md` in the product repo: auth (device flow before raw keys), the loop an agent should perform, the endpoint reference, error shapes, and a common-mistakes table grounded in what actually breaks. Plus the README row and the `npx skills add owner/repo` line for the product's users. Use when the product exposes an API that is not only for its own frontend, when the user says "make my product usable from Claude Code / Cursor", "ship an agent skill for this", "how do agents use my API", or when dev-flow raises it near feature_complete. Refuses when the product has no callable surface. Not for: skills that operate ON this repo (those are dev-flow's own), and not a docs generator �� the output is a runbook, not a reference dump.
lukedj78/dev-flow · ★ 6 · AI & Automation · score 78

Install: claude install-skill lukedj78/dev-flow

# Product → agent-skill Every product this repo builds may end up with an API. An API that only its own frontend calls is an implementation detail. An API that **somebody else's coding agent could drive** is a distribution channel, and it needs one artefact to be usable: a skill file that tells that agent how the product works. This skill writes that file, in the product's repo, for the product's users. ⚠️ **The output belongs to the product, never to dev-flow.** It lands in `<product-repo>/skills/`, it ships and versions with that product, and its audience is whoever installs the product's own repo. It is not added to this repo's 45, not copied into `~/.claude/skills/`, and not listed in `install.sh`. dev-flow builds it and then has nothing more to do with it — the same way it builds an `app/` it does not own. The reference implementation of the shape is [`sleekdotdesign/agent-skills`](https://github.com/sleekdotdesign/agent-skills) (MIT, read 2026-09-03): a design service published one 563-line SKILL.md and became drivable from Claude Code, Cursor and Codex without shipping an SDK for any of them. `references/anatomy.md` is what that file taught us, section by section. ## When this skill applies - The product has a **callable surface that is not only its own frontend**: route handlers under `app/api/`, an OpenAPI spec, a public eve agent, an MCP server. - The user says "make my product usable from Claude Code", "ship an agent skill for this", "how would an agent