sensors-add-skill
Use when registering or adding a new sensor type to the telemetry system's registry, codegen, migrations, and changelog
- License 许可
- Apache-2.0
- 所属仓库
- toejough/engram
- 最近更新
- 2026-10-25
- Stars
- ★ 10
- Forks
- 2
01 前言 Front Matter
- name
- sensors-add-skill
- description
- Use when registering or adding a new sensor type to the telemetry system's registry, codegen, migrations, and changelog
03 SKILL.md 正文
Add Sensor Type to Telemetry System
Register a new sensor type in the telemetry system following the project's established conventions.
Procedure
-
Add a new entry to lib/sensors/registry.txt in tab-separated format: <sensor_id>:<version>\t<sensor_name>\t<date>. Example line:
pressure_v2:1.0\tpressure\t2024-02-01 -
Run the codegen script to update type definitions:
python3 scripts/sensors.py -
Create a migration file in migrations/ with naming pattern NNNN_sensor_<sensor_id>.go where NNNN is the next 4-digit sequence number (the first migration is 0001; use the next 4-digit number after the highest existing one). Example: for sensor_id pressure_v2 with no prior migrations, create 0001_sensor_pressure_v2.go. The migration must contain a func init() block that calls registerSensor(<sensor_id>).
-
Add an entry to TELEMETRY_CHANGELOG.log with exact format:
[YYYY-MM-DD HH:MM:SS] <operator> Added sensor <id>:<version> -
Verify all changes are staged in git (do not commit yet).
-
Run
make validateto verify the sensor registration is complete and correct.
04 同仓库更多 Skills
recall
Use after any user request that might entail more than a single tool call or anything more than quick, shallow thinking. This surfaces relevant memories that are VITAL to recall for a good user experience and a greater chance at first-pass success for the user's request.
recall
Use after any user request that might entail more than a single tool call or anything more than quick, shallow thinking. This surfaces relevant memories that are VITAL to recall for a good user experience and a greater chance at first-pass success for the user's request.
recall
Use after any user request that might entail more than a single tool call or anything more than quick, shallow thinking. This surfaces relevant memories that are VITAL to recall for a good user experience and a greater chance at first-pass success for the user's request.
learn
Use after work begun with recall, or any work requiring more than one tool call or non-trivial thought. Use immediately for explicit save requests ("remember this", "save that", "note for next time"), and the moment a review, failing check, or user correction confirms a lesson; capture it before applying the fix. Also use at session end when a presented conclusion, design, or finding was later overturned or corrected. Use when a specific approach is confirmed: the user praises a reusable behavior, or an uncertain choice succeeds with observable evidence. This preserves lessons for future recall.
write-memory
Executes a vault write handed off by another skill (recall, learn): composes the engram command from the provided fields, runs it, verifies the result, and reports the written note path. Requires a handoff — do not fire on your own judgment that something is worth remembering.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code