SKILLEMALL.ai

AC scientific-problem-selection

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".

FreedomIntelligence/OpenClaw-Medical-Skills Agent Skills author: FreedomIntelligence 11 files body ≈ 2 632 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific…

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

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
99/100
safety, quality, tests
Safety 60%
100
Quality 40%
97
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: RA-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: 11. 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

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 2 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 66 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2632 tokens
    • low 12 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)
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 582: enough signal without eating the budget
    • +4Structure: 38 headings
    • +3Step-by-step instructions: 66 items
    • +3Output format is stated explicitly
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (9 of 9)
    • +1License stated

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