SKILLEMALL.ai
GitHub ↗ RU Sign in

BC smart-wake

Prevent subagent timeout using checkpoint + cron wake + resume via session spawn mechanism.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 212 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Prevent subagent timeout using checkpoint + cron wake + resume via session spawn mechanism.

As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

ProcedureInfrastructureData and analyticsAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
99
Quality 40%
71
Run on models
none yet
Process rating
C
64/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:114
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "task_id": "smar…00Z",
    detector

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "owner"

Process rating: all ten parameters 64/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 54 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1212 tokens
  • low 10 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 91: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 17 headings
  • +3Step-by-step instructions: 54 items
  • +3Output format is stated explicitly
  • +4Has examples (3 code blocks)

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