CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

experimental-read-code-coverage-metrics

Retrieves and analyzes Chromium per-CL code coverage data from the Findit API. Records per-CL coverage metrics for all modified source files and extracts unexecuted code lines.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./agents/skills/experimental-read-code-coverage-metrics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 single-purpose skill with executable commands, explicit inputs, a verification step, and a concrete output example. The main gaps are the unspecified parse_gerrit_url.py output format, the lack of an error-recovery loop, and minor redundancy in the intro paragraph.

Suggestions

Specify the output format of parse_gerrit_url.py (e.g. whether it prints JSON or key=value pairs) so the extracted host/project/change/patchset values can be plugged into the fetch command unambiguously.

Extend the error-handling note into a feedback loop: after checking stderr, state what to do (e.g. re-run with --auth-token on auth errors, or report the API error to the parent agent) instead of stopping at 'check stderr'.

Trim the opening paragraph, which duplicates the frontmatter description, and note in the fetch command that --files is omitted when target_files is not supplied.

DimensionReasoningScore

Conciseness

The body is efficient with command blocks, a concrete input list, and a compact artifact example; the only trimmable padding is the opening paragraph, which restates the frontmatter description, keeping it just below the lean 5 anchor.

4 / 5

Actionability

Provides executable commands ('vpython3 tools/code_coverage/parse_gerrit_url.py <cl_url>' and the fully flagged fetch_coverage_metrics.py invocation) plus a concrete output artifact example, but the output format of parse_gerrit_url.py is never specified, leaving a minor gap to copy-paste readiness.

4 / 5

Workflow Clarity

Clear sequence (extract CL details, run fetch, verify artifact) with an explicit verification step and an error-handling note about non-zero exits, but no recovery loop after checking stderr (e.g. retry, abort, or report guidance), so it stops short of the 5 anchor.

4 / 5

Progressive Disclosure

Well-organized sections (When to Use, Inputs, Workflow, Output, Important Considerations) with no bundle files and nothing that clearly belongs in a separate file; at ~82 lines with an inline sample artifact JSON it exceeds the under-50-line simple-skill exception, so it sits at the good-structure 4 anchor.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, distinctive description with concrete actions and good domain keywords, but it omits any 'when to use' trigger guidance, which caps its completeness. Adding an explicit 'Use when...' clause with natural trigger phrases would raise both completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when establishing baseline coverage for a Chromium CL, verifying coverage after re-running try jobs, or when the user mentions code coverage or uncovered lines.'

Include common synonyms users would naturally say, such as 'test coverage', 'uncovered lines', and 'coverage report', to broaden trigger-term coverage.

Replace or concretize the generic verb 'analyzes' with a specific action (e.g. 'summarizes absolute and incremental coverage percentages') to close the specificity gap.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Records per-CL coverage metrics for all modified source files', 'extracts unexecuted code lines'), though 'analyzes' is semi-generic, leaving minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

The 'what' is clearly stated (retrieves, records, extracts coverage data) but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('code coverage data', 'coverage metrics', 'unexecuted code lines', 'per-CL'), but missing common synonyms like 'test coverage' or 'uncovered lines', so it falls short of the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

'Chromium per-CL code coverage data from the Findit API' carves out a clear niche with distinct triggers and minimal conflict risk with any other plausible skill.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

chromium/chromium

Path

agents/skills/experimental-read-code-coverage-metrics/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.