One-click install
npx skills add https://github.com/skmtc/skmtc --skill skmtc-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skmtc-retro
Source: https://github.com/skmtc/skmtc/tree/main/deno/docs/skills/skmtc-retro
Command: npx skills add https://github.com/skmtc/skmtc --skill skmtc-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents valuable lessons from SKMTC work from being lost by turning session surprises, debugging friction, and newly acquired knowledge into structured, reviewable records.

Core Features & Use Cases

  • Friction Capture: Records mistakes, unexpected API behavior, overridden assumptions, repeated debugging cycles, and other actionable obstacles.
  • Knowledge Tracking: Documents facts learned during the session that were missing from training or existing documentation, including their documentation implications.
  • Priority Ranking: Produces a focused list of the two or three findings with the greatest potential impact on SKMTC skills, documentation, or code.
  • Use Case: After authoring a generator or completing a multi-step SKMTC debugging session, use the Skill to create or update a dated friction-log entry without fabricating observations or duplicating existing records.

Quick Start

Run a SKMTC retrospective on the current session and log its actionable friction, acquired knowledge, and top documentation priorities.

Frequently Asked Questions about skmtc-retro

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

FAQPage Schema
How do I document debugging friction and unexpected API behavior from a work session?

To document debugging friction, you can run a retrospective on your session to capture actionable obstacles, overridden assumptions, and unexpected API behavior into a structured, reviewable Markdown record.

What is a friction log and when do I need to create one for multi-step debugging?

A friction log is a dated, append-only record that preserves lessons learned during multi-step debugging. You need one after completing substantive work sessions to prevent valuable knowledge about mistakes and obstacles from being lost.

How do I prioritize documentation tasks after authoring a generator?

After generator authoring, you can generate a focused list of the two or three findings with the greatest potential impact on skills, documentation, or code by capturing newly acquired knowledge and ranking it by priority.

Can I use this to track knowledge gaps missing from existing CLI documentation?

Yes, you can track facts learned during your session that were missing from existing documentation. The retrospective process records these gaps and explicitly notes their documentation implications for future review.

Does the friction log entry numbering system prevent duplicate records?

Yes, the system requires inspecting session context and locating the canonical friction-log directory to preserve append-only entry numbering and index consistency, ensuring observations are captured without fabricating data or duplicating existing records.