CtrlK
BlogDocsLog inGet started
Tessl Logo

explore-homecore

Map a Homecore capability to reviewed source, tests, ADRs, and limitations.

62

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 ./harness/homecore/.claude/skills/explore/SKILL.md
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.

The body is an exceptionally lean, well-sequenced exploration workflow with a concrete command and a clearly signaled reference. Its only weak spot is the absence of explicit validation/feedback steps, though the read-only nature of the task limits that impact.

DimensionReasoningScore

Conciseness

The ~10-line body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

It gives a concrete executable command `homecore guidance --query "<capability>" --repo <checkout>` and a specific doc path, but uses placeholders and leaves minor gaps in what to do with inspected test results, fitting 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

A clear five-step numbered sequence is present with implicit checkpoints (confirm status, inspect tests before proposing code); it stops short of explicit validate/retry feedback loops, matching 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files and a well-organized numbered structure, the simple-skill exception applies; the single one-level external reference (`v2/docs/homecore-capabilities.md`) is clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

58%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 concise and third-person with a clear niche, but it omits any explicit 'when to use' trigger guidance and relies on domain jargon rather than natural user phrasing. Adding a 'Use when...' clause with common trigger terms would lift completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when exploring or verifying a Homecore capability before writing code against it.'

Add natural-language synonyms users might say (e.g. 'Homecore feature', 'find out what Homecore supports') alongside the jargon terms ADRs/limitations.

Expand the single 'Map ... to' verb into distinct concrete actions to push specificity toward 5.

DimensionReasoningScore

Specificity

"Map a Homecore capability to reviewed source, tests, ADRs, and limitations" names the domain plus several concrete mapping targets; not a full 5 because a single verb covers all targets with minor coverage gaps.

4 / 5

Completeness

The description gives a clear 'what' (map a capability to source/tests/ADRs/limitations) but has no 'Use when...' or equivalent trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Terms like Homecore, capability, ADRs, and limitations are relevant but jargon-heavy and lack the natural synonyms or variations a user would actually say, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The Homecore-specific niche is mostly distinct with minimal conflict risk, though it could overlap slightly with general code-exploration skills, fitting the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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
ruvnet/RuView
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.