extract-from-conversations

Extract friction-driven lessons from agent-user conversation logs into local repo packs.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill extract-from-conversations-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract-from-conversations
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/claudinite-growth/skills/extract-from-conversations
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill extract-from-conversations-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent sessions accumulate friction — misunderstandings, backtracks, and wasted wall-clock waits — that disappears when the session ends. This Skill mines captured conversation logs or the live session for those friction signals and converts them into durable rules, defaults, and conventions in the repo's local packs so the next run needs less human steering. ## Core Features & Use Cases - Friction signal detection: Identifies misunderstandings, suboptimal agent actions, and long wall-time waits, then converts each into a concrete fix such as a default, convention, footgun note, or parallelization rule. - Measured wall-time analysis: Computes real idle-wait versus compute time from the log's own timestamps and tool_use/tool_result pairs rather than estimating. - Dual-window review: Reads both the newest 24 hours of captures and the oldest 24 hours still on the conversation-logs branch for a hindsight re-read. - Provenance comments: Posts a short summarized comment on the originating PR or issue for each rule that lands, never pasting raw transcript. - Use Case: After a week of agent sessions captured on the conversation-logs branch, run a retrospective that turns repeated user corrections into standing conventions and recurring user questions into proactive self-checks. ## Quick Start Ask the agent to extract lessons from the latest captures on the conversation-logs branch and land them as a pull request for review.

Frequently Asked Questions about extract-from-conversations

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

FAQPage Schema
How do I extract lessons from an agent conversation log?▼

Read the JSONL capture end to end, hunt for friction signals like clarifying round-trips, backtracks, and idle waits, then convert each into a durable rule or default in the repo's local packs. Deliver results as a branch and PR for human review.

How do I measure wall-time waits in a session transcript?▼

Use the log's own per-entry timestamps and tool_use/tool_result pairs to compute real wall-clock numbers, separating compute time from genuine idle waiting like sleeps and polling. Never estimate; a fix is only credible against measured numbers.

What is the conversation-logs branch used for?▼

It is an orphan git branch storing session captures as JSONL files named with stamps like <stamp>--pr-<n>--<session>.jsonl. You read files with plain git commands such as git show origin/conversation-logs:<file> directly in the checkout.

Why does reading a JSONL conversation log fail with offset and limit?▼

A single JSONL line can be one tool_use or tool_result running tens of thousands of characters, so a small line window can still overflow the read cap. Check line lengths first with awk or condense the file with a script before reading.

When should a retrospective on a session not be run?▼

Never reflect-and-edit unprompted in the middle of a task, since it interrupts the work. The owner decides when a session is done enough to mine, and live-session retrospectives only happen when explicitly requested.