CtrlK
BlogDocsLog inGet started
Tessl Logo

api-ref-tone

Tone of voice guidance for Highcharts API reference doclets - covering sentence structure, vocabulary, and phrasing patterns for public-facing TS doclets.

67

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 a tight, highly actionable tone-of-voice reference with concrete templates and good/bad examples, well-sectioned and scoped; its only gap is that all content lives in one file with no progressive split into bundle references.

DimensionReasoningScore

Conciseness

The body is a lean reference that assumes Claude's competence — pattern tables, vocabulary lists, and wrong/right pairs with no padding or explanation of basic concepts, so every token earns its place.

5 / 5

Actionability

Concrete copy-paste templates ('The <thing> of the <owner>.', 'Whether <condition>.', 'Fires when <condition>.') plus explicit good/bad example pairs give directly applicable, specific guidance for the common member types.

5 / 5

Workflow Clarity

This is a single-purpose style skill whose single action is unambiguous, and the 'Multi-sentence structure' section provides an explicit sequence (summary first, then edge cases, defaults, cross-references); no destructive/batch validation cap applies.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one well-signaled external pointer ('Read ts/DOCLETS.md for tag syntax, formatting rules, and tooling') and explicit scope separation, but it is a single ~90-line monolithic file rather than content split across bundle files.

4 / 5

Total

19

/

20

Passed

Description

65%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 specific and occupies a clear, low-conflict niche, but it lacks an explicit 'when to use' trigger clause and misses the most natural developer terms (JSDoc/TSDoc), capping completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing JSDoc/TSDoc doclets on public-facing Highcharts TypeScript members.'

Include the natural developer terms 'JSDoc' and 'TSDoc' in the description so it matches what users actually say.

Reframe the coverage list as concrete actions (e.g. 'Write and review sentence structure, vocabulary, and phrasing') to lift specificity above 3.

DimensionReasoningScore

Specificity

Names the domain ('Highcharts API reference doclets') and three concrete coverage facets ('sentence structure, vocabulary, and phrasing patterns'), but these are coverage areas rather than verb-actions, so it sits at the 'names domain + a few specifics' level rather than a comprehensive action list.

3 / 5

Completeness

It clearly states what the skill does ('Tone of voice guidance ... covering sentence structure, vocabulary, and phrasing patterns') but includes no 'Use when...' clause or equivalent trigger guidance, so per the cap, completeness cannot exceed 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('tone of voice', 'Highcharts API reference', 'doclets', 'TS doclets', 'sentence structure', 'vocabulary'), but it omits the developer-natural terms 'JSDoc' and 'TSDoc' that users would most likely say.

4 / 5

Distinctiveness Conflict Risk

The niche is extremely specific — tone of voice for Highcharts public-facing TS API doclets — so it is clearly distinguishable from other skills with minimal conflict risk.

5 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
highcharts/highcharts
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.