CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

telemetry

Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of mobile-app usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/mobile-apps/skills/telemetry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 admirably lean and uses the correct delegation pattern — a pointer to a single, clearly signaled workflow file — but the delegation target (telemetry-workflow.md) is missing from the skill bundle, leaving the skill with no verifiable task instructions, checkpoints, or overview content. What is written is clear and executable, yet the substance of the skill is entirely unverifiable.

Suggestions

Add the referenced telemetry-workflow.md to the skill bundle (the ${PLUGIN_ROOT}/skills/telemetry/ path resolves to a sibling of SKILL.md, but no such file exists there) so the delegated workflow is actually present.

Inline a brief overview of the workflow's key steps in SKILL.md so the skill remains minimally useful and reviewable even if the bundled file fails to load.

Include an explicit validation checkpoint in the workflow (e.g., re-checking and reporting the telemetry state after toggling) so the on/off/status operations have a feedback loop.

DimensionReasoningScore

Conciseness

The entire body is two statements: "Run `node "${PLUGIN_ROOT}/scripts/check-version.js"`" and a pointer to the bundled workflow file. There is zero padding and no explanation of concepts Claude already knows — every token earns its place. Not 4: nothing could be trimmed without losing function.

5 / 5

Actionability

Quotes: "Run `node "${PLUGIN_ROOT}/scripts/check-version.js"`" (concrete, executable) and "Read and follow all steps defined in that bundled file" with an exact path. Concrete guidance is present, but the core task instructions — how to actually enable/disable telemetry — are entirely delegated to telemetry-workflow.md, which does not exist in the skill bundle, so key details are missing. Not 4 because the gap is the entire substantive procedure, not a minor one; not 2 because the body does provide exact executable commands and paths rather than high-level hints.

3 / 5

Workflow Clarity

The body's own sequence is coherent — run the version check, show its output if any, then read and follow the workflow file — but the actual task workflow and any validation checkpoints live in telemetry-workflow.md, which is absent from the bundle (no sibling file, no references/ or scripts/ directories). This matches anchor 3 (sequence present but checkpoints missing or implicit): not 4 because no checkpoints or task steps are visible anywhere, not 2 because what is written is specific and correctly ordered.

3 / 5

Progressive Disclosure

Quotes: "**Workflow: [telemetry-workflow.md](${PLUGIN_ROOT}/skills/telemetry/telemetry-workflow.md)**" — a clearly signaled, one-level-deep reference, which is the right pattern. However, scoring against the actual bundle structure: the referenced file is not present (the path resolves to a sibling of SKILL.md, and no such file exists in the skill directory), and the body provides no inline overview of what the workflow contains. Not 4 because the disclosure chain cannot be verified against the bundle; not 2 because the reference is clearly signaled, not buried, and no content is wrongly inlined.

3 / 5

Total

14

/

20

Passed

Description

87%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 is strong: it explicitly states what the skill does, when to use it, and includes a concrete quoted trigger list with good synonym coverage. The only weakness is asymmetric trigger coverage — the disable direction has four variants while the enable direction has only one, omitting natural phrases like 'turn on telemetry'.

DimensionReasoningScore

Specificity

Quotes: "enable, disable, turn on or off, opt out of, opt in to, or check the status of mobile-app usage data" — several concrete actions (enable, disable, status check) are named, but "turn on or off" and "opt in to" are synonyms of enable/disable rather than additional capabilities. It fits anchor 4 (several specific actions, minor gaps) better than 5 because the distinct action set is only three, and better than 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Quotes: "Use this skill when the user wants to enable, disable ... check the status of mobile-app usage data" plus an explicit "Triggers:" list of concrete trigger phrases. This explicitly answers both what (enable/disable/opt/status of mobile-app usage data) and when (quoted trigger phrases), exactly matching the anchor-5 example; not 4, because the 'when' is fully explicit rather than merely serviceable.

5 / 5

Trigger Term Quality

Quotes: "Triggers: 'disable telemetry', 'turn off telemetry', 'opt out of telemetry', 'stop collecting usage data', 'enable telemetry', 'telemetry status'" — six natural phrases users would actually say, with strong synonym coverage on the disable side. It falls between anchors 4 and 5: 'turn on telemetry' and 'opt in to telemetry' are natural enable-side variants that are missing, so coverage is good but not comprehensive — hence 4, not 5; not 3 because far more than 'some relevant keywords' are present.

4 / 5

Distinctiveness Conflict Risk

Quotes: "mobile-app usage data" and the distinct triggers "disable telemetry" / "telemetry status" — a clear niche with quoted, unambiguous triggers. Minimal conflict risk with other skills; not 4 because the mobile-app qualifier and specific telemetry triggers leave essentially no overlap with generic settings or analytics skills.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

microsoft/power-platform-skills

Path

plugins/mobile-apps/skills/telemetry/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.