agentleFS
lza6lza6/claw-code-tingfeng/skills/trace/SKILL.md

trace

Skill5 starsChanged 12 days agoMITView on GitHub

Show agent flow trace timeline and summary

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use deepinit, map and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • woosikkimSkill

    deepinit

    Generate hierarchical AGENTS.md codebase maps for agent context

    Also in 3 projects that use this

  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 4 projects that use this

  • buddyhSkill

    deep-dive

    Deep dive on any topic. Decomposes into subtopics, researches each in parallel with thorough source gathering, then synthesizes into a comprehensive report (4,000-10,000+ words, 40-100+ sources). Scales depth dynamically based on topic complexity. Use when asked for a deep dive, deep research, comprehensive analysis, or thorough investigation of a topic.

    Also in 3 projects that use this

  • markmdevSkill

    self-improve

    Analyze Claude Code sessions to find workflow frictions, underused tools, stale instructions, documentation gaps, and opportunities for new skills or automation. Produces actionable improvement suggestions with prioritized recommendations. Use when the user says "self-improve", "analyze my workflow", "what can we improve", "find frictions", "optimize workflow", or asks about improving their Claude Code setup. Also suggest running this after long sessions, multi-session projects, or when the user seems frustrated with repetitive work.

    Also in 3 projects that use this

  • LangChainSkill

    remember

    Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.

    Also in 4 projects that use this

  • MicrosoftSkill

    skillify

    Capture a repeatable process from the current session into a reusable Amplifier SKILL.md skill file. Use when the user wants to create a skill, save a workflow as a skill, turn a process into a reusable skill, or mentions "skillify", "create skill", "make a skill", "save as skill", "capture workflow", "turn this into a skill", "new skill", or wants to automate a repeatable process they just performed.

    Also in 3 projects that use this

The file

Files
SKILL.md

Agent Flow Trace

[TRACE MODE ACTIVATED]

Objective

Display the flow trace showing how hooks, keywords, skills, agents, and tools interacted during this session.

Instructions

工具名以真实注册为准(src/core/mcp/trace_server.py 的 TRACE_SERVER_TOOLS)。 早期文档写的 trace_timeline / trace_summary 在全仓没有任何实现, 照着调只会得到「未知工具」。下面是现在真实可用的四个工具。

  1. get_recent_traces —— 列出最近的追踪(先看有哪些 trace_id)
    • 参数:limit(默认 10)
  2. get_trace —— 取某条追踪的完整 span 列表(时间顺序)
    • 参数:trace_id
  3. summarize_trace —— 聚合统计(span 数、最慢 span、错误数)
    • 参数:trace_id
  4. export_trace —— 导出为 json / text,便于贴到报告里
    • 参数:trace_id、format(默认 json)

采集侧:Agent 引擎在 SESSION_START / SESSION_END / PRE_TOOL_USE / POST_TOOL_USE / TOOL_ERROR 五个 hook 点已接线,把 hook 里记录的事件 写进追踪即可得到完整时间线;export_trace 的输出就是"发生了什么"的可核对版本。

Output Format

Present the timeline first, then the summary. Highlight:

  • Mode transitions (how execution modes changed)
  • Bottlenecks (slow tools or agents)
  • Flow patterns (keyword -> skill -> agent chains)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.