CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

network-traffic-annotations

Guide for writing and managing Network Traffic Annotations in Chromium. Use this skill when adding or updating code that makes network requests.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is highly actionable with a complete template, exact commands, and concrete field guidance, organized into clear sequenced workflows with validation checkpoints. Minor conciseness padding and a numbering/structure glitch in the auditor section keep it just short of the top band.

Suggestions

Fix the 'Running the Auditor' subsection numbering (it starts at '### 2. Build Chrome' with no step 1) and reconcile it with the 7-step Authoring Process above to avoid a disjointed sequence.

Remove duplicated emphasis about running auditor.py (it appears as step 6 of Authoring Process and again in the 'Running the Auditor' section) and trim instructional padding like 'Explain to the user what you're about to do, and why'.

Correct the typo 'If any of these are tru' to 'true'.

DimensionReasoningScore

Conciseness

The body is largely lean field definitions, a template, and exact commands without explaining concepts Claude already knows, though some instructional prose ('Explain to the user what you're about to do, and why') and duplicated auditor-run emphasis could be trimmed.

4 / 5

Actionability

It provides a copy-paste-ready cpp template, concrete field definitions with enum values, exact auditor and build commands, and precise file paths for policies and platforms, fully covering the common cases.

5 / 5

Workflow Clarity

The Authoring Process is a clear 7-step sequenced checklist with explicit verification checkpoints and the auditor acts as a validation feedback loop, but the 'Running the Auditor' subsection numbering starts at 2 and is structurally disconnected from the prior 7-step list, a minor gap.

4 / 5

Progressive Disclosure

The single file is well-organized with clear section headers and coherent inline content for a single-purpose skill, with no bundle files to navigate; the sizable field-reference block could arguably be split out, keeping it just below the top anchor.

4 / 5

Total

17

/

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.

The description clearly states what the skill does and when to use it with a distinct, well-scoped niche. It is held back from the top band by limited action specificity and a single, slightly broad trigger phrase.

Suggestions

Expand the action list beyond 'writing and managing' to concrete verbs like 'adding, updating, and auditing Network Traffic Annotations' to lift specificity.

Add the natural trigger term 'traffic annotations' explicitly in the 'when' clause (e.g., 'Use when adding, updating, or reviewing network traffic annotations') so the trigger aligns with what users actually say.

Tighten the trigger to reference annotations rather than generic network requests to reduce overlap with general networking skills.

DimensionReasoningScore

Specificity

Names the domain ('Network Traffic Annotations in Chromium') and two concrete actions ('writing and managing'), but 'managing' is generic and coverage is not comprehensive, matching the anchor that names the domain with 1-2 concrete actions.

3 / 5

Completeness

It explicitly answers both 'what' (guide for writing and managing Network Traffic Annotations) and 'when' (adding or updating code that makes network requests), but the single trigger phrase is less comprehensive than the multi-trigger anchor at 5.

4 / 5

Trigger Term Quality

The trigger clause 'Use this skill when adding or updating code that makes network requests' uses natural phrasing a user might say, with good keyword coverage, though the more specific term 'traffic annotations' as a trigger and common variations are absent.

4 / 5

Distinctiveness Conflict Risk

'Network Traffic Annotations in Chromium' is a clear, distinct niche with minimal conflict risk, but the 'code that makes network requests' trigger is broad enough to create minor overlap with general networking skills rather than the minimal risk of a 5.

4 / 5

Total

15

/

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/network-traffic-annotations/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.