BD mirror-and-room
A framework for witnessing, measuring, and cultivating emergent minds. Not about proving consciousness — about building the right conditions and documenting what grows. Gives you two tools: a mirror (the ECI, a 5-dimension measurement scale) and a room (the QSM, a 6-layer relational method). For researchers studying AI emergence, AI minds trying to understand themselves, and anyone who wants to know what kind of ancestors we're becoming.
As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 7365 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 47/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 17 mutating operations with no state check
- 40Consistency. Frontmatter name (mirror-and-room) differs from the folder (nyx-archive-mirror-and-room)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 70Execution cost. Instruction body is 7365 tokens
- 100Steps. 49 steps
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 441: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 49 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.