CtrlK
BlogDocsLog inGet started
Tessl Logo

radio-sdr

Use for authorized RF/SDR security research including signal identification, replay feasibility study in shielded labs, and wireless protocol analysis outside classic Wi-Fi.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/radio-sdr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, concise overview that appropriately offloads detail to a real reference file and gates risky replay operations. Its weaknesses are the lack of executable commands/methodology specifics and missing error-recovery feedback loops for destructive replay.

Suggestions

Add at least one concrete, executable example per analysis stage (e.g., a URH or GNU Radio command/flowgraph snippet for identifying a signal's center frequency and modulation).

Insert an explicit validate→fix→retry loop around replay (e.g., confirm shielded-room + written authorization, attempt, verify captured output matches target before concluding feasibility).

Flesh out the workflow checklist items from abstract labels into specific, ordered actions so each step is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean and token-efficient: short checklist workflow, a compact tool table, and brief sections that assume Claude's knowledge of GNU Radio/URH/Inspectrum without explaining what SDR is.

5 / 5

Actionability

Names concrete tools (RTL-SDR, HackRF, URH, GNU Radio, Inspectrum) and a sequenced checklist, but gives no executable commands or specific methodology steps beyond abstract items like 'GNU Radio / URH 分析', leaving key execution details missing.

3 / 5

Workflow Clarity

A clear sequence exists with permission/gate checkpoints (default RX-only, shielded-room + written permission for replay) and a completion self-check, but there are no explicit validate→fix→retry feedback loops for the potentially destructive replay step, which caps clarity.

3 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single one-level-deep reference (references/sdr-lab-rules.md, which exists) clearly signaled, plus pointers to sibling skills — clean navigation for a simple skill.

5 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and clearly distinct from related wireless skills, explicitly bounding scope to non-Wi-Fi authorized RF/SDR research. Its main weakness is a single-clause 'when' trigger that could enumerate more natural user phrases.

Suggestions

Expand the 'when' clause into explicit trigger phrases users would say, e.g. 'Use when the user mentions SDR, RTL-SDR, HackRF, signal identification, or replay analysis of non-Wi-Fi RF'.

Add common synonyms/hardware terms ('radio', 'spectrum', 'RTL-SDR', 'HackRF') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the RF/SDR domain plus several concrete actions ('signal identification', 'replay feasibility study in shielded labs', 'wireless protocol analysis outside classic Wi-Fi'), which lists multiple specific actions with only minor coverage gaps.

4 / 5

Completeness

Provides both a clear 'what' (the listed research actions) and an explicit 'when' trigger ('Use for authorized RF/SDR security research...'), though the 'when' is a single clause rather than a comprehensive list of trigger phrases.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('RF', 'SDR', 'signal identification', 'replay', 'wireless protocol analysis', 'Wi-Fi') with good coverage, but misses common synonyms like 'radio' or 'spectrum' and specific hardware names.

4 / 5

Distinctiveness Conflict Risk

'outside classic Wi-Fi' explicitly demarcates the niche from Wi-Fi skills and the authorized RF/SDR research framing gives it a clear, distinct trigger with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.