CtrlK
BlogDocsLog inGet started
Tessl Logo

style-guide

Use when: authoring, modifying, or reviewing Primer React components, hooks, utilities, or component APIs. Covers applying contributor-docs/style.md, including the spectrum of abstraction, presentational components, behavior hooks, config components, accessibility primitives, props, hooks, SSR, and CSS conventions.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/style-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 concise, well-structured overview that correctly defers detail to the external style-guide file, fitting a simple single-purpose instruction skill. Its main weakness is actionability: beyond 'read style.md', the guidance to 'apply the relevant principles' is abstract without concrete examples or a way to verify the principles were applied.

Suggestions

Add one or two concrete examples of applying a style-guide principle (e.g., a before/after props or component-structure snippet) so 'apply the relevant principles' becomes executable rather than abstract.

Tighten the duplicated trigger-verb phrasing between the opening sentence and the third paragraph to remove minor redundancy.

Include a brief verification cue (e.g., 'confirm the change aligns with style.md before finalizing, or note the deviation') to make the workflow's apply-and-check loop explicit.

DimensionReasoningScore

Conciseness

The body is lean (~9 lines) and assumes Claude's competence without explaining Primer React or hook concepts, but the trigger verbs ('authoring, modifying, or reviewing') and the 'apply the relevant style-guide principles' idea are each restated across paragraphs, leaving minor redundancy a 5 would not have.

4 / 5

Actionability

It gives one concrete, executable step ('read `contributor-docs/style.md`') but the rest ('apply the guidelines that are relevant', 'explicitly apply the relevant style-guide principles', 'call out the reason') is high-level direction without specifics on how to apply or surface the principles, leaving the guidance incomplete.

3 / 5

Workflow Clarity

The sequence (read the style guide -> apply relevant guidelines -> note intentional deviations) is clear and appropriate for a simple, non-destructive instruction skill, with only minor gaps since no explicit verification checkpoint is needed here.

4 / 5

Progressive Disclosure

The SKILL.md is a compact overview that keeps all detail in the external one-level-deep reference `contributor-docs/style.md`, which is clearly signaled; for a sub-50-line skill with no bundle files, this is appropriately organized and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

87%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 explicitly pairs a 'Use when' trigger with a concrete 'what' and a comprehensive coverage list tied to a specific style-guide file. The only minor weakness is that the action verbs are fairly generic despite the domain-specific topic enumeration.

DimensionReasoningScore

Specificity

The description names the domain (Primer React components, hooks, utilities, component APIs) and enumerates many concrete coverage areas (presentational components, behavior hooks, config components, accessibility primitives, props, SSR, CSS conventions), giving comprehensive coverage, but the verbs 'authoring, modifying, or reviewing' are somewhat generic relative to the 5-anchor's distinct multi-action examples.

4 / 5

Completeness

It explicitly answers both 'what' (covers applying contributor-docs/style.md, including the enumerated spectrum of abstractions and conventions) and 'when' (the concrete 'Use when:' trigger phrases), matching the 5 anchor.

5 / 5

Trigger Term Quality

The 'Use when:' clause supplies natural phrases a Primer React contributor would say ('authoring, modifying, or reviewing Primer React components, hooks, utilities, or component APIs'), giving good keyword coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Triggers are tightly scoped to the Primer React ecosystem and a specific style.md file, giving a clear niche with minimal overlap risk against unrelated skills.

5 / 5

Total

18

/

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
primer/react
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.