module-creation
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Create automation modules for any process, workflow, or business function by decomposing it into a value chain and identifying friction at each stage. Use this skill whenever the user wants to brainstorm modules, break down a process into automatable steps, identify bottlenecks in a workflow, design a modular system, or figure out "what should I automate." Triggers on phrases like "create modules for," "what modules do we need," "how do I automate this," "brainstorm ideas for," "modularize this," "break this down," "decompose this process," "find the friction," or any request to systematically analyze a workflow and generate actionable components. Also use when the user describes a business process and wants to know where AI, automation, or tooling can be inserted. Also triggers automatically when a PRD skill completes — the PRD skill calls this skill to decompose each P-item into modules and tasks. Works for ANY domain — sales pipelines, content creation, infrastructure, client delivery, product development, personal workflows, or anything with sequential steps that produce an outcome. This is a universal module factory — give it any process, get back a complete set of buildable modules with a machine-readable task list.
In this repository8 other files it gives its agents.
- concept-engineeringSkill
- prdSkill
- process-extractionSkill
- revenue-architectureSkill
- revenue-generationSkill
- session-protocolSkill
- skill-enhancerSkill
- skill-improverSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 18 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈18
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.