CtrlK
BlogDocsLog inGet started
Tessl Logo

repository-investigation

Investigate an unfamiliar repository before changing it. Use this whenever a coding task spans multiple modules, asks for architecture or root-cause analysis, names behavior whose implementation location is unknown, or risks editing before enough evidence is gathered.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 concise, well-organized instruction-only skill that assumes Claude's intelligence and provides specific procedural guidance with a clear sequenced workflow. The only meaningful gap is the absence of an explicit validation/feedback loop and concrete tool names.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, never explaining basic concepts like repositories, concurrency, or persistence; every line is actionable guidance with no padding.

5 / 5

Actionability

Directives are specific and executable for an instruction-only skill ('Search for identifiers, routes, events... before opening large files', 'Verify both writers and readers of persisted or streamed state'), with minor gaps where concrete tooling could be named.

4 / 5

Workflow Clarity

The 8-step sequence is clearly ordered with a decision checkpoint in step 8 and an explicit stop condition, but it lacks a formal validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

At roughly 35 lines with no need for external references, the body is well organized into three clearly signaled sections (Workflow, Investigation discipline, Output), satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

78%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, well-structured description with an explicit and concrete 'Use when...' trigger clause and a clear statement of purpose. Its main weakness is that it enumerates triggering situations rather than the concrete actions the skill performs.

DimensionReasoningScore

Specificity

The description names the domain sharply ('Investigate an unfamiliar repository before changing it') but characterizes situations to trigger the skill rather than listing several concrete actions, sitting between anchor 2 and 3.

3 / 5

Completeness

It explicitly answers both 'what' ('Investigate an unfamiliar repository before changing it') and 'when' with a concrete multi-pronged 'Use this whenever...' clause covering several trigger conditions.

5 / 5

Trigger Term Quality

Natural user phrasings like 'spans multiple modules', 'architecture', 'root-cause analysis', and 'before changing it' are present and likely spoken, though synonyms like 'understand the codebase' or 'trace a bug' are missing.

4 / 5

Distinctiveness Conflict Risk

The pre-change investigation framing carves a clear niche distinct from generic coding skills, with only minor overlap risk against general debugging or refactoring skills.

4 / 5

Total

16

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ageerle/ruoyi-ai
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.