CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contributing

Use when contributing to the Cloudflare Docs repository — writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs, or learning how to contribute.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

This is an exemplary router skill: lean, repo-specific, fully actionable, with genuine progressive disclosure into a real, verified reference bundle. Its main gaps are minor — a slightly repetitive opening and a missing validate-fail feedback loop in the finish checklist.

DimensionReasoningScore

Conciseness

The body is efficient and teaches nothing Claude already knows — every section carries repo-specific value (branch off `production` not `main`, CI-vs-local command sets, redirect validator). The opening, however, repeats the 'references are the source of truth' idea across three consecutive statements ('It does not contain the detail itself...', 'Do not guess at conventions...', 'Canonical references override conflicting local patterns...'), which is minor over-explanation that could be trimmed — anchor 4, not 5.

4 / 5

Actionability

Guidance is fully concrete and executable: exact git procedure (`git fetch origin` then branch from `origin/production`), a task-to-reference table with real paths, and copy-paste commands (`pnpm run check`, `pnpm run build`, `pnpm run format`, `pnpm exec tsm bin/validate-redirects.ts`) with environment-specific variants. As an instruction/index skill its guidance is specific and actionable throughout, matching the 5 anchor.

5 / 5

Workflow Clarity

The process is clearly sequenced (gather context → task index → validate before you finish) with an explicit summary of the authoring workflow and a mandatory validation section with matching commands. It falls short of 5 because there is no error-recovery feedback loop (what to do when `pnpm run check` fails — fix and re-run) and no explicit completion checklist; the validation checkpoints themselves are present, so it is above anchor 3.

4 / 5

Progressive Disclosure

Textbook progressive disclosure: a ~70-line router SKILL.md with a task-index table pointing to one-level-deep references, all of which exist as real, substantive files in the bundle (6 files, 751 lines of detail kept out of context). External `.agents/` references are explicitly distinguished ('Paths are relative to this skill directory unless prefixed with `.agents/`'), and writing-docs.md ties the references into a single workflow — matching the 5 anchor of a clear overview with well-signaled one-level-deep references.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong description in the recommended 'actions + Use when' format: concrete capabilities, explicit trigger guidance, and a clearly bounded niche. The only improvement space is adding a few more natural synonyms (PR review, editing) for wider trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete, domain-specific actions — 'writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs' — comprehensively covering the contribution workflow. This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); the only mildly generic item is 'learning how to contribute', which does not pull it to 4 since the action list itself is complete.

5 / 5

Completeness

It explicitly answers both questions: 'what' via the action list (writing/editing pages, choosing types/components, changelog entries, reviewing docs) and 'when' via the explicit trigger clause 'Use when contributing to the Cloudflare Docs repository... or learning how to contribute'. This mirrors the 5 anchor's structure of concrete actions plus explicit 'Use when' triggers; not 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Natural trigger phrases are present and would be said by users: 'contributing to the Cloudflare Docs repository', 'documentation pages', 'changelog entries', 'reviewing docs', 'content types', 'components'. A few common variations are missing (e.g., 'pull request'/'PR', 'edit a page', 'docs formatting'), which fits anchor 4 (good coverage, a few natural terms missing) rather than 5's synonym-and-extension completeness.

4 / 5

Distinctiveness Conflict Risk

The 'Cloudflare Docs repository' qualifier gives it a clear niche with distinct, repo-specific triggers (pcx_content_type decisions, changelog entries), minimizing conflict with generic writing or documentation skills. It would not fire for non-Cloudflare docs work, matching anchor 5; score 4 would require minor overlap risk that is not evident.

5 / 5

Total

19

/

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

cloudflare/cloudflare-docs

Path

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