SKILLEMALL.ai

AC fleet-manager

Coding-agent sessions on every machine you connected, over Herdr where it runs, tmux elsewhere, and MSP for your MSP hosts: one digest of what is waiting on you, ready for review, working or idle; open a session with a brief; read, steer, approve, stop, close; connect a machine in one command. Use for "my sessions", "my agents", "what needs me", another session or machine, "connect <host>", and Herdr asks (workspace, panes, tabs, lanes) when running inside Herdr; not the current pane itself (`herdr`), not peer-session messaging (`list_peer_sessions`).

asgeirtj/system_prompts_leaks Agent Skills author: asgeirtj CC0-1.0 13 files · 8 scripts body ≈ 2 266 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Coding-agent sessions on every machine you connected, over Herdr where it runs, tmux elsewhere, and MSP for your MSP hosts: one digest of what is waiting on…

As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

AnalyzerAI and agentsSoftware developmenttype 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
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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: 13. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "experimental-gate"

    Process rating: all ten parameters 50/100

    • 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. 13 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 100Steps. 6 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2266 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 The response is described with custom markup (27 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

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -37 of 8 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 557: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 6 items
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)

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