CtrlK
BlogDocsLog inGet started
Tessl Logo

telemetry

Add and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions.

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured, highly actionable telemetry skill with executable code, concrete log-inspection commands, and a clear verify-then-iterate workflow. The main weakness is rule repetition across the three reinforcement sections that could be consolidated.

Suggestions

State the noisy-debug-log guidance once (Core Guidelines or Guardrails) and drop the duplicate phrasing in the Verification Checklist to reduce repetition.

Merge the "do not log secrets" rule with the checklist's "No sensitive payloads" line so the privacy constraint lives in a single place.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no concept re-explanation) and is concrete throughout, but the noisy-debug-log and don't-log-secrets guidance is repeated across Core Guidelines, Guardrails, and the Verification Checklist and could be tightened into one statement.

2 / 3

Actionability

It provides a complete, executable Swift Logger snippet and copy-paste `log stream --predicate` commands plus build/run flags, so guidance is concrete and ready to run rather than pseudocode.

3 / 3

Workflow Clarity

The five-step Workflow is clearly sequenced with an explicit "verify the event fired" checkpoint, a feedback loop ("If it does not fire, move the log closer... and rerun"), and a verification checklist.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is coherently split into Quick Start, guidelines, a code pattern, Workflow, checklist, and Guardrails with easy section navigation.

3 / 3

Total

11

/

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 strong, third-person description with concrete actions, an explicit Use-when trigger, natural domain keywords, and a clearly bounded niche. No specificity or voice penalty applies.

DimensionReasoningScore

Specificity

"Add and verify lightweight macOS runtime telemetry" plus "wiring Logger events or inspecting logs" names several concrete actions (add, verify, wire, inspect) rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers what ("Add and verify... telemetry") and when via an explicit "Use when..." trigger clause, so both halves are present rather than implied.

3 / 3

Trigger Term Quality

Natural terms a developer would say are well covered — "telemetry", "Logger events", "logs", and the UI surfaces "windows, sidebars, menus, and actions" — beyond a single jargon phrase.

3 / 3

Distinctiveness Conflict Risk

The macOS runtime-telemetry niche with Logger/log triggers is clearly bounded and even defers crash analysis to a separate "build-run-debug" skill, so it is unlikely to fire for the wrong skill.

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
openai/plugins
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.