digital-brain

This skill should be used for personal operating-system workflows: content creation, voice consistency, relationship lookup, meeting preparation, weekly review, goal tracking, personal brand management, and network management.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/digital-brain-skill/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized with concrete workflows and a sound progressive-disclosure design, but it is padded in places, lacks validation checkpoints on batch/data operations, and references module files that are absent from the provided bundle. Trimming redundant sections, adding verify steps to the JSONL/script workflows, and shipping the referenced module .md files would raise it substantially.

Suggestions

Add an explicit validation/checkpoint step to the append-only and script-driven workflows (e.g., verify the new JSONL entry parses and the schema line is intact before logging), since these are batch operations.

Remove the 'Integration' section and de-duplicate 'Guidelines' against the earlier 'Core Concepts'/'Detailed Topics' content to reduce padding.

Create the referenced module instruction files (identity/IDENTITY.md, content/CONTENT.md, network/NETWORK.md, operations/OPERATIONS.md, agents/AGENTS.md) so the documented progressive-disclosure structure actually exists in the bundle, or adjust the References to point at files that are present.

Dimension	Reasoning	Score
Conciseness	The body is well-structured and avoids lecturing Claude on basics, but it is padded — the 'Integration' section restates context-engineering principles Claude already knows and the 'Guidelines' repeat points made earlier — so it could be meaningfully tightened.	3 / 5
Actionability	Numbered workflows, explicit file paths, and a runnable command (python agents/scripts/weekly_review.py) give mostly executable guidance, though the actual generation logic is delegated to voice.md/templates rather than shown inline.	4 / 5
Workflow Clarity	Multi-step processes are clearly sequenced, but these are batch/data operations (append-only JSONL writes, goal updates, script-driven reviews) with no validation or verify-before-archive checkpoints, which caps batch/destructive workflows at 3.	3 / 5
Progressive Disclosure	The three-level architecture and signaled References section are well designed, but the referenced module files (identity/IDENTITY.md, content/CONTENT.md, etc.) do not exist in the actual bundle — only references/file-formats.md and scripts/install.sh are present — so navigation points at missing files.	3 / 5
	Total	13 / 20 Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, clearly stating both the capability set and an explicit usage clause, but it reads as an activity catalog rather than natural user-facing triggers. Adding concrete trigger phrases ('write a post', 'prepare me for my meeting with X') would lift completeness and trigger-term quality.

Dimension	Reasoning	Score
Specificity	Lists several distinct personal-OS activities (content creation, voice consistency, relationship lookup, meeting preparation, weekly review, goal tracking, personal brand management, network management), though they are activity categories rather than granular concrete operations.	4 / 5
Completeness	Provides a clear 'what' via the enumerated workflow list and an explicit usage clause ('This skill should be used for...'), but the 'when' is a restated activity list lacking concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Good keyword coverage across the workflow domains, but it omits the short natural phrases a user actually utters ('write a post', 'who is [name]') and synonyms/extensions that appear only in the body.	4 / 5
Distinctiveness Conflict Risk	The 'personal operating-system workflows' framing plus the specific activity set carves a clear niche, with only minor overlap risk against dedicated note-taking or CRM skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: muratcankoylan/Agent-Skills-for-Context-Engineering
Path: examples/digital-brain-skill/SKILL.md
Commit: 6dbe1a1

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.