SKILLEMALL.ai
GitHub ↗ RU Sign in

AB hook-development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

Galaxy-Dawn/claude-scholar Agent Skills author: Galaxy-Dawn MIT 11 files · 6 scripts body ≈ 3 909 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based…

As a process B 65/100 · Nearly there — weak spots: failures and branches, running it twice

GeneratorAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
96
Quality 40%
97
Run on models
none yet
Process rating
B
65/100
Nearly there
Failures and branches w 10
0
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-Skills

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 4

    ✓ No critical or high findings

    Medium and low: 4
    • low Risky intent intent-offensive-security references/migration.md:66
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      "prompt": "Command: $TOOL_INPUT.command. Analyze for: 1) Destructive operations (rm -rf, dd, mkfs, etc) 2) Privilege escalation (sudo) 3) Network operations without user consent. Return 'approve' or '
      quoted
    • low Risky intent intent-offensive-security references/migration.md:290
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      "prompt": "Validate bash command safety: destructive ops, privilege escalation, network access"
      quoted
    • low Risky intent intent-offensive-security references/migration.md:327
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      echo "Privilege escalation" >&2
      quoted
    • low Risky intent intent-offensive-security references/migration.md:334
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      "Check for privilege escalation (sudo, su, etc)"
      quoted

    Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 65/100

    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 6 mutating operations with no state check
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 85Steps. 93 steps, 2 vague phrases
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3909 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 17 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • -213 emoji in the instructions: noise for the model
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 525: enough signal without eating the budget
    • +4Structure: 52 headings
    • +3Step-by-step instructions: 93 items
    • +3Output format is stated explicitly
    • +4Has examples (32 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +3All 3 scripts are documented

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.