CtrlK
BlogDocsLog inGet started
Tessl Logo

telemetry

Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running. Use when wiring `Logger` / `os.Logger`, adding log points for window/sidebar/menu-bar actions, reading runtime logs from Console or `log stream`, or confirming that expected events fire after a local run.

75

Quality

92%

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

The canonical home for this skill is telemetry in openai/plugins

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 well-structured, actionable skill body with executable code, concrete log-streaming commands, and a clear verify-then-tighten workflow. The only weaknesses are mildly editorial quick-start prose and the lack of any external reference split that would push progressive disclosure higher.

Suggestions

Tighten the Quick Start paragraph by dropping the 'logging landfill' editorial phrasing and avoiding overlap with the Core Guidelines bullets.

Consider moving the detailed `log stream` predicate examples and the category-name list into a short references file to deepen progressive disclosure and trim the inline body.

DimensionReasoningScore

Conciseness

Mostly lean with tight bulleted Core Guidelines and a focused code example, but the Quick Start prose ('without turning the codebase into a logging landfill') is mildly editorial and slightly redundant with the Core Guidelines section.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Swift Logger code plus concrete `log stream` commands with example subsystem/category predicates, covering the common build/run/verify cases.

5 / 5

Workflow Clarity

The 5-step Workflow has a clear sequence with an explicit verification checkpoint (step 4: read logs and verify the event fired) and a feedback loop (step 5: 'If it does not fire, move the log closer to the suspected control path and rerun'), reinforced by a Verification Checklist.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Quick Start, Core Guidelines, Minimal Logger Pattern, Workflow, Verification Checklist, Guardrails) and self-contained with no bundle files present; at ~80 lines it exceeds the 50-line simple-skill auto-5 exception, so it sits at good-but-not-perfect.

4 / 5

Total

18

/

20

Passed

Description

96%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 strong, specific description that clearly states its capabilities and provides concrete trigger guidance covering the macOS unified-logging domain. The only soft spot is minor overlap risk with adjacent debug/observability skills, keeping distinctiveness just below a perfect score.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add lightweight runtime telemetry and debug instrumentation', 'verify those events after building and running' — alongside concrete trigger actions like wiring Logger, adding log points, and reading runtime logs, giving comprehensive coverage of the macOS app telemetry domain.

5 / 5

Completeness

Explicitly answers 'what' (add telemetry + verify events after build/run) and 'when' via a concrete 'Use when wiring Logger / os.Logger, adding log points..., reading runtime logs from Console or log stream, or confirming that expected events fire after a local run' clause.

5 / 5

Trigger Term Quality

Includes both natural and technical trigger terms users would say — `Logger` / `os.Logger` synonyms, Console, `log stream`, telemetry, log points, window/sidebar/menu-bar — with comprehensive coverage of the domain's vocabulary.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche scoped to macOS app runtime telemetry via unified logging, but 'telemetry' and 'debug instrumentation' carry minor overlap risk with general observability or build-run-debug skills.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
robinebers/openusage
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.