response-analyzer

Solid

MCP Response Analyzer pattern - Write large responses to temp files, load summaries into context

AI & Automation 24 stars 3 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
47
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
98
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # MCP Response Analyzer Reduce context bloat: write large outputs to `/tmp/aura-frog/`, load only summaries. --- ## Triggers ```toon triggers[5]{scenario,threshold,action}: Command output,>100 lines,Save to temp + summarize API response,>5KB,Save JSON + extract key fields File search results,>50 files,Save list + show top 10 Test output,>50 lines,Save full + summarize pass/fail Build output,>100 lines,Save full + show errors only ``` --- ## Directory ``` /tmp/aura-frog/ ├── responses/ # cmd-*.txt, api-*.json, search-*.txt ├── summaries/ # summary-*.md └── session/ # per-session data ``` --- ## Patterns ### Large Command Output ```bash npm test > /tmp/aura-frog/responses/test-$(date +%s).txt 2>&1 grep -E "(PASS|FAIL|Tests:|Suites:)" /tmp/aura-frog/responses/test-*.txt | tail -10 ``` ### API Response ```bash curl url > /tmp/aura-frog/responses/api-$(date +%s).json jq '{total: .data | length, first_3: .data[:3] | map(.name)}' /tmp/aura-frog/responses/api-*.json ``` ### File Search ```bash find . -name "*.ts" > /tmp/aura-frog/responses/search-$(date +%s).txt echo "Found $(wc -l < file) TypeScript files"; head -10 file ``` --- ## Token Savings ```toon savings[4]{...

Details

Author
nguyenthienthanh
Repository
nguyenthienthanh/aura-frog
Created
9 months ago
Last Updated
1 weeks ago
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Featured

tldr

TLDR code analysis — call graphs, semantic search, impact, dataflow, for far fewer tokens than reading the files raw. Triggers "who calls X", "what affects X", "blast radius", before large file reads or refactors.

44 Updated today
darkroomengineering
AI & Automation Listed

mcp-overflow-delegate-summary

Use when an MCP tool result is dumped to a tool-results/*.txt file because it exceeded the token cap — delegate the read+summarize to a general-purpose subagent (or jq the file for targeted extraction) so the raw payload stays out of the main context.

0 Updated 3 weeks ago
hjr15
AI & Automation Listed

cachewise

Prompt-cache economics forensics — why your Claude Code tokens burn so fast, with the numbers to prove it. Parses local ~/.claude transcripts (0 tokens, a bundled Python script does the counting) and attributes every cache-miss rebuild to a cause — idle gaps past the 5-min TTL, mid-session model/effort switches, prefix churn (MCP tool-lists, edited CLAUDE.md, dynamic content), and cold re-boots of a session you could have resumed — each priced in real USD, then prescribes the fixes ranked by dollars saved. Tracks before/after in out/cachewise/tracker.md so the next run measures whether a fix worked. Use when the user asks why they hit usage limits so fast, wants their cache hit rate or token spend analyzed, or where their tokens are going — e.g. "/cachewise", "analyze my prompt cache", "what's burning my tokens". For recurring behavior mistakes use tune; for today's schedule use daybrief.

9 Updated 3 days ago
duthaho