CtrlK
BlogDocsLog inGet started
Tessl Logo

homelab-research-librarian

Researches, evaluates, and documents homelab tooling, self-hosted apps, and infrastructure patterns.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/homelab-research-librarian/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 compact, well-structured instruction skill with concrete evaluation criteria, an exact output location, and a copy-ready template. Its main gaps are the unspecified search approach and the absence of any validation checkpoint before the recommendation is documented.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, but the intro paragraph largely repeats the frontmatter description and the Invocation section is harness boilerplate that could be trimmed, matching anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than anchor 5.

4 / 5

Actionability

Concrete guidance throughout — the five explicit scoring criteria ("ease of deployment, community support, resource usage, security posture, maintenance burden"), the exact vault path "Homelab/Research/topic.md", and a copy-ready output template. Not 5 because step 2 ("Search for candidates") leaves sources and search strategy unspecified, and there is no worked example of a scored row.

4 / 5

Workflow Clarity

Six clearly sequenced steps (define, survey, evaluate, compare, recommend, document) where the evaluation step acts as an implicit checkpoint before recommending. No explicit validation steps exist, but the operation is non-destructive and single-output, so the workflow-clarity cap does not apply; this keeps it at anchor 4 rather than anchor 5's explicit validation feedback loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (references/ and scripts/ are empty), and the body is organized into clear sections (Invocation, Workflow Steps, Output Format, Companion Skills) — the simple-skill exception in the scoring notes applies.

5 / 5

Total

17

/

20

Passed

Description

61%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 reasonably specific, domain-focused description that clearly states what the skill does, but it lacks any 'use when' trigger guidance and its verbs remain generic rather than concrete. Adding explicit trigger phrases and sharper capability wording would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when comparing self-hosted apps, evaluating homelab tools, or researching alternatives to a service you want to self-host."

Replace the generic verbs with concrete outputs, e.g. "Surveys candidates, scores each on deployment ease, resource usage, and maintenance burden, and writes a comparison note and recommendation to the Obsidian vault."

Include common synonyms and phrasings users would say ("home server", "self-hosting", "alternatives to X", "compare apps") to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ("homelab tooling, self-hosted apps, and infrastructure patterns") plus three actions, but "researches, evaluates, and documents" are generic verbs without concrete outputs, matching anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") rather than anchor 4's specific operations.

3 / 5

Completeness

The 'what' is clear (research, evaluate, and document homelab tooling) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"homelab tooling", "self-hosted apps", and "infrastructure patterns" are natural phrases a homelab user would actually say, giving good keyword coverage; not 5 because common variations like "home server", "self-hosting alternatives", or "compare apps" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche homelab/self-hosted domain makes it mostly distinct with only minor overlap risk against a generic research or documentation skill; not 5 because the vague verbs could still match a general 'research this' request, and not 3 since the domain terms are far more specific than 'works with document files'.

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
pvnkmnk/AgenticSelfHostSkills
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.