CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sub-ghz

Sub-GHz RF capture and replay for 433/868/915 MHz ISM-band targets (garage doors, car keys, alarm sensors, weather stations). Covers fixed-code replay with HackRF/Flipper Zero/RTL-SDR, rolling-code analysis with rfcat, signal visualization with inspectrum and Universal Radio Hacker, and encoding/modulation identification.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A highly actionable, well-sequenced operational guide whose commands are executable end-to-end. Its main gaps are implicit rather than explicit validation checkpoints around risky transmission steps, and no progressive disclosure into reference files despite content that would suit them.

DimensionReasoningScore

Conciseness

The body is command-first and largely lean, with only isolated over-explanations of concepts Claude already knows ('OOK (On-Off Keying) = on/off pattern', the rolling-code counter explanation). Most tokens earn their place, so it sits above 'some unnecessary explanation' but below 'every token earns its place'.

4 / 5

Actionability

Guidance is copy-paste executable throughout: hackrf_transfer capture/replay commands, rtl_433 decode invocations, a runnable numpy burst-trimming script, an rfcat TX script, a PT2262 encoder implementation, the RollJam jam-and-capture sequence, and evidence-hashing commands — covering the common fixed- and rolling-code cases.

5 / 5

Workflow Clarity

Phases 1–5 give a clear capture → identify → replay → rolling-code → craft sequence, with Phase 2 parameter identification structurally gating transmission. However, validation checkpoints are implicit rather than explicit — no step verifies decoded bits across captures, confirms the resync window before RollJam, or confirms replay success before logging evidence, so it falls short of the explicit-validation anchor.

4 / 5

Progressive Disclosure

No bundle files exist; all ~280 lines are inline under well-organized, clearly named sections with a References section of external links. Structure is good, but specialized content (the PT2262 crafting code, KeeLoq/RollJam details, the frequency table) is inlined where one-level-deep reference files would keep the overview lean, so it does not reach the well-signaled-references anchor.

4 / 5

Total

17

/

20

Passed

Description

82%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.

A strong, specific description with comprehensive concrete actions, natural trigger terms, and third-person voice. Its single significant weakness is the absence of an explicit 'Use when...' clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions 433/868/915 MHz signals, HackRF, Flipper Zero, RTL-SDR, sub-GHz, garage doors, keyfobs, or signal replay.'

Optionally mention 'rolling code' and 'KeeLoq' in the description body itself (they appear only in metadata.when_to_use) so the when-guidance and visible description stay aligned.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'capture and replay', 'fixed-code replay', 'rolling-code analysis', 'signal visualization', 'encoding/modulation identification' — each tied to named tools, giving comprehensive coverage of the skill's domain.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or any equivalent explicit trigger guidance in the description, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural user-facing terms are comprehensively covered: '433/868/915 MHz', 'HackRF', 'Flipper Zero', 'RTL-SDR', 'garage doors', 'car keys', 'rolling-code', 'Universal Radio Hacker' — exactly what a user would say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

A clear niche (sub-GHz ISM-band capture/replay) with distinct triggers — named hardware (HackRF, Flipper Zero, RTL-SDR, rfcat) and bands — making conflict with sibling skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/iot/sub-ghz/SKILL.md

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.