CtrlK
BlogDocsLog inGet started
Tessl Logo

review-homecore-server

Review Homecore server startup, restore, authentication, feature, and provider configuration.

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/operate-server/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 a lean, well-organized review checklist with a concrete reference command and clear scope boundary, scoring highly across conciseness and progressive disclosure with only minor actionability and workflow-clarity gaps.

DimensionReasoningScore

Conciseness

Each line is a terse, unpadded directive (e.g., "Restore registries before recorder states and keep limits bounded") with no over-explanation of concepts Claude already knows, matching the lean-and-efficient anchor; not below 5 because every token earns its place.

5 / 5

Actionability

Step 1 gives a concrete command ("Read `homecore-server --help` and ADR-161") and the remaining steps are specific, actionable directives appropriate to a plan-review skill; not a 5 because most steps lack copy-paste commands to verify each criterion, and not a 3 because the guidance is concrete rather than pseudocode-level.

4 / 5

Workflow Clarity

The numbered 1-6 sequence is clear and each item functions as a review checkpoint, with the closing line "This skill reviews a plan. It does not start the server." setting an explicit boundary; not a 5 because there is no explicit validate/feedback loop, and not a 3 because the sequence and per-step checks are well defined.

4 / 5

Progressive Disclosure

At under 50 lines with no need for bundle files (none exist in references/scripts/assets) and a clear title plus well-organized numbered list, this matches the simple-skill exception allowing a 5 with just well-organized sections; ADR-161 is appropriately referenced inline rather than nested.

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, third-person, and names a specific niche with several concrete review areas, but it omits any explicit "Use when..." trigger guidance, which caps completeness and limits trigger-term quality.

Suggestions

Add a "Use when..." clause naming natural trigger phrases (e.g., "Use when reviewing a Homecore server plan, startup sequence, or provider/auth configuration") so Claude knows when to invoke this skill.

Include common user-facing synonyms or phrasings alongside the technical terms to broaden trigger-term coverage.

Keep the concrete review areas but pair them with an explicit when-to-use statement to lift completeness from 3 to 4-5.

DimensionReasoningScore

Specificity

"Review Homecore server startup, restore, authentication, feature, and provider configuration" names the domain plus several concrete review areas (startup, restore, auth, features, provider config), matching the anchor that lists several specific actions with minor gaps; not a 5 because the only verb is "Review" applied to topic nouns rather than multiple distinct concrete actions.

4 / 5

Completeness

The description gives a clear "what" (review these server operation areas) but provides no "when"/"Use when..." trigger guidance, which per the guidelines caps completeness at 3; not a 4 because the "when" is entirely absent rather than weakly present.

3 / 5

Trigger Term Quality

Terms like "startup", "restore", "authentication", and "provider configuration" are relevant but lean technical and lack common variations or synonyms a user might naturally say; not a 4 because natural phrasing coverage is thin, not a 2 because there is more than one or two generic keywords.

3 / 5

Distinctiveness Conflict Risk

The named "Homecore server" niche is mostly distinct with only minor overlap risk against a generic server-review skill; not a 5 because explicit distinct triggers are not provided, and not a 3 because the named domain is clearly specific.

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.