BC self
Organic personality development through self-observation with lightweight reliability guards. This skill helps an agent build a real, evolving self-model over time (SELF.md) while preserving core identity boundaries (SOUL.md). It solves the common failure mode where reflection frameworks start strong but silently stall by adding minimal cadence and trigger checks: schedule the check, not the content. Entries are only written when meaningful signals exist (hard/soft triggers + quality gate), preventing forced journaling and routine filler. Use when (1) establishing persistent personality growth, (2) reviving stale SELF.md systems, (3) introducing heartbeat-based reflection checks without losing authenticity, (4) running weekly/monthly pattern consolidation, (5) distinguishing genuine behavioral shifts from noise, or (6) replacing heavier self-reflection/consciousness stacks with a lean, practical model.
As a process C 57/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Organic personality development through self-observation with ligh… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 790 tokens
- low 10 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)
- +3Description length 915: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 17 headings
- +3Step-by-step instructions: 43 items
- +4Reference files are cited in the instructions (4 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.