CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

process-lifecycle

Use when changing subprocess execution, cancellation, process-tree cleanup, orphan reaping, or Windows child hardening.

Quality

65%

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/process-lifecycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 an information-dense internal ruleset with excellent actionability — exact function names, settings, and guarding tests for every rule. Its weaknesses are structural: monolithic paragraph-length bullets, some generic advice, and inlined deep-dive material (Windows console handling, procreap) that should live in reference files.

Suggestions

Split the Windows console/manifest bullet and the procreap bullet into reference files (e.g. references/windows-console.md, references/procreap.md) and keep a 1-2 line summary with a clearly signaled link in SKILL.md.

Trim regression-test enumerations to the one or two most representative tests per rule to cut token load while preserving verification pointers.

Replace the generic sync/atomic bullet with project-specific concurrency pitfalls, or delete it, since it restates knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is packed with project-specific, non-inferable facts, but several bullets run 300+ words as single paragraphs, regression-test names are enumerated exhaustively, and bullets like "Protect shared mutable state with the standard sync/atomic tools" restate knowledge Claude already has. Mostly valuable content that could be meaningfully tightened, matching anchor 3.

3 / 5

Actionability

Guidance is highly concrete with exact identifiers ("shellenv.ConfigureShellCommand", "winproc.Harden(cmd)", "make winres", "DisallowStartIfOnBatteries... false") and named regression tests. It stops short of anchor 5 because no usage examples or call signatures are shown — Claude must look each API up in internal/shellenv.

4 / 5

Workflow Clarity

Each rule pairs a directive with named regression tests (e.g. "Regressions: TestConfigureCooperativeShellCommandCancelAllowsCleanup"), providing verification checkpoints, and per-scenario routing (agents vs repository commands vs one-shot) is unambiguous. It lacks an explicit ordered sequence or run-fix-revalidate feedback loop, so anchor 4 fits better than 5.

4 / 5

Progressive Disclosure

There is topical structure (one bullet per concern) and one good delegation ("the helper doc comments in internal/shellenv own the details"), but the Windows console-hardening and procreap bullets are inlined essays that clearly belong in separate reference files, and no headers or bundle files aid navigation. Anchor 3's 'content that should be separate is inline' matches.

3 / 5

Total

14

/

20

Passed

Description

52%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 a strong, explicit trigger clause with specific, natural technical terms and low conflict risk, but it omits any statement of what the skill actually does or contains. Adding a capability clause before the "Use when" clause would materially raise completeness and specificity.

Suggestions

Add a leading 'what' clause, e.g. "Provides rules for routing subprocesses through shellenv lifecycle configurators, reaping leaked process trees, and hardening Windows children" before the "Use when" trigger list.

State 1-2 concrete capabilities (e.g. "kills whole process trees on cancellation, sweeps orphaned processes from run worktrees") so specificity reflects actions, not just trigger topics.

Consider adding synonyms users might say, such as "child processes" or "kill the process tree", to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names several concrete domains ("subprocess execution, cancellation, process-tree cleanup, orphan reaping, or Windows child hardening") but states no capability actions — it is purely a trigger list. It exceeds anchor 2's generic domain naming because the topics are specific, but falls short of anchor 4 because no actions the skill performs are listed.

3 / 5

Completeness

Only the "when" is present ("Use when changing...") with no statement of what the skill does — matching anchor 2's "only 'when' is present without 'what'". It cannot score 3 because anchor 3 requires a clear 'what', which is never explicitly stated.

2 / 5

Trigger Term Quality

Phrases like "subprocess execution", "cancellation", "orphan reaping", and "Windows child hardening" are natural terms a developer would use when touching this code. Common variations such as "kill child processes", "zombie processes", or "job objects" are missing, which keeps it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Process-lifecycle management is a clear niche with distinct triggers (orphan reaping, process-tree cleanup), but "subprocess execution" and "cancellation" are broad enough to overlap with a general concurrency or subprocess skill. Minor overlap risk places it at anchor 4 rather than anchor 5's minimal-conflict bar.

4 / 5

Total

13

/

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/process-lifecycle/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.