homelab-logbook

Records all homelab changes, incidents, and maintenance events to a structured, searchable log.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/homelab-logbook/SKILL.md

Quality

Content

68%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 concise and reasonably actionable with a clear entry format and sequenced workflow, and it is well-structured with no nested references. Its main weakness is the absence of any validation/verification step for the log-append and vault-store writes, which the rubric caps at workflow clarity 3 for batch/write operations.

Suggestions

Add an explicit verification step to the workflow, e.g. after Store: confirm the entry was appended and the index/host list was updated; re-run if missing.

Provide one fully filled-in example log entry so the format is unambiguous and copy-paste ready.

Specify the concrete log file path/vault location convention (or reference a small reference doc) so 'append to the running log file' is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line purpose, an entry-format block, a 5-step workflow, and a short companion list, with no padded explanations of concepts Claude already knows; it could be marginally tighter but every section earns its place.	4 / 5
Actionability	Provides a concrete, copy-paste log entry format with explicit field enums (Type, Severity, Result) and a clearly sequenced 5-step workflow; it stops just short of a 5 because it gives no example of a filled-in entry and no literal command/path for the log file.	4 / 5
Workflow Clarity	The five steps are clearly sequenced, but the skill appends to a running log AND a vault store (a write/batch operation) with no validation or verification checkpoint — e.g. confirming the entry was written or the index updated — so per the feedback-loop guideline workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Well-organized into short sections (purpose, invocation, format, workflow, companions) with no nested references; the references/ and scripts/ directories hold only .gitkeep, so there are no broken links. It is not a 5 because, for an append-to-vault skill, detail such as vault path conventions or the index schema could be split into a referenced file rather than left implicit.	4 / 5
	Total	15 / 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 is specific and reasonably distinct within a clear niche, with a solid 'what' statement and natural domain keywords. Its main weakness is the absence of an explicit 'Use when' trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit 'Use when' clause, e.g. 'Use when recording a homelab change, incident, or maintenance event, or when the user asks to log or audit infrastructure activity.'

Expand trigger terms with natural synonyms users would say, such as 'log a change', 'homelab audit trail', or 'what changed in the homelab'.

Name the companion skills' distinct triggers to sharpen distinctiveness and reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain (homelab) and lists concrete event types ('changes, incidents, and maintenance events') with the action 'Records ... to a structured, searchable log', but does not enumerate multiple distinct actions — it covers one action (recording) across several event types, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Has a clear 'what' (records homelab changes/incidents/maintenance to a searchable log) but no explicit 'when' / 'Use when' trigger clause, so per the judging guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant keywords ('homelab', 'changes', 'incidents', 'maintenance') a user might say, but lacks common synonyms or file-extension-style triggers and misses natural phrases like 'log a change' or 'what changed'; matches 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The 'homelab' niche is specific and the companion-skill ecosystem implies distinct triggers, so overlap risk is low; it is not a full 5 because the description itself does not name the sibling skills or give sharply distinct trigger phrases.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: skills/homelab-logbook/SKILL.md
Commit: 0f62e6b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.