CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

observability-triage

Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, a known-noise filter list applied automatically, and the on-demand CPU/heap profiling recipe. Use when asked to review Cloudflare logs/observability, count OOMs or worker errors, compare error rates between periods, investigate a prod error spike, or find where a worker spends CPU or memory (profiles, flamegraphs).

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

The body is an unusually lean, high-signal operational reference: executable query/CLI/API recipes, concrete counting and interpretation gotchas, and explicit checkpoints guarding against wrong conclusions. Its only structural weakness is that the triage flow and the noise-list detail live as organized sections rather than an explicit ordered workflow or a split-out reference file. Scores 4 on workflow clarity and progressive disclosure, 5 on conciseness and actionability.

DimensionReasoningScore

Conciseness

Quotes: "the API's 400s are opaque", "Grouped results are unsorted and effectively capped (~10 rows returned regardless of limit)", "an OOM kills every request pinned to the isolate at the same instant" — every line carries non-obvious, hard-won operational knowledge (opaque 400s, counting caveats, fingerprint-level noise markers) rather than concepts Claude already knows. Not 4: there is no padding or over-explanation to trim; density is high but every token earns its place.

5 / 5

Actionability

Quotes: a complete, executable telemetry query JSON body ("queryId": "adhoc", full filters/calculations/groupBys), exact CLI commands ("cf workers versions profile latest --worker-id open-seo --duration-ms 10000 --profile-type cpu > open-seo-cpu.pprof"), exact endpoints ("POST /accounts/{account_id}/workers/workers/{worker_id}/versions/latest/profile"), and a runnable script path ("node .agents/skills/observability-triage/scripts/pprof-top.mjs open-seo-cpu.pprof", verified to exist in the bundle). Copy-paste ready and covering the common cases; not 4: no gaps in the concrete guidance.

5 / 5

Workflow Clarity

Quotes: "Check $workers.scriptVersion and the scripts' modified_on before concluding a fix didn't work", "Check cloudflarestatus.com/history for the window before reading code", "repeat a capture before trusting a small frame", "judge it by the sibling request's outcome" — the sections form a coherent triage flow (access → query → count correctly → interpret failures → profile if needed → filter noise) with many explicit checkpoints. Not 5: there is no explicit ordered sequence or checklist tying the sections into a single step-by-step triage procedure; not 3: validation checkpoints are explicit and frequent, not implicit or missing.

4 / 5

Progressive Disclosure

The body is organized into well-labeled sections (Access, Query recipes, Counting gotchas, Workflow failures, Profiling, Known noise, Adding an entry) and its one bundle reference — scripts/pprof-top.mjs — is real, correctly pathed, and one level deep. Not 5: at ~100 lines, detail-heavy blocks like the per-entry known-noise fingerprints (~25 lines) are candidates for a reference file that could keep the SKILL.md overview leaner; not 3: structure and signaling are good and nothing is buried.

4 / 5

Total

18

/

20

Passed

Description

100%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.

The description cleanly separates what (verified query recipes, counting gotchas, noise filter, profiling) from when (an explicit 'Use when' clause enumerating the natural trigger phrasings). Every claim is concrete and scoped to a distinct niche, so conflict risk with other skills is minimal. This is an exemplary description.

DimensionReasoningScore

Specificity

Quotes: "verified query recipes, counting gotchas, a known-noise filter list applied automatically, and the on-demand CPU/heap profiling recipe" and "count OOMs or worker errors, compare error rates between periods, investigate a prod error spike, or find where a worker spends CPU or memory (profiles, flamegraphs)" — multiple specific concrete actions with comprehensive coverage of the skill's scope. Not 4: there are no coverage gaps; every capability the skill claims in its body is named here.

5 / 5

Completeness

Quotes: first sentence states what ("Triage OpenSEO production errors in Cloudflare Workers Observability — …") and "Use when asked to review Cloudflare logs/observability, count OOMs… investigate a prod error spike, or find where a worker spends CPU or memory" states when with concrete trigger phrases. Matches the anchor-5 example structure exactly; not 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Quotes: "review Cloudflare logs/observability", "count OOMs or worker errors", "compare error rates between periods", "investigate a prod error spike", "profiles, flamegraphs" — these are the natural phrasings a user would say, including synonyms (OOMs, profiles, flamegraphs, CPU/memory). Not 4: no common variation of the niche's trigger vocabulary is missing.

5 / 5

Distinctiveness Conflict Risk

Quotes: "Cloudflare Workers Observability", "count OOMs", "on-demand CPU/heap profiling" — a clear niche with distinct, product-specific triggers that would not fire for generic logging, error-handling, or profiling skills. Not 4: overlap risk with other skills is minimal, not minor.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

every-app/open-seo

Path

.agents/skills/observability-triage/SKILL.md

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.