base

Universal coding patterns, constraints, TDD workflow, atomic todos

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/base/SKILL.md

Quality

Content

70%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 highly actionable with clearly sequenced, validated TDD workflows and concrete per-stack commands, but it is verbose with repeated TDD emphasis and references bundle files that do not exist alongside inlined content that should be split out.

Suggestions

Consolidate the TDD workflow into one section and reference it elsewhere instead of restating it in Bug Fix, Response Format, and Automatic Loops sections.

Trim the generic anti-patterns list (global state, magic numbers, deep nesting) that Claude already knows, keeping only project-specific rules.

Create the referenced credentials.md, security.md, and session-management.md files and move their inlined detail there, or remove the dangling references.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete rules, but the TDD workflow is repeated across five sections and generic concepts Claude already knows (anti-patterns like 'global state', 'magic numbers') add padding, keeping it at the 'could be tightened' anchor.	3 / 5
Actionability	Provides concrete, executable commands per stack (npm test, pytest, ruff, mypy) and a copy-paste todo template, but some templates use placeholders like [filename-a].ts, leaving minor gaps versus fully copy-paste-ready.	4 / 5
Workflow Clarity	The TDD and bug-fix workflows are explicitly sequenced (RED/GREEN/VALIDATE/COMPLETE) with validation checkpoints, feedback loops on failure, and blocking conditions, matching the 'explicit validation steps + error recovery' anchor.	5 / 5
Progressive Disclosure	Section headers provide structure and one-level references ('See credentials.md', 'See security.md skill', 'See session-management.md'), but those referenced files are absent from the bundle and content that belongs in separate files (credentials, security, session) is inlined.	3 / 5
	Total	15 / 20 Passed

Description

46%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 concise and lists several relevant topics, but it lacks action verbs and any explicit 'when to use' trigger guidance, and its 'universal' framing creates high overlap risk with other coding skills.

Suggestions

Reword topic nouns as concrete actions, e.g. 'Enforces function/file size limits, runs TDD red-green-validate loops, tracks atomic todos'.

Add an explicit trigger clause such as 'Use when starting any coding task that needs structure, testing, or todo tracking.'

Narrow the 'Universal coding patterns' framing to reduce overlap with general coding skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Universal coding patterns') plus several concrete topics ('TDD workflow, atomic todos'), but phrased as a noun list with no action verbs, so it falls short of the multi-action anchor at 4.	3 / 5
Completeness	The description gives a clear 'what' (patterns, constraints, TDD, atomic todos) but contains no 'Use when...' clause or explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'TDD workflow' and 'atomic todos' are terms a user might naturally say, but 'coding patterns, constraints' is generic and no synonyms or file extensions are present, matching the 'some relevant keywords' anchor.	3 / 5
Distinctiveness Conflict Risk	'Universal coding patterns, constraints' is very broad and, as an always-loaded foundation, has high overlap risk with many other coding skills, matching the 'very broad' anchor.	2 / 5
	Total	11 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (534 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/base/SKILL.md
Commit: abc600e

Reviewed: 3 days 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.