analyze-log

Analyze a gptel HTTP log file and trace the multi-agent conversation flow

IndexedGPL-3.0★ 16

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/frauh0lle-analyze-log

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Analyze a gptel HTTP log file and trace the multi-agent conversation flow

Use cases: agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/analyze-log

What's inside

Skill name: analyze-log
Description: Analyze a gptel HTTP log file and trace the multi-agent conversation flow
License: GPL-3.0
Instructions: 26 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

Analyze the gptel HTTP log file at the path given in `$ARGUMENTS`.

If no path is given, look for the most recent `*.log` file in the
current workspace root.

Run the analyzer script:

```!
python3 ${MEVEDEL_SKILL_DIR}/../../scripts/analyze-gptel-log.py $ARGUMENTS
```

After seeing the trace output, provide a brief interpretation covering:

1. **Flow correctness**: Did requests flow in the expected order?
   Did each agent get the right number of turns?
2. **Result deliveries**: Which agents received terminal RESULT envelopes,
   and when?
3. **Message delivery**: Were any SendMessage MAIL envelopes visible?
4. **Anomalies**: Any missing responses, unexpected agent counts,
   or mismatched token counts?
5. **Timing**: How long did the full flow take? Any suspiciously
   long gaps?

Lead with the trace conclusion, retaining the evidence for anomalies, timing, and material uncertainty.

From FrauH0lle/mevedel, GPL-3.0.

Signals

Stars: 16
Forks: 1
Open issues: 0
Last commit (this folder): Sep 14, 2026 (1 month ago)
Last release: Oct 22, 2026 (6 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: GPL-3.0
Repository: github.com/FrauH0lle/mevedel
Website: frauh0lle.github.io/mevedel/
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from FrauH0lle

Cite this page

analyze-log skill. Agent Mart. https://agentmart.dev/skills/frauh0lle-analyze-log (last updated 2026-10-24)