SKILLEMALL.ai
GitHub ↗ RU Sign in

BB instant-execution-discipline

Revenue-focused execution operating system for agents: converts "do it now" requests into immediate tool actions, enforces strict start/progress/finish SLAs, and prevents kickoff-only false completions. Best for shipping tasks where delay kills conversion (publish/release/distribution).

ClawHub Agent Skills author: 横倉 琉伊 v0.1.6 2 files body ≈ 831 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

GeneratorAI and agentsInfrastructureCommercetype 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
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Revenue-focused execution operating system for agents: converts "d… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 9 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 70Failures and branches. 4 branches
  • 100Tools and files. No external tools needed
  • 100Steps. 49 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 831 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (7 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 287: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 49 items

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

External checks

ClawHub: suspicious
This skill is transparent about speeding up execution, but it should be reviewed because it can push agents to start tools, subagents, cron work, and persistent rule changes before clear approval boundaries are defined.
LLM: suspicious (high) · VirusTotal: benign · 28 May 2026