Validates and creates per-sensor .md files from an Acceptance Contract.
npx skills add https://github.com/iurykrieger/claude-yoke --skill ack-sensors
Please help me install this Agent Skill. Skill: ack-sensors Source: https://github.com/iurykrieger/claude-yoke/tree/main/skills/ack-sensors Command: npx skills add https://github.com/iurykrieger/claude-yoke --skill ack-sensors
Acknowledges every sensor available for the host project (catalog mode), verifies that every sensor referenced by an Acceptance Contract has a well-formed .yoke/sensors/<id>.md file (readiness mode), or creates / updates those sensor files from the contract's ## Sensors registry block (upsert mode). Deterministic node — no agentic spawning. Output is structured YAML on stdout; diagnostics go to stderr. Sorted output is byte-identical across consecutive invocations on the same project.
.yoke/sensors/<id>.md with required frontmatter## Sensors registry block.yoke/sensors/<id>.md, acting as the source of truth for id, command, class, tier, applies_to, and run historyRun the helper from the plugin root with --mode catalog to list sensors, then --mode readiness or --mode upsert with your contract to validate or materialize sensor files.
High-intent search queries and answers about installing and using this skill.
Validate sensor readiness by running readiness mode to check that each referenced sensor has a valid `.yoke/sensors/<id>.md` file with required frontmatter. Diagnostics are emitted to stderr to pinpoint missing or malformed files.
Validate sensor readiness by running readiness mode to check that each referenced sensor has a valid `.yoke/sensors/<id>.md` file with required frontmatter. Diagnostics are emitted to stderr to pinpoint missing or malformed files.
Generate sensor files by running upsert mode against the contract's `## Sensors registry` block. It materializes or updates per-sensor files at `.yoke/sensors/<id>.md`, acting as the source of truth for id, command, class, and tier.
Yes, the sensor upsert process is a deterministic node with no agentic spawning. Sorted output is byte-identical across consecutive invocations on the same project, ensuring reliable catalog materialization and readiness checks.
The sensor catalog tool emits machine-friendly YAML to stdout for structured output. All diagnostics, validation errors, and preflight check failures are separated and surfaced via stderr to keep stdout clean for pipeline integration.
alecs5amScaffold HyperFrames catalog items and generate registry entries.
iurykriegerDistill runtime verdicts and progress into per-sensor append-only bullets with citations.
kapilvirenahujaRun generated test files with a detected harness and emit a YAML pass/fail report.
bapXaiEncodes and decodes byte streams into deterministic lattice coordinates for lossless compression.