CtrlK
BlogDocsLog inGet started
Tessl Logo

cc-skill-coding-standards

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

47

Quality

50%

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 ./skills/cc-skill-coding-standards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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 well-structured as a lean overview that cleanly delegates to a single, well-organized reference file, but it is essentially a redirect: it offers little actionable or workflow guidance on its own and its 'When to Use' framing is circular.

Suggestions

Replace the circular 'When to Use' line with concrete trigger conditions (e.g., 'Use when writing or reviewing TypeScript/React/Node.js code') rather than restating the overview.

Add one or two concrete, actionable checks or conventions inline so the skill is usable without immediately loading the reference.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation; only the opening line lightly restates the frontmatter, keeping it at anchor 4 ('Efficient; minor instances of over-explanation that could be trimmed') rather than 5.

4 / 5

Actionability

The body itself provides no executable guidance or steps — only a pointer to the reference — and 'applicable to execute the workflow ... described in the overview' is circular, matching anchor 2 ('Minimal concrete guidance; high-level hints but missing the specific steps to execute').

2 / 5

Workflow Clarity

The single action ('Read the detailed guide before executing') is clearly stated with load guidance, but the circular 'When to Use' wording and absence of any validation checkpoint keep it just below a clean 5, fitting anchor 4 ('Clear sequence with most checkpoints present; minor gaps').

4 / 5

Progressive Disclosure

The body is a clear overview pointing one level deep to references/detailed-guide.md (verified to exist, 523 lines, well-sectioned, no nested references), matching anchor 5 ('Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

15

/

20

Passed

Description

42%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 identifies the domain and tech stack but lacks concrete actions, explicit 'Use when' triggers, and a distinct niche. It reads as a broad knowledge-area label rather than a scoped, triggerable skill.

Suggestions

Add a 'Use when...' clause with concrete task triggers (e.g., 'Use when reviewing, refactoring, or writing TypeScript/React/Node.js code').

List 1-2 concrete actions the skill performs (e.g., 'Applies naming, error-handling, and type-safety conventions to code') instead of the generic 'best practices and patterns'.

Narrow the scope so it is distinguishable from general coding/linting/review skills.

DimensionReasoningScore

Specificity

It names the domain ('coding standards, best practices, and patterns') and stack but lists zero concrete actions, fitting anchor 2 ('Names the domain but actions are minimal or generic') rather than 3 which requires 1-2 concrete actions.

2 / 5

Completeness

The description gives a clear 'what' but no 'Use when...' clause, and the rubric caps completeness at 3 for missing explicit trigger guidance — matching anchor 3 ('Has a clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

'TypeScript, JavaScript, React, and Node.js' are natural terms users say, but there are no task-oriented trigger phrases ('review my code', 'refactor', 'clean up'), so it sits at anchor 3 ('Some relevant keywords but missing common variations or synonyms').

3 / 5

Distinctiveness Conflict Risk

'Universal coding standards' across the TS/JS/React/Node stack is extremely broad and overlaps with any coding, linting, or review skill, fitting anchor 2 ('Very broad; high overlap risk with many similar skills') better than 3.

2 / 5

Total

10

/

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.

Validation15 / 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
sickn33/agentic-awesome-skills
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.