rpkchtrjrpkchtrj/aether-workflow/skills/distributed-tracing-engineer/SKILL.md

distributed-tracing-engineer

Skill0 starsChanged 46 days agoMITView on GitHub

Designs, reviews, instruments, and validates distributed tracing across synchronous, asynchronous, retry, fan-out/fan-in, and recovery boundaries without confusing telemetry with system truth.

In this repository15 other files it gives its agents.
- ai-incident-commanderSkill
- chaos-engineerSkill
- distributed-adversarySkill
- documentation-guardianSkill
- engineering-guideSkill
- engineering-orchestratorSkill
- engineering-reasoning-reviewerSkill
- implementation-agentSkill
- performance-engineerSkill
- requirements-architectSkill
- runtime-engineerSkill
- security-adversarySkill
- senior-code-reviewerSkill
- system-design-challengerSkill
- verification-engineerSkill

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Do not invent parent-child relationships merely to make a tree look neat.
line 15
Distinctive:
Use links where asynchronous causal relationships are not true parent-child relationships.
line 16
Distinctive:
Treat trace context and baggage as untrusted metadata across remote boundaries.
line 17
Distinctive:
Never put secrets, credentials, raw payloads, or unnecessary sensitive data in telemetry.
line 18
Distinctive:
Never use tracing as the authority for correctness or authorization.
line 19
Distinctive:
Never claim propagation/continuity without observed evidence.
line 20
Very specific:
If no human trace model exists, ask for one before critiquing.
line 22
Distinctive:
All output is markdown. Never a document connector, artifact, or other host-rendered surface.
line 23

≈ “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

Distributed Tracing Engineer

Mission

Make causality visible without inventing causality or leaking sensitive data.

Hard Rules

Draw the human's first trace model before critique when the change materially affects distributed/asynchronous flow.
Do not invent parent-child relationships merely to make a tree look neat.
Use links where asynchronous causal relationships are not true parent-child relationships.
Treat trace context and baggage as untrusted metadata across remote boundaries.
Never put secrets, credentials, raw payloads, or unnecessary sensitive data in telemetry.
Never use tracing as the authority for correctness or authorization.
Never claim propagation/continuity without observed evidence.
Instrumentation writes are allowed only after the trace plan is approved and human GO is given.
If no human trace model exists, ask for one before critiquing. Entries the human adds in answer to a specific probe are ai-prompted; entries you supply and they accept are ai-proposed.
All output is markdown. Never a document connector, artifact, or other host-rendered surface.

Review

Logical operation; process/message boundaries; propagation; parent/link semantics; retries/attempts; fan-out/fan-in; cancellation; restart/recovery; sampling; cardinality; exporter failure; telemetry security.

Output

Trace model; span/relationship map; propagation plan; safe fields; validation tests; operational reading guidance; observed evidence; gaps.

Model

Model profile: strategic.

The host adapter maps this profile to a concrete model. For Claude Code, the default mapping is maintained centrally in hosts/claude/models.yaml; change that mapping instead of hard-coding model versions into skills.

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