Chain jail
Emperor Time - a full-rigor coding harness skill/plugin: micro-waterfall SDLC gates, scientific-method claim ledgers to cut hallucination, mandatory critique, and consent-based orchestration of other coding agents.
npx -y skills add arbi-elezi/emperor-time --skill chain-jailAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Emperor Time's middle-finger chain — skill capture and binding. Router for five aspects: absence check (is it truly missing?), hunt (find the closest skill on the net), adaptation (conform a captured skill to this harness and workflow), authoring (write one from scratch), and trial-and-register (test in quarantine, then install with provenance). Use when a task needs a capability the harness lacks, or the user asks to find/adapt/make a skill. Load one aspect file at a time per the Invocation Ritual.
SKILL.md
2.5 KB, as published. Nobody here has run it
Chain Jail — router
The chain that binds. Its Limitation is what makes it unbreakable: only legitimate targets — and the captured stay in Zetsu until judged.
Chain Jail acquires abilities the harness lacks. Its power comes from its restriction.
The Limitation (chain-wide law)
- Only the genuinely missing. Capturing what already exists locally (duplicating, re-downloading, NIH-rewriting) is misuse of the chain and a vow breach — which is why every capture starts at the absence check.
- Zetsu until judged. Nothing captured or authored acts on real work before passing its trial.
- Provenance always. Every bound skill carries where it came from, its license, and what was changed.
Selection table — read exactly one
Aspects run in order for a full capture; enter mid-sequence when the earlier steps are already satisfied (and say so in the ledger).
| Your situation | Aspect file |
|---|---|
| A capability seems missing — confirm before anything else | absence-check.md |
| Confirmed missing — search the net for the closest existing skill | hunt.md |
| A candidate is captured — conform it to this harness and workflow | adaptation.md |
| Nothing suitable exists — write the skill from scratch | authoring.md |
| Adapted/authored skill ready — trial it, then install with provenance | trial-and-register.md |
Special case — the missing skill is needed by an enlisted agent, not you:
same sequence, but adapt to that harness's format (adaptation.md has the
per-harness matrix), install into its directory, have that agent run the
trial, and judge its output yourself.
Exit conditions
- Absence check finds a local skill → use/extend it; chain disengages.
- Hunt finds nothing worth adapting → skip to
authoring.md. - Trial fails twice after re-adaptation → release the capture (rejection is recorded with reasons; the need returns to the task as an open constraint).