Progress Evidence and Comparisons
Reconcile reported results and identify which comparisons the evidence supports.
Free, with limits. These skills produce AI-assisted drafts and reviews. A person who knows the program should check every output against the source documents before it is shared. The examples are fictional and written by hand; they are not real client work or test output.
Claude Code is the checked route. One skill was also checked by browser upload on a paid plan. Anthropic's help page says Free plans can use uploaded skills too, once code execution is turned on; we did not test a Free account. No M&E Studio signup or API key is needed; your Claude account and its limits are separate.
What You Will Get
- Editable Markdown artifact
What to Provide
- Results framework and indicator definitions
- Report extracts and source records
- Comparison-period data, if available
Supply readable files or text. Missing evidence stays explicit; a draft or recommendation is not an approved commitment.
Start the Job
In Code use /me-workspace:progress-evidence with explicit files. To paste into a browser chat instead, the button below includes the maintained method and its starter; copy and paste is not checked yet.
Read the Starter
Start: Progress evidence and trends
Use this skill to check what a progress report supports, whether expected indicators are covered, and whether period comparisons are valid. With one period only, it checks evidence and coverage but will not call results a trend.
Intake: attach reports, or name a folder and ask the assistant to list candidate files first. It must state the intake mode and files used.
Starter:
Use progress-evidence on the attached files [or folder: path]. Check indicator coverage and evidence, and compare periods only when definitions, cohorts, denominators, and periods are comparable. Keep the exact headings Critical Issues, Important Issues, and Minor Improvements. Mark single-period analysis as not a trend assessment.
Examples are fictional and illustrate output shape only.
Try a Fictional Example
These examples are fictional and written by hand. The output shows the structure to expect. It is not a test result and must not be used as source evidence.
Fictional Input
Fictional input: progress extract
Reporting period: Jan-Mar 2026. Indicator: Farmers trained. Reported value: 42 people this quarter.
Evidence: Attendance sheet lists 42 names. No prior-period value, denominator, target, or completion definition supplied.
Narrative claim: “Training is increasing steadily and the program is on track.”
Framework: Not supplied.
Illustrative Output
Illustrative output: progress evidence check
Scope: Single period only. Intake: Uploaded fictional extract. Trend assessment: Not possible.
Evidence register
input.md#Reporting period: Jan-Mar 2026; 42 people reported.input.md#Evidence: Attendance sheet lists 42 names; definition and denominator not supplied.input.md#Narrative claim: “Increasing steadily” and “on track.” No target or comparison supplied.
Coverage and value reconciliation
| Indicator | Reported value | Source | Check | Limitation |
|---|---|---|---|---|
| Farmers trained | 42 people this quarter | Attendance sheet | Reported count matches the stated list size | Completion rule, duplicate check, target, and expected framework coverage are unknown |
Comparison eligibility
| Periods | Definition/population | Denominator | Basis | Eligible comparison |
|---|---|---|---|---|
| Jan-Mar 2026 only | Completion rule unknown | Not supplied | Period value | No trend can be assessed from one period |
Supported finding
The extract reports 42 names on an attendance sheet for Jan-Mar 2026. It does not support “increasing steadily” or “on track” because no comparable prior period or target was supplied. No causal claim is made.
Critical Issues
- None identified from the supplied extract.
Important Issues
- The narrative claims a trend and on-track status without a prior-period value or target.
- The expected indicator framework and completion rule are not supplied, so coverage cannot be confirmed.
Minor Improvements
- Document the reporting-period basis and whether the 42 names represent distinct people meeting a defined completion rule.
Decisions and data needed
Provide a prior comparable period, approved target, indicator definition, and framework to assess trend and coverage.
Read the Maintained Method
name: progress-evidence description: Check progress-report evidence, indicator coverage, and period-to-period comparisons. Use when reported results need a traceable evidence review with gaps and supported trends identified.
Progress evidence and trend checking
Purpose and trigger
Check whether progress claims are supported, indicators are covered, and comparisons use compatible periods and denominators. This does not verify source data independently or establish causal attribution.
Minimum inputs
- At least one progress report or results extract.
- Results framework or indicator definitions when available.
- A prior comparable period for trend analysis. Without it, perform single-period evidence checks only.
Accept explicitly uploaded files or a user-designated folder and file list. Upload mode uses attachments/text only. Folder mode inspects only the named folder and lists files used. Confirm ambiguous reports. State intake mode.
Starter prompt
Use progress-evidence on the attached files [or folder: path]. Check indicator coverage and evidence, and compare periods only when definitions, cohorts, denominators, and periods are comparable. Keep the exact headings Critical Issues, Important Issues, and Minor Improvements. Mark single-period analysis as not a trend assessment.
Procedure
- Confirm intake mode, report period, report type, framework, and whether the request is coverage, data checks, trends, or all three.
- Extract every indicator value with period, unit, numerator/denominator if available, population/cohort, cumulative or period basis, target, source, and disaggregation. Cite
filename#heading, page, table, or row. - Compare the expected indicator set with reported coverage. Distinguish “not reported in supplied material” from “not collected.”
- Recalculate percentages only when numerator, denominator, unit, and population are clear. Check whether disaggregated values reconcile to totals. State arithmetic and source IDs.
- Assess evidence quality and narrative alignment. Separate reported claims from verified arithmetic and interpretation. Flag missing source, unsupported explanation, and data-quality limitation.
- For trends, compare only matching definitions, units, populations/cohorts, denominators, reporting periods, and cumulative-versus-period basis. Show mismatches and decline comparison where necessary.
- Do not infer trend direction from a single period. Do not treat cumulative values as period values. Do not infer causal attribution from pre/post change alone.
- Return the report structure below and prioritize issues by severity. Preserve the exact three issue headings.
Output structure
- Scope and intake mode
- Sources and evidence register
- Coverage and value reconciliation table
- Comparison eligibility table: indicator; periods; definition/population/denominator match; cumulative or period basis; eligible comparison; reason
- Supported findings and limitations
- Decisions and source data needed
Include these exact headings in the produced artifact:
## Critical Issues
## Important Issues
## Minor Improvements
Rules
Keep denominators, periods, cohort/population, units, and cumulative or period basis visible in every reported comparison. Distinguish counts of people from service contacts or events. Do not make targets, thresholds, or status bands up. Preserve indicator definitions; flag silent changes. A report may support a mathematical check without supporting the narrative explanation. Use “not assessable from supplied files” where appropriate.
Reconciliation checks
- Match indicator labels and definitions across periods before comparing values. Similar names do not prove identical definitions.
- Keep reporting period and value basis visible. Do not subtract a cumulative total from a single-period count without a valid calculation path.
- For percentages, verify numerator and denominator definitions, population universe, unit, and observation window. Numeric denominator counts may differ across periods when population size or coverage changes; compare rates only when denominator meaning and population composition are sufficiently comparable, and disclose differences that limit interpretation.
- For disaggregation, check whether categories are exhaustive and mutually exclusive before summing. Report unclassified or missing categories separately.
- For counts, look for duplicate units or repeated service contacts when the source permits the check.
- Reconcile narrative claims to table values and sources. A success story illustrates an experience but does not establish prevalence.
- Compare achievements to explicit period targets only when the target covers the same period and definition.
- Treat target revisions as changes requiring documentation, not evidence that prior performance changed.
- A blank field is not zero. “Not reported” does not establish that data were not collected.
- Do not project trajectory without adequate comparable observations and a justified model. A simple arithmetic rate is descriptive, not a prediction.
- When comparing percentage changes, distinguish percentage-point change (subtract the two percentages) from relative percent change (change divided by the earlier value). State which calculation is shown; do not use “percent increase” ambiguously.
Use Critical Issues for a defect that invalidates a current material finding or its intended use, or presents a serious ethical risk. Important Issues affect usefulness or confidence but still allow a bounded output. Minor Improvements are editorial or detail refinements with limited effect on conclusions. An unsupported claim that does not appear in the supplied material is a limitation or preventive caution, not an actual critical defect. State evidence and a practical correction for each actual issue. If none are identified at a severity, write “None identified from supplied files.”
Missing, conflicting, or unsuitable inputs
- Single period only: report coverage and evidence checks; state clearly that no trend can be assessed.
- Missing definitions or denominators: do not calculate rates or compare affected values.
- Conflicting values: show each source and evidence ID, then flag reconciliation as needed.
- Missing expected indicator framework: assess supplied indicators only; do not claim complete coverage.
- Non-M&E request: explain the scope and stop.
Completion checklist
- Exact severity headings are present.
- Periods, denominators, populations/cohorts, units, and cumulative/period basis are explicit.
- Single-period inputs are not described as trends.
- Missing data is not treated as zero or proof of noncollection.
- Arithmetic, source claims, and interpretations are separated.
- Comparisons use compatible definitions and periods or are declined.
- No causal attribution is inferred from simple pre/post change.
Interruption and resumption
If interrupted, preserve the actual evidence review, extracted values, evidence register with source filenames/versions or dates, and unresolved reconciliation decisions. Resume only from files and handover supplied for the resumed task. Check whether sources changed and flag differences. Record recalculations and edits. Never upgrade a proposal, assumption, or pending decision into an approved result or correction.
Files for This Job
The individual ZIP can be uploaded to claude.ai as a custom skill; that was checked for one skill only. It is not a Claude Code plugin. Install and Plugin ZIPs
Evidence and Limits
Checked in Claude Code on fictional cases, including incomplete and unsuitable inputs, with the outputs reviewed by a second model. A browser upload check has passed for one skill (Evaluation Questions) on a paid plan. The Anthropic help page says Free plans can use uploaded skills; we did not test a Free account. Practitioner feedback is not checked yet.
Check the actual output against your source documents, especially numbers, missing data, proposed owners and approval status. Treat the result as an AI-assisted draft. Markdown and text tables are the checked output; Word, PDF and spreadsheet output are not promised. Keep each method's rating rules distinct from site rubric scores.
Source revision 5a6819f · Checked 2026-10-26