project-brain

Create, validate, and repair Project Brain .harness memory files when setting up Project Brain, saving repo learnings, recording decisions, or preserving quality rules.

Quality

90%

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

Quality

Content

92%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.

A lean, well-structured runbook with strong validation feedback loops and a verified progressive-disclosure layout. The lone gap is the absence of named executable commands, which is acceptable for an instruction-only skill but keeps actionability just below the top anchor.

Dimension	Reasoning	Score
Conciseness	A tight bullet-driven runbook with no concept over-explanation; every section earns its place and it assumes Claude's competence.	5 / 5
Actionability	Concrete instructional guidance ("Start read-only by inspecting...", "Use the canonical bootstrap or repo wrapper") with clear disposition routing, though it stops short of naming specific executable commands.	4 / 5
Workflow Clarity	Workflow is sequenced with explicit validation checkpoints and a feedback loop ("If validation fails, fix only the smallest Project Brain surface... then rerun the same command"; "Fail fast: stop at first failed gate").	5 / 5
Progressive Disclosure	A clear overview body with well-signaled one-level-deep references to real bundle files (references/contract.yaml, evals.yaml, task-profile.json all exist), plus a clearly labeled deferred-detail path.	5 / 5
	Total	19 / 20 Passed

Description

87%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.

A strong, specific description that answers both what and when with concrete actions and natural trigger phrases. Its only soft spot is keyword breadth in the trigger clause.

Dimension	Reasoning	Score
Specificity	"Create, validate, and repair" names three concrete actions against a specific domain (Project Brain .harness memory files), with only minor coverage gaps versus a fully comprehensive list.	4 / 5
Completeness	It explicitly states both what it does ("Create, validate, and repair Project Brain .harness memory files") and when to use it ("when setting up Project Brain, saving repo learnings, recording decisions, or preserving quality rules").	5 / 5
Trigger Term Quality	"saving repo learnings, recording decisions, or preserving quality rules" are natural phrases users would say, with good but not exhaustive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	"Project Brain .harness memory files" carves a clear niche with distinct triggers unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: jscraik/Agent-Skills
Path: Skills/agent-ops/project-brain/SKILL.md
Commit: f1f2f21

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