菜单
Use when: adding a meshsa codec, changing JSON/Compact/CoT encoding, wire format, codec registry, Envelope serialization, per-transport codec bridge, or decode compatibility.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | meshsa-add-codec |
| description | Use when: adding a meshsa codec, changing JSON/Compact/CoT encoding, wire format, codec registry, Envelope serialization, per-transport codec bridge, or decode compatibility. |
| argument-hint | Codec name, wire format, schema compatibility, and roundtrip expectations |
Envelope.JsonCodec, CompactCodec, CotCodec, or per-transport encoding.encode(envelope: Envelope) -> bytes and
decode(data: bytes) -> Envelope.@codec_registry.register("name").IncompatibleSchemaError or a
codec-specific MeshSAError path that the router can drop safely.Envelope.kind, msg_id, source_uid, timestamp, and payload fields
unless the codec explicitly maps to a lossy external protocol such as CoT.compact over JSON and document size tradeoffs.packages/meshsa/src/meshsa/codec.pypackages/meshsa/src/meshsa/compact.pypackages/meshsa/src/meshsa/cot.pypackages/meshsa/src/meshsa/router.pypackages/meshsa/tests/test_registry_codec.pypackages/meshsa/tests/test_router_codecs.pyUse when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.
Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.
Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.
Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.
Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.
Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.