agentleFS
Sign inStart free
tuana-vntuana-vn/system-reverse-engineer/.github/skills/observability-traceability-analysis/SKILL.md

observability-traceability-analysis

Skill0 starsChanged 2 months agoMITView on GitHub

Analyze whether a system has enough evidence to trace an operation across internal layers and external boundaries, identify troubleshooting blind spots, and design or review audit/log traceability without confusing logs with source-of-truth architecture.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not assume custom IDs can be propagated to external systems.

    line 37
  2. Distinctive:

    Do not promote architecture claims merely because logs show one execution.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Observability and Traceability Analysis

Core Goal

For a selected operation, determine whether support can reconstruct:

Inbound request/event
→ business operation
→ routing decision
→ concrete implementation
→ external interaction
→ external result/error
→ internal result

Traceability Dimensions

At each step inspect:

  • timestamp
  • request/operation identity
  • target/entity identity
  • business operation
  • selected implementation
  • mode/config context
  • downstream command/API operation
  • downstream-generated identifiers if naturally available
  • result/error
  • duration

Do not assume custom IDs can be propagated to external systems.

Gap Matrix

Flow StepExisting EvidenceMissing EvidenceTroubleshooting ImpactProposed Improvement

Classify:

  • TRACEABLE
  • PARTIALLY TRACEABLE
  • BLIND SPOT

Important Distinction

  • Source code establishes architectural behavior.
  • Audit/log records establish what happened in a particular execution.
  • Neither should be mistaken for the other.

Output

docs/reverse-engineering/observability/<scope>-traceability-analysis.md

4.0 Source-of-Truth Constraint

Do not promote architecture claims merely because logs show one execution.

Runtime logs prove execution truth for that instance. Source/wiring proves architectural behavior.

Cross-reference both when possible.

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.

Check your setup, free