homelab-logbook

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

Quality

78%

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

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.

The body is well-structured and token-efficient: a concrete entry template drives an unambiguous five-step workflow, and companion skills are cleanly cross-referenced. The remaining gaps are unspecified storage locations (running log file path, index location) and the absence of any format-validation checkpoint, which keep actionability and workflow clarity at 4.

Suggestions

Specify the log file path (e.g. a canonical location like ~/homelab/log.md or a configured variable) in the Store and Index steps so execution is fully deterministic.

Add a quick validation cue in the Capture step, e.g. confirm every field of the entry template is filled before appending.

Drop or compress the Invocation section and the redundant opening paragraph, which repeat the description and harness mechanics.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation: a concrete entry template, five terse workflow steps, and a companion-skill list. Not 5 because the opening paragraph restates the frontmatter description nearly verbatim and the "Invocation" section ("OpenCode / Codex: Invoke homelab-logbook", "Freebuff: /skill homelab-logbook") is harness meta-content that could be trimmed. Not 3 because padding is minor, not 'several unnecessary explanations'.	4 / 5
Actionability	The Log Entry Format block is a concrete, copy-paste-ready template with exact fields and enums ("Type: change \| incident \| maintenance \| observation", "Result: success \| partial \| failed \| ongoing"), and each workflow step names a concrete action. Not 5 because "Append to the running log file" and "Update the homelab log index" never specify the actual file path or index location, leaving execution details implicit. Not 3 because the guidance is fully concrete except for those storage paths — no pseudocode.	4 / 5
Workflow Clarity	The five steps (Classify, Capture, Store, Tag, Index) form a clear, ordered sequence that references the defined entry format. Not 5 because there are no checkpoints (e.g. verifying the entry matches the format, or what to do when a host is unknown to the index) and the storage target is unspecified. Not 3 because logging is neither destructive nor batch, validation checkpoints are not critical here, and the sequence plus template leaves little ambiguity about order.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references (references/ and scripts/ contain only .gitkeep), and the content is organized into clearly signaled sections (Invocation, Log Entry Format, Workflow Steps, Companion Skills) with no nested or dead references. Per the rubric guideline, this matches the simple-skill case that merits a 5 with well-organized sections alone.	5 / 5
	Total	17 / 20 Passed

Description

66%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 specific about what the skill records and where it goes, with natural trigger terms for the homelab domain. Its main weakness is the complete absence of any 'when to use' guidance, which caps completeness at 3. It is also mildly vulnerable to overlap with its companion logging skills.

Suggestions

Append an explicit trigger clause, e.g. "Use when making homelab changes, responding to incidents, performing maintenance, or when the user asks to log/audit homelab activity."

Add natural synonyms users would say, such as "outage", "downtime", or "audit trail", to broaden trigger coverage.

Add a distinguishing cue (e.g. "primary audit trail; vault storage handled by obsidian-homelab-logbook") to reduce conflict risk with the companion logging skill.

Dimension	Reasoning	Score
Specificity	"Records all homelab changes, incidents, and maintenance events to a structured, searchable log" names the domain and several concrete event types with a concrete storage target, matching 'lists several specific actions; minor gaps'. Not 5 because it describes essentially one recording action rather than multiple distinct operations; not 3 because coverage of change/incident/maintenance plus structured, searchable storage goes beyond 1-2 actions.	4 / 5
Completeness	The description has a clear 'what' (recording homelab changes, incidents, and maintenance events to a structured log) but entirely lacks a 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. Not 2 because the 'what' is concrete and specific, not vague.	3 / 5
Trigger Term Quality	Terms like "homelab", "changes", "incidents", "maintenance", and "log" are natural phrases a user would say when needing this skill, but common variations such as "outage", "downtime", "audit trail", or "journal" are missing. This fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of a 5.	4 / 5
Distinctiveness Conflict Risk	"Records all homelab changes, incidents, and maintenance events" carves out a clear homelab-operations niche with distinct triggers, but there is minor overlap risk with the closely related companion skill `obsidian-homelab-logbook` and general note-taking/logging skills. Not 5 because the description itself gives no cue distinguishing it from those vault/logging siblings.	4 / 5
	Total	15 / 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: ff4471e

Reviewed: 2 hours 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.