sd-skill-retro

Audit skill triggering against a finished session and route findings to owning surfaces.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-skill-retro-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-skill-retro
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/contrib/sd-skill-retro
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-skill-retro-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a working session, it is hard to know whether the right skills fired, which ones were missed, and where the fix belongs. This Skill reconstructs the trigger record from the session log and skill files on disk, classifies every miss by the channel that failed, and routes each vetted finding to the surface that owns the repair. ## Core Features & Use Cases - Trigger record reconstruction: Lists which skills actually loaded during the session and verifies each cited skill's frontmatter on disk before judging its trigger text. - Five finding classes: Categorizes outcomes as fired-and-earned, should-have-fired, fired-wrongly, fired-and-ignored, or uncovered gap, each mapped to the trigger channel that failed. - Owner-based routing: Sends defects in sd-* skills to the skills/ directory, files work items against other repositories, and forwards uncovered gaps to sd-propose-skills. - Use Case: After a long development session, ask for a skill retro to discover that a planning skill never fired because its description wording missed the opening request, then get a vetted, routed fix proposal. ## Quick Start Ask the AI to run a skill retro on the session that just finished, reviewing which skills fired, which were missed, and where each fix should be filed.

Frequently Asked Questions about sd-skill-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit which skills fired during a session?▼

Invoke the skill retro explicitly after a session ends. It reconstructs the trigger record from the session log, verifies each skill's file on disk, and classifies outcomes into five finding classes with evidence.

What is the difference between a skill retro and a work retrospective?▼

A skill retro audits skill triggering only: what fired, what missed, and what gaps exist. Retrospectives of the work itself belong to sd-retro, and formal incident analysis belongs to sd-postmortem.

Why did a skill not trigger even though it covers the task?▼

The retro classifies misses by failed channel: entry-time phrase match, in-body cross-reference, artifact or action boundary, or deterministic hook. An installed skill that never fired is a routing defect, not a missing skill.

Can the skill retro run automatically at session end?▼

No. It is user-invoked only and must never self-trigger or treat an ordinary session end as an invitation. The audit is also read-only until the user approves a routed finding.

What happens to findings about skills owned by other repositories?▼

Defects in surfaces another repository owns are filed as work items against that repository, never patched in a consumer checkout. Uncovered gaps become input for sd-propose-skills.