CtrlK
BlogDocsLog inGet started
Tessl Logo

obsidian-homelab-logbook

Logs homelab events, changes, incidents, and maintenance notes to structured Obsidian notes.

60

Quality

70%

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 ./skills/obsidian-homelab-logbook/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.

The body is concise, well-structured, and actionable with a clear sequenced workflow and error-recovery guidance; its main weakness is minor redundancy across the Workflow, Inputs, and Outputs sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but Workflow Steps, Inputs, and Outputs repeat some details (timestamp/host/severity, MOC update), which trims it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete guidance is present via the file-path template "Homelab/Logs/YYYY-MM-DD-event-title.md" and a clear enumerated workflow, with only minor gaps (no note-body template or concrete tag syntax) keeping it from a 5.

4 / 5

Workflow Clarity

Six steps are clearly sequenced and the Failure Modes section supplies feedback loops (write conflict prompts user to close the note; missing host note triggers a stub plus a flag), but there is no explicit validation checkpoint in the workflow itself.

4 / 5

Progressive Disclosure

At roughly 50 lines with well-organized sections and no need for bundle files (references/ and scripts/ are empty), it is a self-contained overview with clearly signaled one-level references (Obsidian Help URL, companion skills), matching the clear-overview anchor.

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.

The description is specific and uses natural homelab terminology, but it omits an explicit "Use when..." trigger clause, which caps its completeness and limits its usefulness for skill selection.

Suggestions

Add an explicit trigger clause, e.g. "Use when recording homelab changes, incidents, or maintenance in an Obsidian vault."

Broaden the verb beyond a single "Logs" to hint at note creation, linking, and indexing actions the skill actually performs.

Include a natural synonym or two (e.g. "outages" alongside "incidents") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (homelab/Obsidian) and several concrete logged categories ("events, changes, incidents, and maintenance notes"), but relies on a single verb ("Logs") and does not cover creation/indexing actions the body describes, so it sits at the anchor for clear-but-not-comprehensive coverage rather than the level above.

3 / 5

Completeness

It states a clear "what" (logs homelab events to structured Obsidian notes) but provides no "Use when..." trigger guidance, and the rubric caps completeness at 3 when explicit trigger guidance is missing.

3 / 5

Trigger Term Quality

Includes natural terms a homelab operator would say ("homelab events, changes, incidents, maintenance notes" plus "Obsidian"), giving good keyword coverage above the single-generic-keyword anchor, though it lacks synonyms or file extensions that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

The Obsidian-native homelab-logging niche is mostly distinct with minimal conflict risk; the only overlap is with the closely related companion skill `homelab-logbook`, matching the minor-overlap anchor rather than a fully isolated niche.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.