- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jfarcand/mirroir-mcp --skill register-limitation -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jfarcand/mirroir-mcp --skill register-limitation -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jfarcand/mirroir-mcp --skill register-limitation -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add jfarcand/mirroir-mcp --skill register-limitation -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/jfarcand/mirroir-mcp/tree/HEAD/.claude/skills/register-limitationFrom the publisher
Any of these, without exception:
The gates are the Apache-2.0 llm-registre tool,
vendored as the .registre submodule and run by Tier 1 of
runner/scripts/ci/pre-push-validate.sh and by CI (limitation-register.yml).
The register exists so honest gaps become tracked obligations, not so gaps become easy to ship. If you can implement the real thing now, do that instead. Registering is the fallback, and it costs a permanent entry someone has to close later. (A file over the cap or a stray inline allow is never registered — extract the helper or fix the lint.)
Read registre.toml at the repo root — its tracker key names this repo's register. Never
assume; registers are per project. For mirroir that is jfarcand/mirroir-carnet.
grep tracker registre.toml
Never file on the code repo itself. It is PUBLIC, and a limitation issue states precisely where a capability or defence is incomplete — a roadmap when the code is open. Issue bodies may hold reasoning and residual risk; the code comment stays thin.
File it through the carnet skill's script — the one path into the register. It reads the
tracker from registre.toml, refuses a public tracker, prefixes the title [<project>] , and
adds the project label. Pass --label limitation because a marker will point at this issue.
.claude/skills/carnet/carnet.sh create \
--label limitation \
--title "Short statement of the gap" \
--body "Where it is (file + symbol). What is incomplete. What the correct fix looks like."
# → https://github.com/jfarcand/mirroir-carnet/issues/42
# marker: LIMITATION(registre#42): <name the limited item on this line>
Add --claim when you are about to keep working the gap in this session, so a peer sees it
held. The ledger line create writes is also how bilan credits the issue as a registered
limitation rather than work this session owes.
On the comment line that names the limited item:
// LIMITATION(registre#1): device-only step kinds (launch, home, shake,
// reset_app, set_network, measure, condition) have no replay dispatch arm.
Rules that make a marker valid rather than decorative:
registre#<number> — the bare word, never the tracker repo name. The tracker is
configuration (registre.toml); the marker never changes when it moves..registre/limitation-gates.sh --list-files prints what is in), so a marker there is
validated by nothing and never credits the issue as registered. A gap in test coverage
belongs to the production item that goes uncovered: mark that item, where the next person to
change it reads it.Add to feature-phases.yaml (fixed shape — the review workflow parses it with awk):
- name: kebab-case-feature-name
surface: Sources/mirroir-mcp/TheFlag.swift
current: what ships today, i.e. the disarmed state
advance_when: the criterion that arms the next phase
review_by: 2026-09-30
The weekly "Monitor: Feature Phase Review" workflow opens a feature-phase issue in the tracker
once review_by passes, so phase 1 cannot silently become forever. Keep values free of ": "
and " #".
./.registre/limitation-gates.sh
With no arguments it scans the scan_dirs that registre.toml declares. Expect all five gates
green. Tier 1 of runner/scripts/ci/pre-push-validate.sh and CI (limitation-register.yml) run
the same command.
Fix the gap, delete the marker in the same change, close the issue. A stale marker still exempts prose from the gates, so exhausted markers are debt of their own.
These gates are per-change: they stop new debt at authoring time and cannot reach the standing stock of defects that live between diffs — a handler nothing reaches, an override nothing reads, two components each locally correct and jointly wrong. Those come out of periodic adversarial cold-reads and get filed here like anything else. A green gate means no new unregistered debt, not a clean codebase.
Register a known gap in the limitation register — file the issue in the private tracker, write the LIMITATION(registre#n) marker, or ledger a dark-launched feature. Use when the register gates fail, o
---name: register-limitationdescription: Register a known gap in the limitation register — file the issue in the private tracker, write the…---# .claude/skills/register-limitation/SKILL.mdOverview
Register a known gap in the limitation register — file the issue in the private tracker, write the LIMITATION(registre#n) marker, or ledger a dark-launched feature. Use when the register gates fail, or when you are about to document why something is incomplete.
FAQ
Download .claude/skills/register-limitation/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/jfarcand/mirroir-mcp.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.