SKILLEMALL.ai

AC sysclaw-ops

SysClaw operator skill for processing agent requests and managing the cross-agent communication system. Use when SysClaw needs to check for pending agent requests, review issues, process verdicts, send notifications back to agents, or manage the system_comm database. This is the server-side counterpart to sysclaw-reporting. Triggers on phrases like check agent requests, process notifications, review requests, pending agent requests, agent needs approval.

ClawHub Agent Skills author: Morten Bojer v1.6.2 MIT-0 5 files body ≈ 2 707 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
99
Quality 40%
88
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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 · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Dangerous commands cmd-privilege SKILL.md:231
      Privilege escalation / world-writable permissions (detector / deny-list definition)
      - Dangerous operations (rm -rf, chmod 777)
      detector

    Files scanned: 5. 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 59/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 14 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 35 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2707 tokens
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 458: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 35 items
    • +4Has examples (6 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)

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

    External checks

    ClawHub: suspicious
    This skill is a real operations workflow for a privileged SysClaw agent, but it needs review because it can automatically change databases and run SSH actions on infrastructure.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026