CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/project-brain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 well-organized with clearly labeled sections and a genuine progressive-disclosure structure backed by real reference files, but it operates almost entirely at the policy level. It names no executable command, script, or validation gate, which leaves both actionability and workflow clarity in the middle of the scale despite the skill's runbook intent.

Suggestions

Name the actual commands in the body: replace 'Use the canonical bootstrap or repo wrapper' with the exact bootstrap script path and invocation, and specify what 'strict skill audit' and 'Plugin Eval' concretely run.

Merge the overlapping Constraints / Execution Boundaries / Avoid / Anti-Patterns / Gotchas sections into one boundaries section to remove near-duplicate bullets like the two 'keep writes inside...' statements.

Turn the Validation section into explicit checkpoints (e.g., the exact validation command per changed surface and the pass condition) so the fail-fast loop is executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but is noticeably padded by redundant sections: 'Keep writes inside the repo-owned source path unless the user explicitly approves another target' (Constraints) restates 'Keep writes inside the target repository Project Brain surfaces...' (Execution Boundaries), and Avoid/Anti-Patterns/Gotchas overlap heavily. This fits the 3 anchor ('mostly efficient but... could be tightened') better than 2, since the verbosity is repetition of policy rather than unnecessary explanation of known concepts.

3 / 5

Actionability

The guidance is abstract throughout: 'Use the canonical bootstrap or repo wrapper when setup is needed' never names the command, 'Run the smallest command or test that exercises the changed behavior' never names a test, and 'Use strict skill audit and Plugin Eval' gives no invocation. It matches the 2 anchor ('high-level hints but missing the specific steps to execute') rather than 1, because structural hints exist (start with 2-3 surfaces, route by confidence and permanence, stop and report exact blockers), but nothing is executable or copy-paste ready.

2 / 5

Workflow Clarity

The Workflow section lists a rough sequence (inspect existing state, read instructions, bootstrap, route facts, report) and the Validation section mandates fail-fast reruns, so a sequence is present. But checkpoints are implicit and abstract — no concrete validation command is ever named — matching the 3 anchor ('sequence present but checkpoints missing or implicit') and short of 4's 'most checkpoints present'. Since the skill writes durable repo memory and forbids destructive commands without naming the actual gates, this does not reach 4.

3 / 5

Progressive Disclosure

A dedicated Progressive Disclosure section clearly signals one-level-deep references with their purpose ('Use references/contract.yaml for the machine-readable contract', 'references/evals.yaml for benchmark and quality gates', 'references/task-profile.json for evaluator thresholds'), and all three files exist in the bundle. It does not reach 5 because the body also points to Infrastructure/references/openai-cookbook-expert-lens-pack.md and Infrastructure/references/deferred-skill-context/agent-ops-project-brain/, which are not present in this bundle, leaving dangling navigation paths.

4 / 5

Total

12

/

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.

The description is strong: third-person, concise, and it explicitly states both what the skill does and when to use it with natural trigger phrases. Its only weakness is modest coverage — it names create/validate/repair but not the fact-routing capability that fills much of the skill body.

DimensionReasoningScore

Specificity

Names the domain ('Project Brain .harness memory files') and three concrete actions ('Create, validate, and repair'), matching the 'several specific actions with minor gaps' anchor. It falls short of the 5 anchor because it omits other capabilities the body covers, such as routing facts to knowledge/decisions/learnings surfaces, and above 3 because the actions are specific rather than generic.

4 / 5

Completeness

Explicitly answers both questions: what ('Create, validate, and repair Project Brain .harness memory files') and when ('when setting up Project Brain, saving repo learnings, recording decisions, or preserving quality rules'), with concrete trigger phrases matching the 5 anchor pattern. Not 4, because the 'when' clause is explicit and enumerates specific triggering scenarios rather than being merely adequate.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present: 'setting up Project Brain', 'saving repo learnings', 'recording decisions', 'preserving quality rules', plus distinctive terms like '.harness'. A few natural variations (e.g. 'remember this lesson', 'wire in repo memory') are missing, so it sits between the 4 and 5 anchors, clearly above 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

'Project Brain' and '.harness' are niche, distinctive artifacts with clear triggers, so the description occupies a clear niche with minimal conflict risk against generic note-taking or memory skills. It matches the 5 anchor; there is no neighboring anchor that fits better since the trigger terms are proprietary rather than broad.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/project-brain/SKILL.md

Reviewed

Table of Contents

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.