develop-plugin
Skill136 starsChanged 19 days agoMITView on GitHub
Maintain AutoformBot's code, skills, tests, examples, and installation.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-reviewSkill
- debrief-orchestratorSkill
- formalizeSkill
- human-reviewSkill
- roadmapSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Treat Autoform as an example-based plugin for an independent formalization repository.
- Distinctive: line 16
Keep Cabannes-specific facts in examples.
≈ “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
Develop Autoform
Treat Autoform as an example-based plugin for an independent formalization
repository. State a consumer scenario and invariant. Treat user nudges as
product evidence. Fix the product first: the command's output, error message, or
default. Add a skill sentence only when behavior cannot carry the fix, in the
one skill that owns the step. Tests check behavior, links, and that documented
commands parse; never add a test that pins a skill's wording, except the short
list of safety rules in tests/test_skill_examples.py.
Keep Cabannes-specific facts in examples; keep plugin and formalization roots distinct. Agents can infer routine details; keep shared agent entrypoints concise and link on-demand references.
For local views/source evidence/mirrors/pins/releases/explorers, read repository contracts.
Run:
make lint
make test
make check-exampleValidate skills and manifests with skill-creator and plugin-creator. Test cachebuster/reinstall discovery only in a new thread.
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.

