product-skill
AGENTS.md1 starsChanged 4 months agoMITView on GitHub
This repository is the released product skill: the Discover/Strategy stage of the Digital Product Skills family. The runtime skill lives under skills/product/; repository and plugin names use the -skill suffix. Version metadata lives in .codex-plugin/plugin.json, CHANGELOG.md, and tags — never in SKILL.md. Product discovery, strategy, positioning, business-model & pricing, market sizing & competition, PRDs & acceptance criteria, prioritization & roadmaps, success metrics & metric-trees, and the risk/assumption register — across websites, web/SaaS apps, mobile, agentic/AI products, and internal tools. It…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms.txtllms.txt
- mediabunnySkill
- remotion-best-practicesSkill
- remotion-captionsSkill
- remotion-createSkill
- remotion-docsSkill
- remotion-interactivitySkill
- remotion-markupSkill
- remotion-renderSkill
- remotion-saasSkill
- remotion-upgradeSkill
- productSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run scripts/check-sync before any release.
- Distinctive: line 24
Every method must be grounded in its named framework with a source.
- Very specific: line 26
Keep the boundary discipline: reference sibling territory by backtick name and recommend it.
- Very specific: line 28
Keep the eval contract current: evals/{activation,traversal,output,compression-ablation} must reflect the router.
- Very specific: line 30
Treat README as the primary storefront.
- Distinctive: line 37
Do not mark a change complete merely because lint passes.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent guide — product-skill
This repository is the released product skill: the Discover/Strategy stage of the Digital Product
Skills family. The runtime skill lives under skills/product/; repository and plugin names use the
-skill suffix. Version metadata lives in .codex-plugin/plugin.json, CHANGELOG.md, and tags —
never in SKILL.md.
What this skill owns
Product discovery, strategy, positioning, business-model & pricing, market sizing & competition,
PRDs & acceptance criteria, prioritization & roadmaps, success metrics & metric-trees, and the
risk/assumption register — across websites, web/SaaS apps, mobile, agentic/AI products, and internal
tools. It owns the decision about what to build, not its execution. It recommends siblings
(design, frontend, architecture, marketing, growth, sales, success, data) for work
it does not own and never silently invokes them.
Maintainer rules
- Run
scripts/check-syncbefore any release; it validates packaging, routes, references, metadata, and eval fixtures. Runscripts/lint-skillandscripts/count-skill-tokenstoo. SKILL.mdis the direct router: a faceted table of one primary job × at most one product-type overlay. References are flat underreferences/, directly linked, self-describing, and loaded only when their observable condition applies. No required second-hop navigation.- Every method must be grounded in its named framework with a source. Fix a wrong formula or misattribution as a correctness bug, not a nit (the v0.1 review caught two).
- Keep the boundary discipline: reference sibling territory by backtick name and recommend it; never absorb design/frontend/marketing/growth work.
- Keep the eval contract current:
evals/{activation,traversal,output,compression-ablation}must reflect the router. Add near-miss activation cases when a new sibling overlap appears. - Treat README as the primary storefront. The
site/andremotion/profiles follow thesite/README.mddesign brief — designed for this skill's faceted-router model inside the shared family chrome and the emerald accent, never a filled-in skeleton. - Release through matching plugin version + changelog entry +
v<version>tag + GitHub Release, and keep the GitHub About area configured (family-style description, canonical site alias as homepage, base + domain topics).
Do not mark a change complete merely because lint passes. Activation, traversal, and output evaluations must show the skill still changes agent behavior usefully.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.