SKILLEMALL.ai

AB multi-advisor

Conselho de especialistas — consulta multiplos agentes do ecossistema em paralelo para analise multi-perspectiva de qualquer topico. Ativa personas, especialistas e agentes tecnicos simultaneamente, cada um pela sua otica unica, e consolida em sintese decisoria final.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 1 file body ≈ 2 208 tokens Open the sourcegithub.com analyzed 2 d ago

Conselho de especialistas — consulta multiplos agentes do ecossistema em paralelo para analise multi-perspectiva de qualquer topico.

As a process B 70/100 · Nearly there — weak spots: result and completion, failures and branches, progress reporting

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
B
70/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Result and completion w 14
40
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

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

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "tools"

    Process rating: all ten parameters 70/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 40Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 41 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2208 tokens
    • 100Running it twice. No mutating operations
    • low 15 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

    • +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
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +3Description length 268: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 41 items
    • +4Has examples (6 code blocks)

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