repo-architecture

Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills.

Quality

68%

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 ./skills/repo-architecture/SKILL.md

Quality

Content

82%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 a lean, well-structured filing guide with concrete decision-tree paths, an output template, and useful anti-patterns, appropriately offloading full rules to external references. Its main weaknesses are the advisory (non-executable) notability step and references to files that do not exist in the bundle.

Suggestions

Inline a brief, concrete notability check (or its key pass/fail criteria) so the workflow is self-contained instead of deferring entirely to skills/conventions/quality.md.

Convert bare backtick references (e.g., `skills/_brain-filing-rules.md`) into markdown links and ensure the referenced files exist in the bundle so navigation actually resolves.

Add an explicit verification checkpoint (e.g., 'Confirm no existing page covers this subject before creating') to give the filing workflow a validate-before-write feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; sections like Contract, Phases, Output Format, and Anti-Patterns each earn their tokens and offload full rules to external files.	5 / 5
Actionability	The decision tree gives concrete file paths (e.g., 'people/{name-slug}.md') and an explicit output-format template, but the output is explicitly advisory and notability checking is deferred to an external file rather than being executable inline, leaving a minor gap.	4 / 5
Workflow Clarity	A clear four-phase sequence (identify subject, walk decision tree, cross-link, check notability) with the notability gate acting as a checkpoint, but there is no explicit validate-and-retry feedback loop and two phases simply point to external files.	4 / 5
Progressive Disclosure	Content is well split into labeled sections with one-level-deep references to skills/_brain-filing-rules.md and skills/conventions/quality.md, but those referenced files are not present in the bundle and paths are bare backticks rather than navigable links, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

53%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 clearly communicates the skill's niche (filing brain pages by primary subject) but lacks an explicit use-when trigger clause and concrete action enumeration, capping completeness and specificity. Trigger terms are domain-appropriate but the natural user phrasing is segregated into the triggers field rather than the description.

Suggestions

Add an explicit 'Use when ...' clause to the description naming the natural user phrases (e.g., 'Use when creating a new brain page or deciding where a brain file goes').

Enumerate 2-3 concrete actions (e.g., 'classify by primary subject, walk the decision tree, cross-link related pages') so specificity reads as comprehensive rather than a protocol label.

Surface at least one natural trigger synonym inside the description body, not only in the triggers field, to lift trigger-term quality.

Dimension	Reasoning	Score
Specificity	Quotes 'Decision protocol for filing brain pages by primary subject' name the domain and a concrete decision action, but the description frames it as a reference/protocol rather than enumerating multiple concrete actions, so it is not comprehensive.	3 / 5
Completeness	The 'what' is clear ('Where new brain files go... Reference for all brain-writing skills'), but there is no explicit 'Use when...' clause and the 'when' is only weakly implied, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Terms like 'brain files', 'brain pages', 'filing', and 'primary subject' are relevant domain keywords, but the natural phrases a user would actually say live in the triggers field rather than the description, leaving common variations missing.	3 / 5
Distinctiveness Conflict Risk	'Reference for all brain-writing skills' carves a clear, narrow niche for filing brain pages, making it mostly distinct with only minor overlap risk against other brain-writing skills.	4 / 5
	Total	13 / 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: garrytan/gbrain
Path: skills/repo-architecture/SKILL.md
Commit: 055ac6c

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