Evaluation Questions
Prioritize answerable questions tied to the decisions an evaluation must support.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Evaluation QuestionsPractical M&E skills, document reviews and workflows to use in Claude.
Try evaluation questions, indicators or logframe review.
Choose a task to see what to provide, what you can expect and how to use it. 12 task skills, 12 document reviews and 3 workflow packs.
Use these resources in your own Claude account. Check drafts and reviews against your source documents before sharing them. Checking Evidence and Limits
Prioritize answerable questions tied to the decisions an evaluation must support.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Evaluation QuestionsMatch evaluation questions to feasible evidence, methods and limitations.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Question and Method AlignmentDraft a source-linked TOR with feasible scope and unresolved decisions visible.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Evaluation TOR DraftDraft a sampling plan with visible calculations, or check the sizing and selection of an existing one.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Sampling Plan DraftPlan baseline measurement for every indicator, or check a baseline against the framework, without inventing starting values.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Baseline PlanningDefine each indicator so people can collect and interpret it consistently.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Indicator Reference SheetsCalculate collection workload and compare practical simplification options.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Measurement Feasibility and BurdenBuild a practical plan and check that definitions, responsibilities and use agree.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for M&E Plan Draft and CoherenceCompare a theory of change, logframe and indicators for gaps and conflicts, keeping source versions visible.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Results Chain AlignmentPlan a risk-based data quality assessment with proposed checks, owners and timing.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Data Quality Assessment PlanCheck results logic, indicators, assumptions and means of verification.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Logframe ReviewExamine the results chain, causal assumptions and evidence behind it.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Theory of Change ReviewAssess definitions, SMART and CREAM qualities, disaggregation and measurability.
Document Review
Checked in Claude Code
Inputs, Examples and Files for Indicator Quality ReviewIdentify gaps and inconsistencies in a measurement and learning plan.
Document Review
Checked in Claude Code
Inputs, Examples and Files for M&E Plan ReviewReview the approach, evaluation arrangements, resources and staffing in a proposal.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Proposal M&E ReviewReview commissioning scope, methodological feasibility, ethics and deliverables.
Document Review
Checked in Claude Code
Inputs, Examples and Files for Evaluation TOR ReviewCheck questionnaire quality, structure and data collection feasibility.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Survey ReviewReview the sampling approach, assumptions, frame and calculations.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Sampling Plan ReviewReview baseline evidence, indicator coverage and the basis for later comparison.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Baseline Report ReviewCheck reported numbers, explanations and evidence-linked conclusions.
Document Review
Checked in Claude Code
Inputs, Examples and Files for Progress Report ReviewReview data quality evidence, verification and proposed improvement actions.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Data Quality ReviewReview design, evidence, findings, conclusions and recommendations.
Document Review
Earlier Release; Not in Latest Claude Code Checks
Inputs, Examples and Files for Evaluation Report ReviewReconcile reported results and identify which comparisons the evidence supports.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Progress Evidence and ComparisonsTurn supported findings into a traceable proposed management response.
Task Skill
Checked in Claude Code
Inputs, Examples and Files for Findings to ActionsWork through related tasks in sequence, using the same source documents and checking the result at each step.
Move from evaluation decisions to questions, methods and a revised TOR.
Workflow Pack
Checked in Claude Code
Inputs, Examples and Files for Evaluation PlanningMove from indicator review to reference sheets and a feasible M&E plan.
Workflow Pack
Checked in Claude Code
Inputs, Examples and Files for Feasible MeasurementMove from checked results to a revised report and proposed actions.
Workflow Pack
Checked in Claude Code
Inputs, Examples and Files for Reporting to ActionA hand-written fictional illustration of Logframe Review. This is not an observed test result or a complete review.
Fictional excerpt for explanation only. This is not an observed test result or a complete review.
A fictional framework lists training sessions as its outcome, with attendance as the only indicator. No adoption measure is supplied.
Fictional excerpt for explanation only. This is not an observed test result or a complete review.
The supplied outcome and indicator describe delivery, not a demonstrated change in practice. Ask the program team to clarify the intended outcome and its evidence; do not invent an adoption target.
Claude Code is the route checked across the recorded task cases. Browser upload was checked for one skill on a paid plan. Check Claude’s documentation for current account requirements and setup steps.
Add the marketplace, then install the review and workspace plugins using the recorded setup commands:
/plugin marketplace add mestudiohq/me-review
/plugin install me-review@me-review
/plugin install me-workspace@me-reviewIf the install summary asks you to reload plugins, follow that instruction. Then type /me-workspace: or /me-review: to see the skills. Each task page gives its command and required inputs.
Open a task page and check its individual skill files. When a verified skill ZIP is available, that page provides the download.
The recorded browser check covered Evaluation Questions on a paid plan. It does not establish that every skill or account type behaves the same way.
Check the provider’s current instructions before choosing an account or uploading files. Follow your organization’s data rules.
Markdown is the checked output format. Word, PDF and spreadsheet output are not promised. Each method has its own review rules; an AI review is not approval.
Install the plugins, choose a job, start it, check the Markdown file you get back, and pause or resume with a handover.
One fictional program taken through evaluation questions, a feasible measurement plan and a report with proposed actions.
How to credit M&E Studio when you share or adapt these guides, and how the plugin license differs.
Checks ran in Claude Code on fictional cases, including incomplete and unsuitable inputs, the three workflows, and pausing and resuming. A second model checked the outputs against expected findings. Earlier failures were fixed and the affected cases repeated.
Browser upload passed for Evaluation Questions on a paid plan. Free accounts, copy and paste, and practitioner feedback were not checked. Of the 12 document reviews, 4 were included in the latest recorded checks; the others come from earlier releases.
The examples are fictional and written by hand. They are not real client work or observed test output. Review every output against your supplied evidence before use.
Source revision 18dd509 · Checked 2026-10-26