analyze-tools

Analyze Claude tool usage patterns from vibe-check MCP server data.

1|1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/wanderingstan/vibe-check --skill analyze-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-tools
Source: https://github.com/wanderingstan/vibe-check/tree/main/skills/vibe-check-analyze-tools
Command: npx skills add https://github.com/wanderingstan/vibe-check --skill analyze-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude tool usage is scattered across conversations, making it hard to identify patterns and optimize tooling. This skill consolidates tool usage data to reveal which tools are most prevalent and how they are combined, enabling data-driven workflow improvements.

Core Features & Use Cases

  • Analyze tool usage across Claude conversations via the vibe-tools endpoint.
  • Identify top tools, usage counts, percentages, and tool combinations.
  • Support time-bounded analyses and repository-specific patterns to tailor insights for teams.

Quick Start

Ask Claude to analyze your tool usage by requesting a 30-day report from the vibe-check MCP server.

Frequently Asked Questions about analyze-tools

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

FAQPage Schema
How do I analyze Claude tool usage patterns across conversations?

This Skill analyzes Claude tool usage patterns by consolidating scattered conversation data via the vibe-tools endpoint. It identifies top tools, usage counts, percentages, and tool combinations to reveal workflow insights.

What insights can I get from analyzing tool usage in the vibe-check MCP server?

Analyzing tool usage in the vibe-check MCP server provides insights into top tools, usage counts, percentages, and tool combinations. These metrics reveal prevalent tools and workflow optimization opportunities.

Can I generate a time-bounded report of Claude tool usage?

Yes, you can generate a time-bounded report of Claude tool usage. This Skill supports time-bounded analyses to tailor insights for specific periods, such as requesting a 30-day report from the vibe-check MCP server.

Do I need any specific dependencies to analyze repository-specific tool patterns?

No external dependencies are required to analyze repository-specific tool patterns. The Skill operates independently to fetch usage data and identify repository-specific patterns within the vibe-check MCP server.

How does this approach identify tool combinations within Claude conversations?

This approach identifies tool combinations by fetching consolidated usage data from the vibe_tools endpoint and processing how individual tools are used together across conversations. This reveals frequent tool combinations when requested.