agentleFS
Sign inStart free
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/wireless-telemetry/SKILL.md

wireless-telemetry

Skill28 starsChanged 29 days agoMITView on GitHub

Design and diagnose embedded telemetry, packet freshness and wireless coexistence using UDP, ESP-NOW or a serial bridge. Use when users need AP+STA operation, low-latency data, sequence/boot identifiers, packet-loss analysis or bench-control leases. Do not use for generic web networking, ordinary serial logs or to promise RF latency without measurements.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the shared contract. Identify exact MCU/framework, endpoints, topology, payload size, cadence, channel, power-save policy and …

    line 14
  2. Distinctive:

    Keep callback work bounded.

    line 21
  3. Distinctive:

    Use the single bench-control contract when driving is in scope.

    line 26
  4. Very specific:

    Test missing/corrupt/replayed packets, reconnects, boot resets, queue pressure and channel changes.

    line 35
  5. Very specific:

    Run the package's test_embedded_workflows.py suite and the host tests/lease_guard_test.cpp.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wireless Telemetry

Produce a transport/freshness contract and a reproducible measurement plan. Separate telemetry observation, command authority and radio delivery.

Workflow

  1. Read the shared contract. Identify exact MCU/framework, endpoints, topology, payload size, cadence, channel, power-save policy and security/provisioning requirements.
  2. Select the transport from constraints, not a latency slogan. UDP is useful for freshest state; reliable streams have different backlog semantics. ESP-NOW needs target-version payload/channel/peer/security checks. Read coexistence and measurement.
  3. Keep callback work bounded; defer heavy processing. Specify queue depth, overflow/drop behavior and data age. Networking must not own actuator outputs.
  4. Define protocol version, stream identity, boot/session identity, sequence width/wrap, clock basis and authentication/replay behavior. A checksum is not authentication. A send callback does not establish application receipt.
  5. Use the single bench-control contract when driving is in scope. Autonomous operation rejects steering; expired, stale or replayed commands never renew authority. STOP and fresh re-arm are separate from reconnecting a dashboard.
  6. Record endpoints, units, duration, workload, samples and completeness. Use uv run scripts/analyze_trace.py TRACE.csv for the explicit trace schema. It reports observed forward gaps, duplicates, late/stale sequence events, receive intervals and same-clock RTT. It never calculates loss rate or unsynchronized one-way latency.
  7. Test missing/corrupt/replayed packets, reconnects, boot resets, queue pressure and channel changes. Host traces prove analysis/protocol logic only; label RF, device deadline and actuator-stop behavior unverified until measured.

Integration and verification

arduino-serial-monitor owns serial capture and desktop-console integration; this skill owns wireless interpretation. realtime-control-design owns the control budget; ota-deployment-guardian owns updating. Do not duplicate live dashboards, transport drivers or schedulers here.

Run the package's test_embedded_workflows.py suite and the host tests/lease_guard_test.cpp. See source lessons. Deliver the measured/assumed distinction, actual valid/rejected samples, scope of supported clocks/protocols and recovery/security notes from the shared contract. CPU affinity, AP setup and a successful compile are not low-loss or low-latency proof.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free