CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-telemetry

Enforce session-cost telemetry and execution-metadata reporting. Use when explicitly invoking get_session_cost, reporting token/cost usage, applying telemetry or cost guidance during a workflow handoff, or writing artifacts/session-cost.md at a workflow terminal state.

Quality

80%

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 ./.agents/skills/common/common-telemetry/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 actionable and well-sequenced, with exact field names, provenance semantics, and a ready-to-use output table. Its main weakness is redundancy — the same accounting-boundary rules are repeated across §2, Anti-Patterns, and Canonical response anchors — which inflates token cost without adding guidance.

Suggestions

Consolidate the duplicated rules: merge 'Accounting Boundaries & Lineage Semantics', 'Anti-Patterns', and 'Canonical response anchors' into one authoritative section so each rule appears once.

Remove the content-free trailing bullet ('- Telemetry & Cost Reporting') from the anchors section.

Add a brief example get_session_cost call payload (with workflow, slug, outcome fields) to make the tool invocation fully copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient and imperative, but the same rules are stated three times: 'Missing ≠ Zero' (§2) is restated as 'No zero-coercion of missing metrics' (Anti-Patterns), 'Discovery Lifecycle Distinctness' as 'No conflating catalog discovery with usage', and the §4 table rules reappear in 'Canonical response anchors' — which ends with a content-free bullet ('- Telemetry & Cost Reporting'). Not 4 because the triple repetition is a clear trimming opportunity; not 2 because there is no padding of concepts Claude already knows.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: named tool call with an exact field list ('workflow', 'model', token counts, 'slug', 'outcome'), explicit costSource semantics, and a copy-paste-ready Markdown table template. Not 5 because no example tool-call payload is shown and phrases like 'other runtime cost fields when available' leave gaps; not 3 because the guidance goes well beyond high-level hints.

4 / 5

Workflow Clarity

A clear 5-step numbered sequence with conditional handling ('If token counts are unavailable, report MCP-observed telemetry... never fabricate') and an explicit fallback when the host does not expose the helper. Not 5 because there is no verification checkpoint confirming the artifact was appended or the call succeeded; not 3 because missing-data checkpoints and error branches are explicitly present and the operation is non-destructive.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and none are referenced, yet the ~65-line body is self-contained and sectioned ('Finalizing a Workflow', 'Accounting Boundaries', 'Host Runtime Contract', 'Telemetry Format', 'Anti-Patterns'). Not 5 because of minor organization gaps: stray top-level bullets, inconsistent blank-line separation, and the 'Canonical response anchors' section dangling below 'Anti-Patterns' without a clear role.

4 / 5

Total

15

/

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 pairs a concrete capability statement with an explicit 'Use when...' clause containing specific tool names, artifact paths, and natural trigger phrases. Its only weakness is keyword coverage that misses a few common synonyms users might say.

Suggestions

Add one or two natural synonyms such as 'spend' or 'usage summary' to the trigger terms to broaden when-coverage.

Consider mentioning the provenance/boundary reporting rules (e.g., 'reporting cost provenance as host, agent-estimate, or unavailable') to more fully enumerate the skill's capabilities.

DimensionReasoningScore

Specificity

Names the domain ('session-cost telemetry and execution-metadata reporting') and several concrete actions anchored to real artifacts — 'explicitly invoking get_session_cost', 'reporting token/cost usage', 'writing artifacts/session-cost.md at a workflow terminal state'. Falls short of 5 because coverage is not comprehensive (the boundary/lineage semantics in the body are absent) and above 3 because it lists more than 1-2 specific actions.

4 / 5

Completeness

Explicitly answers both: 'what' ('Enforce session-cost telemetry and execution-metadata reporting') and 'when' with a concrete trigger clause ('Use when explicitly invoking get_session_cost, reporting token/cost usage, applying telemetry or cost guidance during a workflow handoff, or writing artifacts/session-cost.md at a workflow terminal state'). Matches the score-5 anchor pattern of concrete what + explicit when.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'token/cost usage', 'session cost', 'cost report', plus the concrete tool name 'get_session_cost' and artifact path. Not 5 because common user synonyms like 'spend', 'usage summary', or 'budget' are missing; not 3 because the terms present are phrases a user would naturally say when needing this skill.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — session-cost telemetry, the specific MCP tool 'get_session_cost', and the 'artifacts/session-cost.md' artifact path make it unlikely to fire for unrelated skills. Minimal conflict risk.

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-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.