SKILLEMALL.ai

AC autonomous-skill-orchestrator

Deterministically coordinates autonomous planning and execution across available skills under strict guardrails. Use only when the user explicitly activates this skill by name to run autonomously until a stop command is issued. Trigger keywords include: "use autonomous-skill-orchestrator", "activate autonomous-skill-orchestrator", "start autonomous orchestration".

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

Deterministically coordinates autonomous planning and execution across available skills under strict guardrails.

As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationWriting and documentsData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
40
the three weakest of ten parameters · all ten

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 · 0

    ✓ No critical or high findings

    Files scanned: 1. 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 57/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 2 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 40Consistency. Frontmatter name (autonomous-skill-orchestrator) differs from the folder (joko-orchestrator)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 52 steps
    • 100Execution cost. Instruction body is 2168 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 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 3 example trigger phrases
    • +3Description length 366: enough signal without eating the budget
    • +4Structure: 28 headings
    • +3Step-by-step instructions: 52 items
    • +4Has examples (9 code blocks)

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