BC proclaw-omni-memory-ultimate-en
Autonomous Intelligent Agent Cognitive Core, integrating 8-layer memory architecture with 4-phase autonomous capabilities: Self-Driven Engine (intrinsic motivation/goal generation) + Self-Evolution Core (cognitive assessment/architecture upgrade) + Self-Learning Engine (question generation/knowledge construction) + Core Axis System (cognitive/value/growth axes/evolution chain/value chain/transaction chain); Use when building intelligent agents with intrinsic drive, proactive evolution, and self-breakthrough capabilities
As a process C 51/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: 41. 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: Autonomous Intelligent Agent Cognitive Core, integrating 8-layer m… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "website" - note
frontmatter-keyunknown frontmatter key "contact" - note
frontmatter-keyunknown frontmatter key "dependency"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (proclaw-omni-memory-ultimate-en) differs from the folder (proclaw-omni-memory-ultimate)
- 100Tools and files. No external tools needed
- 100Steps. 30 steps
- 100Execution cost. Instruction body is 3224 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- -46 reference files, but SKILL.md never points to them: the model will not open them
- -316 of 31 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 525: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.