Task Retrospective

Conduct structured self-evaluations after tasks to analyze efficiency, accuracy, approach quality, and extract patterns for improved future performance.

Security Scan

The skill is an instruction-only retrospective template for agents and its requested footprint (no installs, no credentials) matches its stated purpose.

Purpose & Capability

Name and description describe structured self-evaluation and the SKILL.md contains only instructions for reconstructing, evaluating, extracting patterns, and recording retrospectives. There are no unrelated binaries, credentials, or installs requested.

Instruction Scope

Instructions are narrowly scoped to analyzing tasks, scoring phases, and producing structured output. They do mention reviewing prior retrospectives (e.g., "Review my last 5 retrospectives") and team/multi-agent workflows, which implies the agent may need access to stored retrospectives or agent memory. The skill does not specify where prior retrospectives live or how to access them—this is expected for a generic template but is an ambiguity the user should be aware of.

Install Mechanism

No install spec and no code files are present. Instruction-only skills write nothing to disk by themselves and pose minimal installation risk.

Credentials

The skill requests no environment variables, credentials, or config paths. There are no disproportionate privilege or secret requests relative to the retrospective purpose.

Persistence & Privilege

always is false and model invocation is allowed (the platform default). The skill does not request persistent agent-wide changes or access to other skills' configs.

Assessment

This skill is an agent-facing template for doing post-task retrospectives and is internally consistent and low-risk. Before installing, consider: (1) Where will retrospectives be stored? If you ask the agent to "Review my last 5 retrospectives", the agent will need access to whatever storage (agent memory, files, or a database) — make sure that storage is appropriate and not containing sensitive data you don't want reprocessed. (2) If you use the Team Retrospective features, avoid pasting private credentials or sensitive logs into the input. (3) If you prefer the agent not to run retrospectives autonomously, keep autonomous invocation settings as-is or restrict how the agent is allowed to invoke skills. (4) Decide a retention policy for generated retrospectives (and delete any you don't want kept). Overall this skill appears coherent and safe for use, but be mindful of the data you feed it and where its outputs are stored.

Structured self-evaluation for AI agents after completing tasks. Analyze what worked, what failed, and extract reusable patterns to improve future performance. Use after completing complex tasks, debugging sessions, or multi-step workflows.

Usage

Run a retrospective on the task I just completed.

Or with specific context:

Retrospective: [task description]. 
Outcome: [success/partial/failure].
Time spent: [duration].
What surprised me: [unexpected findings].

How It Works

1. Reconstruct — review the task timeline (steps taken, tools used, decisions made)
2. Evaluate — score each phase on efficiency, accuracy, and approach quality
3. Extract — identify reusable patterns, anti-patterns, and decision heuristics
4. Record — generate a structured retrospective for future reference

Evaluation Dimensions

Efficiency

• Were there unnecessary steps or dead ends?
• Could tool calls have been batched or parallelized?
• Was the research phase too long or too short?

Accuracy

• Was the final output correct and complete?
• Were there false starts or incorrect assumptions?
• Did the solution match the actual requirements?

Approach Quality

• Was the problem decomposition effective?
• Were the right tools chosen for each step?
• Would a different strategy have been faster?

Learning Extracted

• What new patterns can be reused?
• What anti-patterns should be avoided?
• What domain knowledge was gained?

Output Format

## Task Retrospective

### Summary
[1-2 sentences: what was the task, what was the outcome]

### Timeline
| Phase | Duration | Verdict |
|-------|----------|---------|
| Research | Xm | Efficient / Too long / Insufficient |
| Planning | Xm | Good / Skipped / Over-planned |
| Execution | Xm | Clean / Had rework / Multiple attempts |
| Validation | Xm | Thorough / Skipped / Caught issues |

### What Worked
- [Pattern that should be repeated]

### What Didn't Work
- [Anti-pattern to avoid] → [Better alternative]

### Reusable Patterns
- **Pattern name**: [Description of when and how to apply]

### Key Decisions
- [Decision point] → [Choice made] → [Outcome: good/bad/neutral]

### Improvement Actions
- [ ] [Specific action to improve future performance]

Advanced Usage

Compare Approaches

Compare my approach to [task] with the ideal approach. 
What I did: [steps].
What I should have done: [if known].

Pattern Library

Over time, retrospectives build a pattern library:

Review my last 5 retrospectives. What recurring patterns emerge?
Which improvement actions have I actually followed through on?

Team Retrospective

Run a retrospective on this multi-agent workflow.
Agents involved: [list].
Handoff points: [where work transferred between agents].
Bottlenecks: [where things slowed down].