indicator-design
Skill0 starsChanged 49 days agoCC-BY-4.0View on GitHub
Design, select, define and quality-assure monitoring, evaluation and learning (MEL) indicators for development, humanitarian and public-sector programmes. Use this skill whenever the user is building or reviewing a results framework, logframe, theory of change, M&E plan, performance measurement framework, results chain, indicator matrix, indicator reference sheet / PIRS, KPI set, baseline or target values, disaggregation plan, or data collection plan — and also when they simply say things like "how do we measure this outcome", "what indicators should we use for this project", "our indicators aren't working", "help me write a logframe", "we need SMART indicators", or "review our M&E framework", even if the word "indicator" is never used. Applies to donor-funded work (World Bank, EU/DG INTPA, UN agencies, FCDO, Department of State, GIZ, AfDB, IsDB, philanthropies), government sector plans, and NGO proposals alike.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- shakeebshaan/claude-code-quant-skillstheir own version, first seen Apr 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- shakeebshaan/claude-code-quant-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 10 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — 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.