AB sdr-project-design
Design, compare, research, and plan SDR projects for OpenClaw. Use when the user wants broad SDR research, beginner orientation, hardware/software selection, or to get any SDR project built in OpenClaw across Linux, Windows, macOS, Raspberry Pi, SBC, server, or mixed host/node setups; extend a radio observatory stack; compare tools like scanner-map, trunk-recorder, rdio-scanner, openwebrx+ (preferred over vanilla OpenWebRX), GQRX, SDR++, SatDump, rtl_433, readsb/tar1090, Dire Wolf, URH, GNU Radio, or SoapySDR; choose OpenClaw-friendly architecture for ingest/decoding/storage/UI; or turn SDR research into a concrete implementation plan.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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: 18. 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 5 branches
- 100Steps. 95 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1920 tokens
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 643: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 95 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (15 of 16)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.