CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

load-repo-context

Primes understanding of repository architecture by navigating hierarchical ABOUT.md manifests.

Quality

75%

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 ./.agents/skills/load-repo-context/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a compact, single-purpose skill whose body delivers a clear, sequenced, read-only workflow with appropriate structure and no bundle-file overhead. Its only weaknesses are minor: a redundant opening sentence, undefined 'Elephant' jargon, and no fallback guidance when ABOUT.md files are absent. These small issues keep conciseness and actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and imperative with numbered steps that assume Claude's competence, but the opening sentence 'Primes understanding of repository architecture by navigating hierarchical ABOUT.md manifests before inspecting or modifying source code' restates the frontmatter description, and 'to establish the "Elephant" context' is unexplained jargon — minor instances that could be trimmed.

4 / 5

Actionability

The guidance is concrete and executable for an instruction-only skill ('Read the root `./ABOUT.md`', 'Traverse and read only the targeted child `ABOUT.md` files', 'Present a 3-5 bullet point architectural summary'), with only minor gaps such as no fallback if no ABOUT.md exists — mostly executable rather than fully complete.

4 / 5

Workflow Clarity

A clear, unambiguous 4-step numbered sequence (read root manifest → identify relevant subsystems → traverse child manifests → present summary) for a simple, single-purpose, read-only skill; the simple-skill exception applies since the single task is unambiguous and no destructive or batch validation is needed.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references, the body is well-organized into a title, a one-line purpose statement, and an Instructions section — meeting the simple-skill criterion for a top progressive disclosure score.

5 / 5

Total

18

/

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 states a clear, third-person 'what' anchored by the distinctive ABOUT.md mechanism, giving it low conflict risk with other skills. However, it entirely lacks a 'when to use' trigger clause and offers only one concrete action, leaving both completeness and trigger coverage at the mid anchor. Adding an explicit 'Use when...' sentence with natural trigger phrases would lift the two heaviest-weighted dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when onboarding to an unfamiliar codebase, planning a change that spans subsystems, or when ABOUT.md files exist in the repository.'

Enumerate the concrete actions more fully (e.g. 'maps top-level subsystems, traverses child ABOUT.md manifests, and summarizes targeted architecture') to raise specificity from one action to several.

Include natural user phrasings and synonyms such as 'repo', 'codebase', 'project structure', or 'repo overview' so the description matches how users actually ask for this.

DimensionReasoningScore

Specificity

Names the domain ('repository architecture') and one concrete action ('navigating hierarchical ABOUT.md manifests'), matching the domain-plus-1-2-actions anchor; it is not a 4 because there are not several distinct specific actions listed.

3 / 5

Completeness

The 'what' is clear ('Primes understanding of repository architecture by navigating hierarchical ABOUT.md manifests') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like 'repository', 'architecture', and 'ABOUT.md' are present, but common natural variations users would say ('repo', 'codebase', 'repo structure', 'project layout') are missing, matching the some-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

'ABOUT.md manifests' is a distinctive niche trigger that clearly separates this from generic document or code skills, matching the mostly-distinct anchor with only minor overlap risk against general repo-onboarding or codebase-exploration skills; not a 5 because 'repository architecture' alone is broad enough to overlap with such skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

flutter/flutter-intellij

Path

.agents/skills/load-repo-context/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.