everything-claude-code

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/everything-claude-code/SKILL.md

Quality

Content

46%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 information-rich with concrete examples and clear conventions, but it is verbose, structurally repetitive, and lacks validation checkpoints and any progressive file structure. Several workflow 'Example commit sequence' blocks are broken, repeating step text rather than showing commits.

Suggestions

Fix the 'Example commit sequence' blocks in the Add Language Rules, Add New Skill, Add New Agent, Sync Catalog Counts, Add Cross Harness Skill Copies, Add Or Update Hook, and Address Review Feedback workflows — they currently duplicate the step prose instead of showing real commits.

Add validation/verification checkpoints to destructive or batch workflows (e.g., Sync Catalog Counts, Database Migration) following a validate → fix → retry pattern.

Move the long per-workflow reference material into files under references/ and link to them from SKILL.md to improve navigation and reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose and structurally repetitive, with ~10 near-duplicate workflow sections; several 'Example commit sequence' blocks merely repeat the step prose rather than showing real commits, padding the document.	2 / 5
Actionability	It provides concrete, copy-paste-ready commit examples, a naming-convention table, specific file globs, and per-workflow file lists — mostly executable guidance with only minor gaps (e.g., the mis-pasted commit sequences and the vague 'No specific test framework detected').	4 / 5
Workflow Clarity	Workflows list numbered steps and involved files, but several embed step prose inside 'Example commit sequence' blocks instead of real commits, and none include validation checkpoints for destructive/batch operations like catalog sync or migrations — capping this at 3 per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are empty) and all content is inlined into a single monolithic SKILL.md with no external references or navigation, so content that belongs in separate files is not split out.	2 / 5
	Total	11 / 20 Passed

Description

48%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 project but lacks an explicit trigger/use-when clause and concrete capabilities. It is reasonably distinct because it names the specific project, yet it reads more like a tagline than an activatable skill description.

Suggestions

Add an explicit 'Use when...' clause listing concrete triggers (e.g., 'Use when writing commit messages, adding tests, or adding skills/agents/workflows to this repository').

Replace the generic 'conventions and patterns' phrasing with concrete actions the skill enables, such as 'format commit messages, follow naming conventions, and match project file/test patterns'.

Include natural keyword variations users would say, like 'commit message', 'conventional commit', and 'JavaScript conventions'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Development conventions and patterns for everything-claude-code') but the only semi-concrete action referenced is 'conventional commits', which is a pattern rather than an action the skill performs; actions are minimal/generic.	2 / 5
Completeness	There is a recognizable 'what' (development conventions/patterns) but no 'when' clause — no 'Use when...' guidance — so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant keywords like 'JavaScript project' and 'conventional commits' are present, but it misses the natural phrases users actually say such as 'commit message', 'write commits', or 'format commits'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific project 'everything-claude-code' makes it mostly distinct from other skills, with only minor overlap risk from the broad phrase 'development conventions and patterns'.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .agents/skills/everything-claude-code/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.