recipe-maintenance
Skill226 starsChanged 16 days agoMITView on GitHub
Maintain MagicNet's primary Markdown recipes, dependency contracts, and honest acceptance records before regenerating implementation.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- android-cliSkill
- kamfwSkill
- magicnet-device-debuggingSkill
- perfetto-sqlSkill
- perfetto-trace-analysisSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read AGENTS.md and recipes/magicnet/BUILD_PROMPT.md.
- Distinctive: line 7
Keep generated implementation under ignored generated/<implementation-name>/.
- Very specific: line 8
Run recipkg check recipes/magicnet, pack outside recipes, check the archive and render its complete build prompt.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Read AGENTS.md and recipes/magicnet/BUILD_PROMPT.md. Update the owning component recipe and its acceptance cases when changing behavior, interfaces, dependencies, storage, or limits. Preserve source attribution and unknowns.
Keep generated implementation under ignored generated/<implementation-name>/; never copy implementation, binaries, secrets, hooks, or filesystem links into recipe payloads.
Run recipkg check recipes/magicnet, pack outside recipes, check the archive and render its complete build prompt. Inspect every archive member as UTF-8 Markdown, including recursive dependencies.
Record actual results in recipes/magicnet/VERIFICATION.md. Packaging is not implementation acceptance. Use local verification for normal changes; publish only within existing authorization, preserving the project name MagicNet and original remote.
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.

