task-result
Skill1 starsChanged 50 days agoMITView on GitHub
Retrieve Task deliverables and explain completion evidence, partial results, and concerns.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skillsSkill
- task-createSkill
- task-listSkill
- task-signalSkill
- task-statusSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 8
Read the operation contract and completion evidence policy.
- Distinctive: line 16
If runtime reports completion but evidence is missing or contradictory, report both facts and the verification gap.
- Distinctive: line 18
If work is still running, label artifacts as intermediate.
- Distinctive: line 20
If result querying is unavailable, do not manufacture a result from chat memory.
≈ “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
task-result
Read the operation contract and completion evidence policy. Resolve the Task ID and query authoritative result/state. Retrieve only artifacts needed to answer; retain source references and recorded verification outcomes. Compare available evidence with the accepted completion contract. Lead with the outcome, then deliverables and the evidence supporting each material claim. Mark partial output, unavailable artifacts, failed checks, and uncertainty. A worker summary or successful exit is not proof of completion. If runtime reports completion but evidence is missing or contradictory, report both facts and the verification gap. Do not independently rewrite lifecycle state. If work is still running, label artifacts as intermediate. Do not claim delivery merely because an artifact reference exists but cannot be accessed. If result querying is unavailable, do not manufacture a result from chat memory.
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.