management-consulting-plugin
CLAUDE.md62 starsChanged 11 days agoMITView on GitHub
Use the skill matching the user's consulting task and read its linked references only when relevant. Preserve the requested scope, format, client template, and existing approvals. The skills are portable; no particular model or external connector is required. Lead with the decision or finding and explain the evidence, trade-offs, and next action. Match depth to what affects the decision. Use plain prose without invented precision, fixed sentence counts, or generic filler. Keep facts, forecasts, judgment, and illustrative examples distinct. Trace…
In this repository16 other files it gives its agents.
- change-managementSkill
- client-deliverablesSkill
- due-diligenceSkill
- engagement-pricingSkill
- engagement-setupSkill
- financial-modelingSkill
- implementation-planningSkill
- org-designSkill
- process-excellenceSkill
- project-closeoutSkill
- project-governanceSkill
- proposal-developmentSkill
- strategic-analysisSkill
- thought-leadershipSkill
- workshop-facilitationSkill
- writing-styleSkill
The file
We split this CLAUDE.md 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 3
Use the skill matching the user's consulting task and read its linked references only when relevant.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.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
Management Consulting Plugin
Use the skill matching the user's consulting task and read its linked references only when relevant. Preserve the requested scope, format, client template, and existing approvals. The skills are portable; no particular model or external connector is required.
Lead with the decision or finding and explain the evidence, trade-offs, and next action. Match depth to what affects the decision. Use plain prose without invented precision, fixed sentence counts, or generic filler.
Keep facts, forecasts, judgment, and illustrative examples distinct. Trace consequential claims to supplied evidence, verified sources, or reproducible calculations. Conditional language does not make an unsupported empirical claim acceptable. Preserve conflicting evidence and state what would change the recommendation. Never invent client experience, benchmarks, owners, or commitments.
The writing-style skill contains the maintained guidance for tone and evidence handling. Draft useful work with labeled gaps when possible; external approval and publication follow the user's actual authority and instructions.
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.