Aar
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
Install
$ agentstack add skill-neurofoo-agent-skills-aar ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-neurofoo-agent-skills-aar) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
After-Action Review
Conduct a structured debrief to extract learning from any significant event or experience.
Instructions
Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.
Output Format
Event: What are we reviewing? Date: When did it happen? Participants: Who was involved?
1. What Was Expected?
Before the event, what did we think would happen?
Goals/Objectives
- [What were we trying to achieve?]
Plan
- [What was the plan to achieve it?]
Success Criteria
- [How would we know if we succeeded?]
Assumptions
- [What did we assume would be true?]
2. What Actually Happened?
Facts only—what occurred, not why
Timeline | Time | Event | |------|-------| | [When] | [What happened] |
Outcomes
- [What results did we get?]
Compared to Expected | Expected | Actual | Gap | |----------|--------|-----| | [expectation] | [reality] | [+/-] |
3. Why the Difference?
Analysis of the gap between expected and actual
What Went Well (sustain these) | Success | Contributing Factors | |---------|---------------------| | [what worked] | [why it worked] |
What Didn't Go Well (improve these) | Problem | Root Cause | |---------|-----------| | [what failed] | [why it failed] |
Surprises
- [Things we didn't anticipate]
4. What Do We Do Next?
Specific actions to sustain or improve
Sustain (keep doing these) | Action | Owner | How to Protect It | |--------|-------|-------------------| | [what to continue] | [who] | [mechanism] |
Improve (change these) | Action | Owner | By When | |--------|-------|---------| | [what to change] | [who] | [deadline] |
Key Takeaways Top 3 lessons from this review:
- [Lesson]
- [Lesson]
- [Lesson]
Follow-up When will we check if improvements are working?
Guidelines
- Do this soon—memory fades fast
- Be specific: "Communication failed" → "We didn't update Slack until hour 3"
- Balance: Include what went well, not just problems
- Assign owners: Insights without ownership become forgotten
- Make it safe: Blame shuts down honesty
$ARGUMENTS
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: neurofoo
- Source: neurofoo/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.