project-conventions

Core conventions and patterns for this codebase

Quality

26%

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 ./.squad/templates/skills/project-conventions/SKILL.md

Quality

Content

33%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 an unfilled starter template: well-structured section scaffolding but no actual executable guidance, code, or workflow. It is token-lean and cleanly organized yet delivers essentially no actionable skill content.

Suggestions

Replace each HTML-comment placeholder with concrete conventions, e.g. real error-handling rules, the actual test framework and run command, and the real linter/formatter config.

Fill the Examples code block with copy-paste-ready snippets that demonstrate the conventions in use.

Add an explicit authoring workflow with validation (e.g. 'verify examples compile against the current lint config before saving').

Dimension	Reasoning	Score
Conciseness	The body is lean and does not over-explain concepts Claude already knows, but the meta 'This is a starter template' note and numerous HTML-comment placeholders are scaffolding tokens that don't fully earn their place, keeping it just below a 5.	4 / 5
Actionability	Every section is a placeholder — the code block is empty ('// Add code examples') and guidance is author-facing prompts like '<!-- Example: How does your project handle errors? -->' — providing no concrete, executable instruction, matching the 'entirely vague or abstract' anchor.	1 / 5
Workflow Clarity	There is no multi-step sequence and no validation checkpoints whatsoever; the body is unsequenced scaffolding, matching the 'steps missing or incoherent' anchor.	1 / 5
Progressive Disclosure	Section headers (Context, Patterns, Examples, Anti-Patterns) are logically organized and the skill is under 50 lines with no bundle files, but the placeholder-only content means no real overview-to-detail split is demonstrated, so it stays below 5.	4 / 5
	Total	10 / 20 Passed

Description

20%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 a generic placeholder that names a domain but states no concrete actions and provides no usage trigger, making it indistinct and unlikely to surface for the right task. It reads as template scaffolding rather than a real skill description.

Suggestions

Add 2–3 concrete actions, e.g. 'Documents error-handling, testing, and code-style conventions and surfaces them when editing this codebase.'

Append an explicit trigger clause: 'Use when writing or modifying code in this codebase, or when the user asks how things are done here.'

Narrow the niche with codebase-specific terms (framework names, file types) to reduce overlap with other skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Core conventions and patterns' names only abstract subject matter with no verbs or concrete actions — vaguer even than the score-2 anchor 'Processes PDF files', which at least names a minimal action.	1 / 5
Completeness	It gives only a vague 'what' (the subject matter) and entirely lacks a 'when'/'Use when' trigger clause, matching the 'vague what and no when' anchor; the missing-trigger cap of 3 is not reached anyway.	2 / 5
Trigger Term Quality	It offers a couple of generic keywords ('conventions', 'patterns', 'codebase') a user might say, but misses the natural trigger phrases users would actually invoke, fitting the 'one or two generic keywords' anchor.	2 / 5
Distinctiveness Conflict Risk	'Core conventions and patterns for this codebase' is very broad and overlaps with nearly any coding skill, though the 'this codebase' scoping keeps it just above the 'conflicts with virtually any skill' level.	2 / 5
	Total	7 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sbroenne/mcp-server-excel
Path: .squad/templates/skills/project-conventions/SKILL.md
Commit: b2eab4c

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