Skip to content
TrustedSkillsbeta
Back to all skills

conversation-analyzer

Checked
mhattingpete·v1.0.0·agents·Apache-2.0

Analyzes your Claude Code conversation history to identify patterns, common mistakes, and opportunities for workflow improvement. Use when user wants to understand usage patterns, optimize workflow, i

Install on your platform

Showing OpenClaw.

  1. 1

    Run this in your terminal

    terminal
    $ 

What we know about this skill

Publisher

mhattingpete

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mhattingpete/claude-skills-marketplace at b5b34bcf4c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
2 files, 502 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The mhattingpete-conversation-analyzer skill analyzes past conversations within the Claude Code environment. It identifies recurring patterns in your interactions, highlights frequent errors or misunderstandings, and suggests potential improvements to your coding workflow. This allows for a data-driven approach to refining how you interact with Claude Code.

When to use it

  • Workflow Optimization: You've noticed inconsistencies in the quality of code generated over time and want to understand why.
  • Error Pattern Identification: You repeatedly encounter similar errors or unexpected behavior from Claude Code and need help pinpointing the root cause.
  • Usage Analysis: You want a summary of how you are using Claude Code, including common prompt structures and areas where you might be over-relying on certain features.
  • Training/Onboarding: To understand best practices for new users interacting with Claude Code.

Key capabilities

  • Identifies patterns in conversation history.
  • Highlights common mistakes or misunderstandings.
  • Suggests workflow improvements.
  • Provides a summary of usage patterns.

Example prompts

  • "Analyze my last 20 conversations with Claude Code and identify any recurring themes."
  • "Show me the most frequent types of errors I've encountered in our interactions."
  • “What are some ways I can improve my prompting style based on past conversation data?”

Tips & gotchas

The skill requires access to your Claude Code conversation history. The quality of the analysis depends heavily on the volume and clarity of the historical data available.