CtrlK
BlogDocsLog inGet started
Tessl Logo

code-style-patterns

Apply community code styles from shadcn, sindresorhus, or ahmadawais. Use when the user names those styles or wants a community pattern applied to code. It does not design plugins (that's `plugin-craft`).

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/tooling/skills/code-style-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured with exemplary progressive disclosure and a clear per-style workflow, but it leans on repeated directional prose instead of executable guidance and restates some broadly known principles. Tightening the repeated blocks and adding concrete adaptation examples would raise the efficiency and actionability scores.

Suggestions

Collapse the three near-identical 'Follow the How To Use This Style' blocks into one shared workflow referenced once, to remove repetition and improve token efficiency.

Add one concrete before/after adaptation snippet per style (or a pointer to one in the reference) so the 'Adapt patterns responsibly' step becomes executable rather than directional.

Trim 'Key principles' bullets that restate common knowledge (e.g. narrow APIs, documentation hygiene) to the few that are distinctive to each developer.

DimensionReasoningScore

Conciseness

The body is organized and mostly assumes Claude's intelligence, but the near-identical four-step 'Follow the How To Use' block is repeated three times and several 'Key principles' restate widely known ideas (narrow APIs, TypeScript, doc hygiene); it could be tightened without loss.

3 / 5

Actionability

Guidance is directional ('Identify relevant repos', 'clone to /tmp', 'Adapt patterns responsibly') with concrete file-loading targets in the Modes table, but lacks executable specifics or concrete examples for adapting patterns — incomplete rather than vague, matching anchor 3.

3 / 5

Workflow Clarity

A clear Identify -> Inspect -> Adapt -> Return sequence is given per style, the Modes table maps intent to files, and the Quality Checklist plus end-of-session 'Did this help?' loop serve as checkpoints; not a 5 because the 'Adapt' step is subjective with no explicit verification.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with three one-level-deep references (shadcn.md, sindresorhus.md, ahmadawais.md — all present on disk), each signaled by bold 'Always load...' callouts, and the Modes table maps every mode to a file, matching the anchor-5 navigation pattern.

5 / 5

Total

15

/

20

Passed

Description

82%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 strong: it states a concrete action, names explicit triggers tied to specific developers, covers both what and when, and disambiguates from a sibling skill. Its only soft spot is a single broad verb, leaving specificity slightly below the top anchor.

Suggestions

Expand the verb set beyond 'Apply' to concrete actions like 'refactor, adapt, or scaffold code toward' a named style to lift specificity toward anchor 4-5.

Add one or two natural synonyms users might say (e.g. 'coding conventions', 'community style guide') to round out trigger term coverage.

DimensionReasoningScore

Specificity

It names the domain (three specific developers) and a concrete action ("Apply community code styles"), but offers only one main verb so coverage is not comprehensive — matching anchor 3, and not 4 since the action set is minimal.

3 / 5

Completeness

It explicitly answers both what ("Apply community code styles from...") and when ("Use when the user names those styles or wants a community pattern applied to code") with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Natural terms a user would say are present ("shadcn, sindresorhus, or ahmadawais", "community pattern applied to code") giving good keyword coverage; not a 5 because broader synonyms or file-style phrasing variants are missing.

4 / 5

Distinctiveness Conflict Risk

It names three specific developers and draws an explicit boundary ("It does not design plugins (that's plugin-craft)"), giving a clear niche with minimal conflict risk.

5 / 5

Total

17

/

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
saif-shines/devex-kit
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.