measure-success
Skill2 starsChanged 2 months agoMITView on GitHub
Define practical success measures for an initiative, including baselines, metric definitions, meaningful targets, and safeguards against misleading improvement. Use when deciding how to judge success, not reporting existing KPI results.
In this repository18 other files it gives its agents.
- check-my-analysisSkill
- clean-handoffSkill
- clean-upSkill
- decision-coachSkill
- design-system-fitSkill
- feedback-to-findingsSkill
- form-flow-fixerSkill
- gameplanSkill
- knowledge-interviewSkill
- meeting-briefSkill
- motion-resilienceSkill
- practice-coachSkill
- proposal-reviewerSkill
- reconcile-reportsSkill
- research-briefSkill
- simplify-reportSkill
- ui-state-completenessSkill
- ui-stress-testSkill
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 12
Use the initiative, intended beneficiaries, decision, time horizon, and constraints already supplied.
- Distinctive: line 22
Check whether proposed measures are timely, feasible, interpretable, and vulnerable to gaming.
≈ “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
Measure success
Build a measurement plan that can change a real decision. Distinguish the desired outcome from the activity intended to produce it.
Frame the outcome
Use the initiative, intended beneficiaries, decision, time horizon, and constraints already supplied. Ask only for consequential missing information. Clarify what improvement would mean to the people affected, what the team can influence, and which harms would make a nominal improvement unacceptable.
Inspect existing definitions and baseline evidence when available. Do not require a connected analytics system to draft a useful plan from supplied context. Distinguish an available measure from one that would require new collection.
Choose usable measures
Select the smallest useful set of outcome measures, earlier signals, and guardrails. Include a metric only if its movement informs a decision or reveals a consequential tradeoff. Explain where a proxy could improve without the intended outcome improving.
Specify enough detail for repeatable measurement: eligible population, unit of analysis, numerator and denominator or calculation, time window, exclusions, source or collection method, and review cadence where relevant. Distinguish zero from missing data. If ownership is unknown, mark it unassigned rather than inventing a responsible person.
Check whether proposed measures are timely, feasible, interpretable, and vulnerable to gaming. Consider mix shifts, selective exclusions, delayed harms, and burden of collection. Pair a speed or volume measure with relevant quality or outcome evidence when the tradeoff matters.
Set justified targets
Separate metric selection from target setting. Use baseline performance, capacity, comparable evidence, or a clearly explained operational requirement to justify thresholds. Preserve targets supplied by the user, labeling aspirations separately from evidence-backed forecasts.
When the baseline is unknown, propose a baseline collection phase and a rule for setting a target afterward. Do not invent a percentage improvement to complete a table. Provisional ranges should identify their assumptions. Verify current external benchmarks when used and explain whether they are comparable.
Define how results will inform action, including what happens if the outcome improves but a guardrail deteriorates. Proposed decision thresholds remain proposals until adopted. Distinguish monitoring progress from proving that the initiative caused it; suggest a credible comparison or evaluation design if attribution is necessary.
Deliver the plan
Return a compact plan linking the outcome, operational definitions, baseline status, justified targets, review timing, and decision rules. Include unresolved measurement gaps and the smallest useful next step. Honor the requested format. Planning collection, dashboards, or recurring reviews does not itself authorize implementation, account access, or scheduling.
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.

