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.

80

Quality

100%

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

100%

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

The body is lean, executable, and well-structured, with concrete code, explicit verification checkpoints, and a feedback loop for when events fail to fire. It avoids over-explaining basics and keeps the workflow tight.

DimensionReasoningScore

Conciseness

Lean body that assumes competence — no explanation of what logging or unified logging is — with concise code and tight guideline bullets; every section earns its place without padding.

3 / 3

Actionability

Provides copy-paste-ready Swift Logger code and concrete executable commands such as 'log stream --style compact --predicate' and './script/build_and_run.sh --telemetry', with specific subsystem/category examples.

3 / 3

Workflow Clarity

A clear 5-step workflow with an explicit verification step (step 4) and a feedback loop in step 5 ('If it does not fire, move the log closer ... and rerun'), reinforced by a Verification Checklist.

3 / 3

Progressive Disclosure

A single-purpose skill with no bundle files and well-organized sections (Quick Start, Core Guidelines, Minimal Logger Pattern, Workflow, Verification Checklist, Guardrails); per the simple-skills note, clear organization without external references supports a top score.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, third-person description that states concrete capabilities and an explicit 'Use when' trigger with natural vocabulary. It clearly delineates its macOS telemetry niche and avoids vague fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running' — plus specific instrumentation targets like wiring Logger and adding log points for window/sidebar/menu-bar actions.

3 / 3

Completeness

Explicitly answers both what (add and verify telemetry) and when via a clear 'Use when wiring ... adding log points ... reading runtime logs ... or confirming that expected events fire' trigger clause.

3 / 3

Trigger Term Quality

Includes natural terms a user would say — 'wiring Logger / os.Logger', 'reading runtime logs from Console or log stream', 'confirming that expected events fire' — covering the real vocabulary of the task.

3 / 3

Distinctiveness Conflict Risk

The macOS-specific logging niche with distinct triggers (Console, log stream, os.Logger, build/run verification) makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.