docs-retro

Parse JSONL transcripts to identify documentation gaps and missing skills.

71|10|Updated Aug 20, 2025
One-click install
npx skills add https://github.com/elastic/elastic-docs-skills --skill docs-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-retro
Source: https://github.com/elastic/elastic-docs-skills/tree/main/skills/workflow/docs-retro
Command: npx skills add https://github.com/elastic/elastic-docs-skills --skill docs-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes Claude Code session transcripts to identify documentation gaps, evaluate skill usage, and suggest missing skills, streamlining documentation improvement workflows.

Core Features & Use Cases

  • Identify Documentation Opportunities: Pinpoint content gaps, outdated information, and areas needing new documentation based on user interactions.
  • Evaluate Skill Effectiveness: Assess how well existing skills were used, identify friction points, and highlight underutilized or missing skills.
  • Use Case: After a documentation-focused session, use this skill to generate a report detailing what documentation was missing, what skills could have been better utilized, and actionable steps for improving the documentation.

Quick Start

Run a retrospective analysis on the current session transcript.

Frequently Asked Questions about docs-retro

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

FAQPage Schema
How do I analyze Claude Code session transcripts for documentation gaps?

You can analyze Claude Code session transcripts by parsing JSONL files to extract conversation flow, tool calls, and docs touched. This retrospective analysis surfaces content gaps, outdated information, and areas needing new documentation based on user interactions.

What is session retrospective analysis and when do I need it for workflow improvement?

Session retrospective analysis is a post-session process that evaluates skill usage, identifies friction points, and highlights underutilized capabilities. You need it after documentation-focused sessions to pinpoint missing skills and generate actionable steps for improving assistant capabilities.

Can I evaluate skill effectiveness and find missing skills from JSONL conversation transcripts?

Yes, you can evaluate skill effectiveness from JSONL conversation transcripts by extracting skills invoked and errors encountered. This identifies friction points, highlights underutilized skills, and surfaces missing skills needed to streamline documentation improvement workflows.

What's the best way to identify content gaps from post-session analysis?

The best way to identify content gaps is running a retrospective analysis on session transcripts to parse conversation flow and docs touched. This pinpoints outdated information and documentation opportunities based on actual user interactions and decision points.

Does Claude Code session analysis work without additional dependencies?

Yes, Claude Code session analysis works without additional dependencies. It directly parses JSONL transcripts to extract tool calls, syntax issues, and decision points, requiring only the session transcript files to identify documentation opportunities and evaluate skill usage.