CtrlK
BlogDocsLog inGet started
Tessl Logo

ac-stop-hook-analyzer

Analyze context and decide on continuation via Stop hook. Use when determining if work should continue, analyzing completion status, making continuation decisions, or implementing the Two-Claude pattern.

61

Quality

71%

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/ac-stop-hook-analyzer/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.

A concise, well-structured skill body with executable Quick Start code and a clean pointer to the implementation script. It is held back by a time-sensitive model-version pin and a Decision Logic section without explicit validation checkpoints.

Suggestions

Remove or generalize the 'Opus 4.5' version pin (e.g., 'a capable long-context model') so the skill does not go stale as models change.

Turn the Decision Logic bullets into an explicit sequence with a validation checkpoint, e.g. 'Validate safety limits; if exceeded, return stop' to make the feedback loop concrete.

Replace the `project_dir` placeholder in Quick Start with an explicit value or a one-line setup note so the example is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean, but 'using Opus 4.5' pins a time-sensitive model version outside any deprecated/old-patterns section, and the Purpose section lightly rehashes the description.

3 / 5

Actionability

Quick Start gives executable code with a concrete return example; minor gap is the undefined `project_dir` placeholder.

4 / 5

Workflow Clarity

Decision Logic lists a four-step sequence but lacks explicit validation checkpoints or a validate-fix-retry feedback loop, leaving checkpoints implicit.

3 / 5

Progressive Disclosure

A short, well-organized overview with a clearly signaled one-level reference to the existing scripts/stop_hook_analyzer.py; fits the simple-skill exception.

5 / 5

Total

15

/

20

Passed

Description

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

A well-structured description that clearly states both capability and trigger conditions with a strong 'Use when' clause. Trigger coverage is good though a few natural user phrasings could be added.

DimensionReasoningScore

Specificity

Names the domain ('continuation via Stop hook') and 1-2 concrete actions ('Analyze context and decide on continuation'), but coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both what ('Analyze context and decide on continuation via Stop hook') and when (a rich 'Use when...' clause with concrete triggers).

5 / 5

Trigger Term Quality

Lists several natural trigger phrases ('determining if work should continue', 'analyzing completion status', 'making continuation decisions', 'Two-Claude pattern'); a few common user phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Niche triggers ('Stop hook', 'Two-Claude pattern') give it a clear distinct identity with only minor overlap risk against general analysis skills.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.