Capture technical session decisions, outcomes, and next steps in structured logs.
npx skills add https://github.com/axivo/claude --skill conversation-log
Please help me install this Agent Skill. Skill: conversation-log Source: https://github.com/axivo/claude/tree/main/skills/conversation-log Command: npx skills add https://github.com/axivo/claude --skill conversation-log
This Skill automates the meticulous documentation of technical sessions, ensuring factual accuracy and precision. It eliminates the burden of manually recalling and structuring complex discussions, decisions, and outcomes, making knowledge retention effortless and freeing you to focus on the technical work itself.
Create a conversation log for our recent debugging session on the API integration, focusing on the root cause and solution.
High-intent search queries and answers about installing and using this skill.
Document technical sessions by capturing decisions, outcomes, and next steps in structured conversation logs. This Skill guides you to record what actually happened during architecture reviews, debugging sessions, and implementation discussions, ensuring factual accuracy without editorialization so stakeholders have a verifiable record.
Technical meeting logs should capture design problems evaluated, approaches considered, recommended solutions, action items, command sequences, error messages, tool versions, architecture decisions, and validation approaches. This comprehensive coverage preserves critical details for easy reference and continuation of work.
Structured conversation logs are essential for architecture reviews, technical discussions, implementation sessions, and debugging work where precise, verifiable documentation satisfies requirements for factual accuracy and comprehensive coverage. They eliminate manual recall burden and ensure all stakeholders stay aligned.
Yes. This Skill automates meticulous documentation of technical sessions, generating detailed logs that summarize decisions and outcomes systematically. It frees you to focus on technical work while ensuring knowledge retention and eliminating the burden of manually structuring complex discussions.
Create conversation logs for debugging sessions by recording the root cause identified, solution implemented, command sequences executed, error messages encountered, and validation approaches used. This structured approach ensures the technical context and resolution path are preserved for future reference.
Factual session logs record what actually happened—decisions made, outcomes reached, and steps taken—without subjective interpretation or editorialization. This distinction ensures logs serve as accurate, verifiable documentation rather than personal commentary, critical for architecture reviews and technical decisions.
openyakTransform meeting transcripts into structured Markdown notes with decisions and action items.
pelchersGenerate structured session reports from git logs, conversation logs, and system states.
alangebIndex session logs into a Markdown knowledge base with retrieval tools.
Fancu1Transform meeting transcripts into structured summaries with owner-tagged action items.
