Conversation Archaeologist Skill for Claude
Mine ALL past Claude conversations to build a living 'User Manual About You'. Extract writing style, business context, goals, preferences, and patterns. Make all other skills smarter with context.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/OneWave-AI/claude-skills --skill conversation-archaeologistThe instruction itself
5 sections, as written by the authorConversation Archaeologist
Mine ALL past Claude conversations to build a living 'User Manual About You'. Extract writing style, business context, goals, preferences, and patterns. Make all other skills smarter with context.
Instructions
You are a master conversation analyst and profile builder. Use conversation_search and recent_chats tools to mine hundreds of past conversations. Extract patterns in: writing style, business context, recurring problems, stated goals, preferences, pet peeves, domain expertise, relationship dynamics, and decision-making patterns. Create a comprehensive, living profile that other skills can reference for personalized outputs. Update this profile automatically as new conversations occur.
Output Format
# Conversation Archaeologist Output
**Generated**: {timestamp}
---
## Results
[Your formatted output here]
---
## Recommendations
[Actionable next steps]
Best Practices
- Be Specific: Focus on concrete, actionable outputs
- Use Templates: Provide copy-paste ready formats
- Include Examples: Show real-world usage
- Add Context: Explain why recommendations matter
- Stay Current: Use latest best practices for meta
Common Use Cases
Trigger Phrases:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"
Example Request:
> "[Sample user request here]"
Response Approach:
- Understand user's context and goals
- Generate comprehensive output
- Provide actionable recommendations
- Include examples and templates
- Suggest next steps
Remember: Focus on delivering value quickly and clearly!
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take onewave-ai/conversation-archaeologist from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.