SKILLEMALL.ai

AF opcode

Zero-token execution layer for AI agents. Define workflows once, run them free forever — persistent, scheduled, deterministic. 6 MCP tools over SSE. Supports DAG-based execution, 6 step types (action, condition, loop, parallel, wait, reasoning), 26 built-in actions, ${{}} interpolation, reasoning nodes for human-in-the-loop decisions, and secret vault. Use when defining workflows, running templates, checking status, sending signals, querying workflow history, or visualizing DAGs.

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files body ≈ 4 630 tokens Open the sourcegithub.com analyzed 2 d ago

Zero-token execution layer for AI agents.

As a process F 43/100 · Will not run — References files that are not bundled: ../../docs/benchmarks.md

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: ../../docs/benchmarks.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/benchmarks.md

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../../docs/benchmarks.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/benchmarks.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 9 mutating operations with no state check
  • 70Execution cost. Instruction body is 4630 tokens
  • 100Steps. 17 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 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
  • -2localhost URLs: will not work for another user
  • +2Single-language instructions
  • +3Description length 484: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (13 code blocks)
  • +4Reference files are cited in the instructions (6 of 6)
  • +1License stated

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