digital-brain

This 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.

1.38x

Quality

68%

Does it follow best practices?

Impact

98%

1.38x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/digital-brain/SKILL.md

Quality

Content

65%

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-structured and actionable with concrete paths and commands, but it lacks validation checkpoints in its workflows and references module files that are absent from the provided bundle.

Suggestions

Add an explicit validate/verify checkpoint to batch and append workflows (e.g., confirm a JSONL entry is well-formed after appending before proceeding).

Ensure referenced module files (identity/IDENTITY.md, content/CONTENT.md, network/NETWORK.md, operations/OPERATIONS.md, agents/AGENTS.md) exist in the bundle, or remove the broken references.

Trim the 'Integration' name-dropping and 'Skill Metadata' footer to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is dense and mostly efficient, but the 'Integration' section name-drops context-engineering concepts and the 'Skill Metadata' footer adds filler that does not earn its tokens, so it could be tightened.	2 / 3
Actionability	Workflows use concrete file paths (identity/voice.md, network/contacts.jsonl), a real executable command (python agents/scripts/weekly_review.py), and explicit pipelines (ideas.jsonl → drafts/ → posts.jsonl), giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	Multi-step workflows are clearly numbered and sequenced, but none include explicit validation or verification checkpoints for batch/append operations, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The L1/L2/L3 architecture is well signaled and a References section lists module docs, but the referenced paths (identity/IDENTITY.md, content/CONTENT.md, etc.) do not exist in the actual bundle, so navigation is partly broken.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 has excellent, natural trigger terms and a clear niche, but it front-loads "when" while omitting an explicit statement of what the skill actually does, capping both specificity and completeness at 2.

Suggestions

Lead with a concrete statement of what the skill does (e.g., 'Manages personal brand voice, contacts, content pipeline, and goals'), then keep the trigger phrase list.

Add an explicit 'Use when...' clause paired with the capability list so both 'what' and 'when' are unambiguous.

Dimension	Reasoning	Score
Specificity	The description names the domain ("personal brand, content creation, network management, voice consistency") and surfaces actions only implicitly via trigger phrases, but never states concrete capabilities the skill performs, matching the "names domain and some actions" anchor rather than a full action list.	2 / 3
Completeness	The "when" is explicit and strong ("should be used when the user asks to..."), but the "what does this do" is never stated explicitly, so it does not clearly answer both halves as the level-3 anchor requires.	2 / 3
Trigger Term Quality	Natural, user-spoken phrases like "write a post", "check my voice", "look up contact", "prepare for meeting", and "weekly review" give strong coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The cohesive personal-OS trigger set (voice, contacts, meetings, weekly review, goals) carves a clear niche unlikely to collide with other skills.	3 / 3
	Total	10 / 12 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: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/digital-brain/SKILL.md
Commit: f627ab5

Reviewed: about 8 hours 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.