CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-coding-standards

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

30

Quality

23%

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

Quality

Content

22%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This SKILL.md is essentially a bare table of contents with 29 links to sub-skills but provides no actionable content, examples, or workflow guidance in the body itself. While the progressive disclosure approach of linking to sub-files is sound in principle, the complete absence of any summary content, concrete guidance, or organizational structure beyond a flat numbered list makes this skill body nearly useless on its own. The file fails to serve as an effective overview that would help Claude understand when and how to apply these coding standards.

Suggestions

Add a concise quick-start section with 3-5 of the most critical coding standards summarized inline with brief code examples, so the SKILL.md provides immediate actionable value without requiring sub-file reads.

Group the 29 sub-skills into logical categories (e.g., 'General Principles', 'TypeScript/JS', 'React Patterns', 'Node.js/API', 'Testing') with brief 1-line descriptions of each, so Claude can navigate efficiently.

Add a brief workflow section explaining when to apply these standards (e.g., 'When writing new code, follow these priorities: 1. Readability, 2. Type Safety, 3. Error Handling') to provide sequencing and prioritization.

Fix inconsistent numbering (e.g., '1. [1. Readability First]' and '27. [1. Long Functions]') which suggests the list was auto-generated without cleanup.

DimensionReasoningScore

Conciseness

The content is relatively lean—it's essentially a table of contents with no verbose explanations. However, it's almost entirely devoid of substance in the SKILL.md itself, which means the tokens it does use (numbered headings, redundant numbering like '1. [1. Readability First]') aren't maximally efficient.

2 / 3

Actionability

The SKILL.md provides zero concrete guidance, code, commands, or examples. It is purely a list of links to sub-skills with no actionable content whatsoever in the body itself. Claude would gain no executable knowledge from reading this file alone.

1 / 3

Workflow Clarity

There is no workflow, sequence, or process described. The content is an unstructured flat list of 29 links with no indication of when or how to apply these standards, no prioritization, and no validation steps.

1 / 3

Progressive Disclosure

The skill does attempt progressive disclosure by linking to 29 sub-skill files, which is the right structural approach. However, there is no categorization, grouping, or signaling beyond numbered links—no quick-start summary, no grouping by topic (e.g., React, Node.js, general), and no guidance on which sub-skills are most important. Without bundle files to verify, the references appear one-level deep but poorly organized.

2 / 3

Total

6

/

12

Passed

Description

25%Scale 1-3

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 its technology stack but is too vague about what it actually does and completely lacks trigger guidance for when it should be selected. The broad scope covering four technologies with generic terms like 'best practices and patterns' makes it highly prone to conflicts with other coding-related skills. It needs concrete actions and explicit 'Use when' clauses to be effective.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about coding conventions, style guidelines, naming patterns, or best practices for TypeScript, JavaScript, React, or Node.js projects.'

Replace vague 'best practices and patterns' with specific actions like 'enforces naming conventions, applies error handling patterns, recommends project structure, defines type safety rules'.

Narrow the scope or add distinguishing details to reduce conflict risk — e.g., specify whether this is about linting rules, architectural patterns, code review standards, or project setup conventions.

DimensionReasoningScore

Specificity

Names the domain (coding standards) and technologies (TypeScript, JavaScript, React, Node.js), but 'best practices and patterns' is vague — it doesn't list specific concrete actions like 'enforce naming conventions, apply design patterns, lint code'.

2 / 3

Completeness

Describes 'what' at a high level (coding standards and best practices) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores a 1.

1 / 3

Trigger Term Quality

Includes relevant technology keywords (TypeScript, JavaScript, React, Node.js) that users might mention, but 'coding standards' and 'best practices' are somewhat generic. Missing natural trigger terms like 'code review', 'style guide', 'linting', 'conventions', 'clean code'.

2 / 3

Distinctiveness Conflict Risk

Very broad scope covering four major technologies with generic terms like 'best practices' and 'patterns' — this would easily conflict with any TypeScript, JavaScript, React, or Node.js skill, as well as general coding or code review skills.

1 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.