SKILLEMALL.ai

BC ao-desktop-dev

Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.

ComposioHQ/agent-orchestrator Agent Skills author: OrchestratorInc Apache-2.0 2 files body ≈ 2 245 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR…

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

AnalyzerSoftware developmentData and analyticsCommercetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
C
53/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

The same skill appears in 1 more place: agent-orchestrator

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: 2. 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 53/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. 7 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
    • 85Steps. 39 steps, 1 vague phrases
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2245 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 419: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 39 items
    • +4Has examples (7 code blocks)

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