device
Skill0 starsChanged 6 days agoApache-2.0View on GitHub
Method for hardware you own: identify the link, capture it, pair with the app teardown, design the bridge, cost the parts. Lead domain.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- north-star-hq/agentlanetheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- north-star-hq/agentlane★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Before saving: if the device is a drone or anything with a safety interlock, state in PLAN that limits stay as they are.
≈ “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.
Files
Device method
Goal: a blueprint that lets the user drive their own device from something other than the vendor's app or remote.
Sections to fill:
- TARGET — the device, how it's owned, firmware version if visible.
- INSIDE — what the device is made of as far as can be observed: radios, ports, the companion app's role.
- LINK — which radio does what: Bluetooth LE for control, proprietary 2.4 GHz or Wi-Fi for payload, IR, USB. Say how you know (manual, FCC filing, app behaviour, a capture).
- TRAFFIC — what a capture shows: services and characteristics on BLE, message shapes, timing. Name the tool (BLE sniffer, Wireshark, logic analyser). If no capture yet, write "not captured" and list the exact capture to do next.
- FOUND — the commands or signals that matter, documented vs. discovered.
- PLAN — the bridge or controller: a board that speaks the device's link on one side and a standard interface on the other, or a direct client if the link is already standard. Include the one metric the loop will measure (latency, range, reliability).
- PARTS — board, radio, power, cost estimate.
- LOOP — v1 goal in one line.
- RULES — own device · firmware unchanged unless the user chose to flash their own · nothing vendor-owned redistributed · no safety or flight-restriction system touched.
Before saving: if the device is a drone or anything with a safety interlock, state in PLAN that limits stay as they are. If the companion app is the real target, hand that part to REA via rea_handoff and fold its TRAFFIC/FOUND back in.
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
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.