digital-brain
tessl i github:muratcankoylan/Agent-Skills-for-Context-Engineering --skill digital-brainThis skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
57%This skill demonstrates strong organizational structure and progressive disclosure, making it easy to navigate a complex personal operating system. However, it sacrifices actionability by describing workflows abstractly rather than providing executable examples, and lacks validation checkpoints for data operations. The content could be tightened by removing explanatory sections about file formats and architecture that Claude already understands.
Suggestions
Add executable code examples for common operations (e.g., actual Python/jq commands to append to JSONL files, search contacts, read voice.md)
Include validation steps in workflows: how to verify JSONL append succeeded, what to do if contact lookup returns empty, how to confirm voice.md was properly loaded
Remove or condense the 'File Format Strategy' and 'Progressive Disclosure Architecture' sections - Claude understands these concepts and they consume tokens without adding actionable value
Add example input/output for the JSONL operations showing the exact JSON structure expected when logging posts or interactions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanations (e.g., explaining what JSONL/YAML/Markdown are for, the 'Core Concepts' section explaining progressive disclosure architecture that Claude understands). The module overview and file format strategy sections add bulk without proportional value. | 2 / 3 |
Actionability | Workflows are listed as numbered steps but lack executable code examples. The 'Content Creation Workflow' and 'Pre-Meeting Preparation' sections describe what to do but don't show concrete commands or code snippets for file operations. Python script references exist but no actual usage examples with expected outputs. | 2 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (content creation, meeting prep, weekly review), but validation checkpoints are missing. There's no guidance on what to do if a contact isn't found, if voice.md is malformed, or how to verify successful JSONL appends. The 'append-only' rule is stated but no verification step is provided. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to module-specific documentation. The skill explicitly states 'Only load what's needed for the current task' and provides a clean module overview table with well-signaled links to detailed docs (IDENTITY.md, CONTENT.md, etc.). | 3 / 3 |
Total | 9 / 12 Passed |
Activation
30%This description is fundamentally flawed because it only specifies when to use the skill without ever explaining what the skill does. While it has good trigger term coverage, the complete absence of capability descriptions makes it impossible to understand the skill's purpose. The broad, overlapping triggers would cause conflicts with numerous other skills.
Suggestions
Add a clear 'what' statement at the beginning describing specific capabilities (e.g., 'Manages personal branding by drafting social media posts, maintaining voice consistency guidelines, and organizing professional contacts.')
Narrow the scope to reduce conflict risk - currently covers at least 4-5 distinct domains (content writing, voice analysis, contact management, meeting prep, goal tracking) that should likely be separate skills
Restructure to follow the pattern: '[Specific capabilities]. Use when [triggers]' rather than leading with triggers alone
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only trigger phrases. It never explains what the skill actually does, using only vague references like 'personal brand, content creation, network management' without specifying any capabilities. | 1 / 3 |
Completeness | The description only addresses 'when' (trigger conditions) but completely omits 'what' the skill does. There is no explanation of capabilities, features, or actions the skill performs. | 1 / 3 |
Trigger Term Quality | Includes many natural trigger phrases users would say: 'write a post', 'check my voice', 'look up contact', 'prepare for meeting', 'weekly review', 'track goals'. These are conversational and cover multiple use cases. | 3 / 3 |
Distinctiveness Conflict Risk | The triggers are extremely broad and would conflict with many other skills - 'write a post' could match any writing skill, 'track goals' any productivity skill, 'prepare for meeting' any calendar/meeting skill. No clear niche is established. | 1 / 3 |
Total | 6 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
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.