Record the aikido-device-protection skill in the harness mirror¶
- Date: 2026-11-03
- Status: Proposed
- Tags:
tooling|process
Context¶
An aikido-device-protection skill now lives in ~/.claude/skills/. It covers a failure that
looks like an expired token but is not: when Aikido Device Protection blocks a package
install, the registry returns HTTP 403, a connection reset, or a version older than expected.
The skill tells the session to run aikidoctl events --json before it debugs credentials,
edits registry config, switches package managers, or disables TLS verification.
syncing-harness-inventory mirrors ~/.claude into claude/harness/. The 2026-11-03 snapshot
found the skill as a new component. Because a skill was added, the diff is structural, so it
needs an ADR. The same snapshot also updated the GitHub and Linear plugin cache to version
f8c5e7a1dcb7, and settings.json changed.
Decision¶
- Record
skills/aikido-device-protection/SKILL.mdin the harness mirror. - Keep the plugin version bump and the
settings.jsonchange in the same weekly sync, with their own entries inCHANGELOG.md.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
| Exclude the skill from the mirror | The skill has no employer identifiers and no personal prose, so nothing needs excluding. Excluding it would hide a tool the harness depends on. |
Ship the skill with skip-adr |
adr-check requires an ADR for any change to a skill, hook, command or agent. A skip label would be wrong for a structural diff. |
Consequences¶
Positive:
- The mirror shows which tool handles blocked installs, so a future session can find it without rediscovering it.
Negative / Trade-offs:
- The mirror now has one more skill to keep redacted and current.
Ongoing obligations:
- Re-check the skill on each weekly sync. A skill added or removed later needs its own ADR.
ADRs are immutable. If this decision changes, create a new ADR with status "Superseded by" pointing here, and update this record's status.