CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

daemon-runtime

Use when changing daemon startup, singleton ownership, shutdown, logging, event subscriptions, lifecycle commands, or the daemon's login-shell environment.

Quality

67%

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 ./.agents/skills/daemon-runtime/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

This is a dense, high-signal internal invariants document: nearly every line encodes non-obvious daemon design rationale anchored to specific files, functions, and regression tests, with nothing wasted on general knowledge. Its weaknesses are structural — monolithic inline detail with no reference files, and topic-based rather than change-workflow-based organization that leaves the sequence for safely executing a modification implicit.

Suggestions

Split the deep protocol detail into per-topic reference files (e.g. references/restart-when-idle.md, references/event-subscriptions.md, references/shellenv.md) and keep SKILL.md as the invariants-plus-pointers overview.

Add a short 'When changing daemon code' sequenced workflow at the top (identify affected area -> apply the listed invariants -> run the named regression tests -> verify guard behavior for destructive commands) to make the validation checkpoints an explicit loop.

Move the long inline regression-test name lists into per-section reference files or a single tests.md index, keeping only one or two sentinel test names inline to cut the densest bullets.

DimensionReasoningScore

Conciseness

Nearly every sentence carries project-specific knowledge Claude could not know (kernel-released singleton locks, SIGTTIN/Setsid rationale, held-push replay ordering) with no padding or explanation of known concepts, matching anchor 4's efficient-with-minor-trim; several bullets are long run-ons packing five-plus facts and long inline test-name lists, keeping it below anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact files and functions ("internal/daemon/lock.go", "waitForDaemonStop", "clearDeadDaemonArtifacts"), commands ("no-mistakes daemon run --root", "update --when-idle"), and hard constants (64 events, 1 MiB, 512 KiB, singletonLockRetry 250ms) — anchor 4's mostly-executable guidance, though it prescribes constraints and rationale rather than copy-paste procedures.

4 / 5

Workflow Clarity

The body is organized by concern, not by sequenced workflow: there is no 'when touching lock.go, do 1-2-3' ordering, and validation checkpoints (named regression tests, the active-runs guard with --force) are attached to individual rules rather than forming an explicit validate-fix-retry loop — anchor 3's structure-present-but-checkpoints-implicit.

3 / 5

Progressive Disclosure

Five clear section headers give real navigation, but no bundle files exist and all deep detail — the full restart-when-idle protocol, shellenv probe mechanics, eventmailbox design — is inlined in a ~180-line SKILL.md, matching anchor 3's 'content that should be separate is inline'; it stays above anchor 2 because the in-body structure is genuinely well-organized.

3 / 5

Total

14

/

20

Passed

Description

56%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 has excellent trigger scoping and distinctiveness for a narrow internal domain, but it is purely a 'Use when' clause: it never states what the skill actually provides. Adding a concrete 'what' (e.g., the invariants, design rationale, and regression tests it holds for daemon changes) would lift it substantially.

Suggestions

Add a leading 'what' clause before the 'Use when' clause, e.g. 'Holds the daemon-runtime invariants, design rationale, and regression-test index for the no-mistakes daemon. Use when changing...'

State the concrete artifacts the skill delivers (singleton-lock rules, logging bounds, event-subscription contract, lifecycle guards, shellenv probing) so the capability is explicit rather than inferred from trigger areas.

Include a few natural synonyms contributors might use, such as 'daemon process', 'IPC health', or 'restart behavior', to broaden trigger coverage beyond the current single-pass listing.

DimensionReasoningScore

Specificity

The description names the domain precisely through seven concrete sub-areas ("daemon startup, singleton ownership, shutdown, logging, event subscriptions, lifecycle commands, or the daemon's login-shell environment") but states only one generic action verb ("changing"), leaving it between anchor 2's minimal actions and anchor 3's 1-2 concrete actions.

3 / 5

Completeness

Only the "when" is present ("Use when changing daemon startup...") with no statement of what the skill does, which anchor 2 explicitly covers as "only 'when' is present without 'what'"; it is not a 3 because the 'what' cannot be inferred under the score-only-what-is-stated guideline.

2 / 5

Trigger Term Quality

Terms like "daemon startup", "shutdown", "logging", and "lifecycle commands" are natural phrases a contributor would say when needing this skill, matching anchor 4's good-but-not-exhaustive coverage; no synonyms or file-path variants are offered, so anchor 5 is not reached.

4 / 5

Distinctiveness Conflict Risk

"Singleton ownership", "event subscriptions", and "login-shell environment" carve out a clear daemon-runtime niche with distinct triggers and minimal overlap risk with other skills, matching anchor 5.

5 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

kunchenguid/no-mistakes

Path

.agents/skills/daemon-runtime/SKILL.md

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.