skills/skill-performance-profiler/SKILL.md
Analyzes skill usage patterns across conversations to track token consumption, identify heavy vs. lightweight skills, measure invocation frequency, detect co-occurrence patterns, and suggest consolidation opportunities. Use when the user asks to analyze skill performance, optimize skill usage, identify token-heavy skills, find consolidation opportunities, or review skill metrics.
npx skillsauth add auldsyababua/instructor-workflow skill-performance-profilerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive analysis tool for tracking and optimizing skill usage patterns, token consumption, and identifying opportunities for skill consolidation.
Use this skill when users request:
Trigger phrases include: "analyze my skills," "which skills use the most tokens," "skill performance," "consolidation opportunities," "optimize my skills," "skill usage report," etc.
The analysis involves three main steps:
Use the recent_chats tool to gather conversations for analysis. The time range and number of conversations depends on the user's request:
# For recent analysis (default - last 20 conversations)
recent_chats(n=20)
# For specific time periods
recent_chats(n=20, after="2025-10-01T00:00:00Z")
# For comprehensive analysis (iterate to get more)
recent_chats(n=20, before=earliest_timestamp_from_previous_call)
Extract the conversation content and metadata (especially updated_at timestamps) from the results.
Create a JSON file containing the conversation data in this format:
{
"conversations": [
{
"content": "full conversation text including tool calls and responses",
"updated_at": "2025-10-22T10:30:00Z"
}
]
}
Save this as /home/claude/conversations.json.
Execute the analysis script:
cd /home/claude
python3 /mnt/skills/user/skill-performance-profiler/scripts/analyze_skills.py conversations.json
This produces conversations_analysis.json with comprehensive metrics including:
Create formatted output using the report generator:
# Generate markdown report
python3 /mnt/skills/user/skill-performance-profiler/scripts/generate_report.py conversations_analysis.json markdown
# Generate CSV export
python3 /mnt/skills/user/skill-performance-profiler/scripts/generate_report.py conversations_analysis.json csv
# Generate both formats
python3 /mnt/skills/user/skill-performance-profiler/scripts/generate_report.py conversations_analysis.json both
This creates:
conversations_report.md: Comprehensive markdown report with all metricsconversations_export.csv: Tabular data for spreadsheet analysisPresent the analysis to the user in the most appropriate format:
/mnt/user-data/outputs/ and provide a linkInvocation Count: Number of times a skill was used across analyzed conversations
Token Consumption:
Skill Categories (by average tokens):
Co-occurrence Rate: Percentage of time skills are used together, indicating potential consolidation opportunities
Consolidation Opportunities: Skill pairs used together ≥50% of the time, suggesting they might benefit from being merged into a single skill
Quick Performance Check:
User: "Which of my skills are using the most tokens?"
→ Collect 20 recent chats, analyze, show top 5 heaviest skills
Comprehensive Audit:
User: "Give me a full analysis of my skill usage over the last month"
→ Collect conversations from last month (multiple calls to recent_chats)
→ Run full analysis
→ Generate markdown report and provide download link
Consolidation Analysis:
User: "Are there skills I should consolidate?"
→ Analyze conversation patterns
→ Focus on consolidation_opportunities in results
→ Present recommendations with supporting data
Trend Analysis:
User: "Show me skill usage trends over time"
→ Collect conversations across time periods
→ Analyze and group by time buckets
→ Create visualization artifact with trend charts
Token counts are estimated using a 4:1 character-to-token ratio. This is an approximation since:
For more accurate analysis, actual token counts from the API would be ideal, but this estimation provides useful relative comparisons for optimization decisions.
Choose output format based on user needs:
Move all generated files to /mnt/user-data/outputs/ and provide computer:// links so users can download them.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
testing
Three-step Linear update protocol after job completion - update child issue, check parent completion, update parent if all children done
testing
This skill should be used whenever users need help planning trips, creating travel itineraries, managing travel budgets, or seeking destination advice. On first use, collects comprehensive travel preferences including budget level, travel style, interests, and dietary restrictions. Generates detailed travel plans with day-by-day itineraries, budget breakdowns, packing checklists, cultural do's and don'ts, and region-specific schedules. Maintains database of preferences and past trips for personalized recommendations.
tools
Proactive token budget assessment and task chunking strategy. Use this skill when queries involve multiple large file uploads, requests for comprehensive multi-document analysis, complex multi-step workflows with heavy research (10+ tool calls), phrases like "complete analysis", "full audit", "thorough review", "deep dive", or tasks combining extensive research with large output artifacts. This skill helps assess token consumption risk early and recommend chunking strategies before beginning work.