workflow-reuse
Skill4 starsChanged 54 days agoMITView on GitHub
Choose existing project solutions and compatible audited components for the specific work.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- clean-implementationSkill
- code-reviewSkill
- core-analysisSkill
- core-debuggingSkill
- core-documentationSkill
- core-planningSkill
- core-securitySkill
- delivery-pipelineSkill
- domain-backendSkill
- domain-engineeringSkill
- domain-frontendSkill
- domain-mobileSkill
- flowcairn-controlSkill
- implementation-lessonSkill
- project-contextSkill
- testingSkill
- workflow-diagnosisSkill
- workflow-planningSkill
- workflow-test-qualitySkill
- workflow-verificationSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use the pinned project Skills and registered checks selected by the trusted runtime.
≈ “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
Reuse decision
- Inspect current manifests, versions, architecture and equivalent local components first. Preserve the project's stack and conventions. Do not replace a working component merely because another library is popular.
- Recommend a ready-made component only for a concrete missing capability. Verify its published documentation, full relevant instructions, dependencies, compatibility and license before import. Unresolved provenance or license remains unresolved.
- Distinguish a Skill (guidance), tool (authorized execution), library (code dependency) and verifier (evidence). Loading instructions does not install a CLI, authorize a command or prove the result.
- Use the pinned project Skills and registered checks selected by the trusted runtime. Suggest missing capabilities explicitly; do not create executable registrations, invoke forbidden MCP/tools or update floating instructions inside an authorized plan.
- Select only methods needed by the current phase, scope, framework/version, task and risk. For a routine change, avoid optional design exploration, scans or process artifacts while preserving the mandatory checks and rights.
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.