CtrlK
BlogDocsLog inGet started
Tessl Logo

signals-scout-apm

Signals scout for PostHog distributed tracing (APM / OpenTelemetry spans). Watches per-service RED metrics for error-rate and latency regressions, new error signatures, and traffic cliffs.

66

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced scout body with explicit validation checkpoints and clean deferral to bundled skills; its only weaknesses are minor redundancy of the core discriminator and a somewhat long overview.

Suggestions

Consolidate the repeated 'rate vs raw total' emphasis into the discriminator section once, cross-referencing it from later sections instead of restating.

Consider moving the profile-shape table or the per-pattern Explore detail into a reference file to shorten the overview.

DimensionReasoningScore

Conciseness

Dense and information-rich, assuming Claude's competence (no explaining what tracing or RED metrics are); the 'rate not raw total' discriminator is restated a few times across sections and could be trimmed slightly.

4 / 5

Actionability

Fully actionable: names exact tools with concrete parameters (e.g. `query-apm-spans` with `flatSpans: true` / `rootSpans: false`, `apm-spans-aggregate` with a copy-ready query JSON, attribute keys like `server.address`, `db.system`, `service.version`, `status_code = 2`).

5 / 5

Workflow Clarity

A clearly sequenced run (oriented → discriminator → profile → explore → memory → decide → close out) with explicit validation — a 'Disqualifiers (skip these)' checklist, the 'latest complete bucket' rule, and the ≥2-complete-buckets guard against partial-bucket false reads — plus edit-vs-author and append_evidence feedback loops.

5 / 5

Progressive Disclosure

Well-organized into clear sections and appropriately offloads detail to the bundled `exploring-apm-traces` skill and `authoring-scouts → references/report-contract.md` (one level deep, clearly signaled); the body is long for an overview and no bundle files exist in this skill's own directory to verify structure against.

4 / 5

Total

18

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, distinctive, third-person description that concretely names the signals it watches, but it omits an explicit 'Use when...' trigger clause, capping completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when investigating PostHog distributed tracing / APM regressions — error-rate steps, latency regressions, new error signatures, or service traffic cliffs.'

Add a couple of natural user phrasings ('traces', 'spans', 'slow requests') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (PostHog distributed tracing / APM / OpenTelemetry spans) and lists multiple concrete signal types — 'error-rate and latency regressions, new error signatures, and traffic cliffs' — giving comprehensive coverage of what the scout watches.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Strong natural-keyword coverage for the target audience ('distributed tracing', 'APM', 'OpenTelemetry', 'spans', 'RED metrics'), with a few common variations a user might say ('traces', 'performance monitoring') absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche — PostHog APM/distributed-tracing regression scouting — with distinct triggers and minimal overlap with sibling AI-observability or logs scouts.

5 / 5

Total

17

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository
PostHog/posthog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.