agentsclimarketplace

Observability tracing

Skill planifest/planifest-framework/planifest-framework/external-skills/observability-tracing

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill observability-tracing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Observability tracing workflow for distributed trace coverage and critical-path diagnosis. Use when cross-service request paths need instrumentation or analysis to localize latency/error bottlenecks; do not use for business-feature implementation logic.

SKILL.md

1.9 KB, 327 tokens by cl100k_base, as published. Nobody here has run it

Observability Tracing

Overview

Use this skill to make critical request flows traceable end-to-end for latency and failure diagnosis.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Span attribute and sampling rules:
    • references/span-attribute-and-sampling-rules.md

Templates And Assets

  • Trace coverage map template:
    • assets/trace-coverage-map-template.md
  • Trace quality checklist:
    • assets/trace-quality-checklist.md

Inputs To Gather

  • Critical cross-service user flows.
  • Current instrumentation and propagation gaps.
  • Sampling constraints and storage budget.
  • Incident diagnosis requirements.

Deliverables

  • Trace coverage map for critical paths.
  • Span attribute conventions and sampling policy.
  • Validation evidence for trace queryability.

Workflow

  1. Define coverage targets in assets/trace-coverage-map-template.md.
  2. Apply span/sampling policy from references/span-attribute-and-sampling-rules.md.
  3. Validate quality via assets/trace-quality-checklist.md.
  4. Fix missing spans/attributes on critical paths.
  5. Publish tracing baseline and ownership.

Quality Standard

  • Critical flows are traceable end-to-end.
  • Span attributes are consistent for diagnosis queries.
  • Sampling preserves incident usability.

Failure Conditions

  • Stop when critical paths remain untraceable.
  • Stop when trace context propagation is inconsistent.
  • Escalate when tracing gaps block root-cause isolation.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.