CtrlK
BlogDocsLog inGet started
Tessl Logo

google-devdocs-style

Write and review developer documentation in Google Developer Documentation Style. Use when drafting guides, API reference, READMEs, procedures, or release notes, not UI strings, commit messages, PR bodies, or code comments.

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 lean, highly actionable prescriptive skill body with a clear drafting workflow, validation checklists, and a well-structured one-level-deep reference layout. Only minor conciseness trim opportunities remain.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no basic-concept padding, but rhetorical framing like "Ordered by how often they get broken" and "Read this before the style rules, because it constrains all of them" are minor instances of over-explanation that could be trimmed.

4 / 5

Actionability

Concrete before/after examples ("Write 'To delete the document, click **Delete**', not 'Click **Delete** to delete the document'") and specific banned-word lists give fully actionable, case-covering guidance appropriate to an instruction-only skill.

5 / 5

Workflow Clarity

The "Draft or revise" sequence, the "Before you finish" checklist, and the line-by-line fidelity pass ("Is there a single sentence you wrote that the source does not support? Delete it.") provide a clear sequence with explicit validation and a feedback loop.

5 / 5

Progressive Disclosure

The "Look it up" section signals one-level-deep references (rules.md, word-list.md, official-pages.md), each with when-to-read guidance, and all three referenced files exist in references/.

5 / 5

Total

19

/

20

Passed

Description

78%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, well-scoped description that clearly states both capability and trigger conditions with useful negative boundaries. The main weakness is specificity, since only two verbs (write, review) describe the actions.

Suggestions

Add one or two more concrete actions (e.g., "audit", "rewrite") to lift specificity beyond the two-action anchor.

Include a natural synonym or file-type trigger (e.g., "developer guides" or ".md READMEs") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Write and review developer documentation" names the domain and two concrete actions (write, review), matching the 1-2-concrete-actions anchor; it does not list several specific actions that would warrant a 4.

3 / 5

Completeness

It explicitly answers what ("Write and review developer documentation in Google Developer Documentation Style") and when ("Use when drafting guides, API reference, READMEs, procedures, or release notes") with concrete trigger phrases and exclusions.

5 / 5

Trigger Term Quality

"guides, API reference, READMEs, procedures, or release notes" plus the negative triggers ("not UI strings, commit messages, PR bodies, or code comments") give good natural keyword coverage, though synonyms and file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

The named Google Developer Documentation Style niche and explicit exclusions (not commit messages, PR bodies, code comments) make it mostly distinct, but it still has minor overlap risk with closely related technical-writing or general documentation skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
EpicenterHQ/epicenter
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.