coding-standards

Convenciones de codificación base entre proyectos para nomenclatura, legibilidad, inmutabilidad y revisión de calidad de código. Usar skills de frontend o backend para patrones específicos de frameworks.

Quality

62%

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 ./docs/es/skills/coding-standards/SKILL.md

Quality

Content

57%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 skill is a rich, actionable convention catalog with strong PASS/FAIL code examples, but it is over-long for a SKILL.md, re-explains familiar concepts, and lacks both a validation-backed workflow and genuine progressive disclosure into separate files. Tightening the body and splitting framework-specific sections (React, API design, performance, tests) into referenced files would improve conciseness and progressive disclosure.

Suggestions

Trim restatements of well-known principles (KISS/DRY/YAGNI definitions, async/await basics) and keep only the team-specific conventions to lift conciseness.

Move the larger framework-specific sections (React, API design, performance, testing) into referenced files (e.g. references/react.md, references/api-design.md) with one-line pointers, improving progressive disclosure.

Add an explicit review/refactor workflow with validation checkpoints (e.g. run lint/typecheck, verify no direct mutation) so workflow clarity reflects the skill's "Cuándo Activar" triggers.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with PASS/FAIL code pairs, but it re-explains well-known principles (KISS, DRY, YAGNI, what async/await does) and inlines large sections (React, API design, performance, tests) that largely restate knowledge Claude already has, adding padding.	3 / 5
Actionability	It provides numerous concrete, executable TypeScript code examples covering naming, immutability, error handling, hooks, validation, and tests with clear PASS/FAIL contrasts, though some examples are stubs ("// Implementación") leaving minor gaps.	4 / 5
Workflow Clarity	There is no real multi-step workflow sequenced with checkpoints; the skill is a reference catalog of conventions, and its "Cuándo Activar" list gives triggers but no validation or verification steps for batch/destructive operations like refactors, so sequence-with-checkpoints is only weakly present.	3 / 5
Progressive Disclosure	It has clear section headers and signals sibling skills/rules (frontend-patterns, backend-patterns, rules/common/coding-style.md), but the bulk of detailed reference material is inlined in SKILL.md rather than split into one-level-deep files, and no bundle files exist, so content that should be separate remains inline.	3 / 5
	Total	13 / 20 Passed

Description

67%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 specific and establishes a clear niche with explicit deferral to sibling skills, but it lacks a direct 'Use when...' trigger clause and natural user-facing keywords, capping completeness and trigger quality. Rewording the second sentence as an explicit activation trigger would lift both dimensions.

Suggestions

Add an explicit 'Usar cuando...' trigger clause naming natural situations (e.g. al iniciar un proyecto, al revisar código, al configurar linting) so completeness can reach 5.

Incorporate natural user-facing terms and synonyms ("code review", "naming conventions", "linting", "DRY/KISS", "code quality") to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("nomenclatura, legibilidad, inmutabilidad y revisión de calidad de código") rather than vague language, but the actions are framed as topical domains rather than discrete verbs, leaving minor gaps in coverage.	4 / 5
Completeness	It answers "what" (base coding conventions across projects) and gives a weak-to-explicit "when" via the redirect clause ("Usar skills de frontend o backend para patrones específicos"), but the trigger guidance is indirect rather than a concrete 'Use when...' phrase.	4 / 5
Trigger Term Quality	It names relevant domains (nomenclatura, legibilidad, inmutabilidad, calidad de código) but lacks the natural phrases and variations a user would actually say (e.g. "naming", "code review", "linting", "DRY/KISS"), missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	It carves a clear niche (cross-project base conventions) and explicitly routes framework-specific work to sibling skills, minimizing overlap, with only minor risk of broad triggering on general 'code quality' requests.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (550 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: docs/es/skills/coding-standards/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.