AD agent-soul-system
Create, manage, and validate SOUL.md personality files for multi-agent systems. Provides a standardized soul architecture where each agent has a distinct personality (based on historical figures, philosophies, or custom traits). Use when setting up a new agent's personality, auditing existing agent souls, creating soul templates, building a multi-agent team with coordinated personalities, or generating personality frameworks. Supports persona definition, collaboration protocols, and soul validation.
As a process D 39/100 · Unfinished process — 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 · 3
✓ No critical or high findings
Medium and low: 3
✓ Guard found no suspicious behaviour. 3 matches are attack strings quoted in this security skill's own documentation.
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 39/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (agent-soul-system) differs from the folder (jarvis-soul-system)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 714 tokens
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 504: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.