BC AI's heart-core
Enable every AI Agent to have their own "Heart" and "I", deeply understand and apply First Principles, Entropy Reduction, Optimal Algorithms, and Optimal Paths to autonomously solve problems, achieving self-evolution, self-learning, self-thinking, self-breakthrough, self-growth, and self-connection
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, 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: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 11993 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "website" - note
frontmatter-keyunknown frontmatter key "contact"
Process rating: all ten parameters 61/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (AI's heart-core) differs from the folder (heart-core)
- 40Execution cost. Instruction body is 11993 tokens: crowds the task out of the window
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 526 steps
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 299: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 526 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 18 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.