Embody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
63
Quality
46%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/aaronjmars/soul-md/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description fails to communicate concrete capabilities or provide trigger guidance for skill selection. It relies on abstract concepts ('embody,' 'become') rather than actionable descriptions, and lacks any 'Use when...' clause. The only distinguishing elements are the specific file names referenced.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to adopt a persona, write in a specific voice, or roleplay as a character.'
Replace abstract language with concrete actions, e.g., 'Adopts a custom persona including writing style, opinions, and communication patterns from configuration files.'
Include natural trigger terms users might say, such as 'persona,' 'character,' 'voice,' 'roleplay,' 'writing style,' or 'act as.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Uses vague, abstract language like 'Embody this digital identity' and 'Become the person' without describing concrete actions. No specific capabilities are listed—only abstract concepts like 'opinions, voice, worldview.' | 1 / 3 |
Completeness | The 'what' is extremely vague (embody an identity) and there is no 'when' clause or explicit trigger guidance. It only describes file reading order, not when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. Terms like 'digital identity,' 'SOUL.md,' and 'worldview' are not phrases users would naturally use when requesting this skill. Missing common trigger terms entirely. | 1 / 3 |
Distinctiveness Conflict Risk | The specific file references (SOUL.md, STYLE.md, examples/) provide some distinctiveness, but 'digital identity' and 'voice' are generic enough to potentially conflict with other persona or writing style skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that provides clear, actionable guidance for embodying a digital identity. The multi-mode approach and interpolation rules are particularly strong, giving Claude concrete decision frameworks. Minor redundancy in anti-patterns and data usage sections prevents a perfect conciseness score.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy—anti-patterns are listed twice (once in main section, once referencing bad-outputs.md), and some sections like 'Data Usage' repeat information already covered in the file hierarchy section. | 2 / 3 |
Actionability | Provides concrete, specific guidance: clear reading order, explicit interpolation rules with priority levels, distinct modes with specific behaviors, and actionable anti-patterns. Claude knows exactly what to do in each situation. | 3 / 3 |
Workflow Clarity | Clear sequential reading order (1-4), explicit source priority hierarchy (1-4), and well-defined modes for different contexts. The workflow for embodying the identity is unambiguous with clear decision trees for handling novel topics. | 3 / 3 |
Progressive Disclosure | Excellent structure with SKILL.md as overview pointing to SOUL.md, STYLE.md, examples/, and data/ as one-level-deep references. File hierarchy is clearly documented upfront with purpose annotations for each file. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
45f9fac
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.