braindump

Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction

Quality

22%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/braindump/SKILL.md

Quality

Discovery

17%

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 relies on buzzwords like 'intelligent domain classification' and 'competitive intelligence extraction' without explaining concrete actions or when the skill should be triggered. It lacks a 'Use when...' clause and natural user-facing trigger terms, making it difficult for Claude to reliably select this skill from a pool of alternatives.

Suggestions

Add a 'Use when...' clause specifying explicit triggers, e.g., 'Use when the user wants to jot down quick notes, capture ideas, or log competitive insights about market players.'

Replace abstract phrases like 'intelligent domain classification' with concrete actions, e.g., 'Captures quick notes and automatically categorizes them by topic such as product ideas, competitor moves, or market trends.'

Include natural trigger terms users would actually say, such as 'note', 'idea', 'thought', 'competitor', 'market intel', 'brainstorm', 'jot down'.

Dimension	Reasoning	Score
Specificity	Names some actions ('quick capture of raw thoughts', 'domain classification', 'competitive intelligence extraction') but these are somewhat abstract and buzzword-heavy rather than concrete, actionable descriptions of what the skill actually does.	2 / 3
Completeness	Only addresses 'what' at a high level and completely lacks any 'when' clause or explicit trigger guidance. No 'Use when...' or equivalent, which per the rubric caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Uses technical/jargon terms like 'intelligent domain classification' and 'competitive intelligence extraction' that users would rarely say naturally. Missing common trigger terms a user might actually use when needing this skill.	1 / 3
Distinctiveness Conflict Risk	The combination of 'raw thoughts capture' with 'competitive intelligence' is somewhat distinctive, but the vague phrasing could overlap with note-taking skills, brainstorming skills, or market research skills without clear boundaries.	2 / 3
	Total	6 / 12 Passed

Implementation

27%

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

This skill is significantly over-engineered and verbose for what is essentially a thought-capture workflow. It contains substantial sections that are aspirational rather than actionable (learning and adaptation, success metrics, uncertainty handling) and explains concepts Claude already understands (emotional tone assessment, confidence indicators). The core workflow is buried under layers of abstract framework description, and the entire content should be roughly 1/3 its current size with detailed templates and analysis frameworks split into separate reference files.

Suggestions

Cut the skill to ~100 lines by removing sections Claude doesn't need: 'Success Metrics', 'Learning and Adaptation', 'Uncertainty Handling' descriptions, and 'Verification Protocols' — these describe general good practices Claude already knows.

Extract the output templates (braindump template and competitive intelligence template) into separate reference files (e.g., BRAINDUMP-TEMPLATE.md, COMPETITIVE-INTEL-TEMPLATE.md) and reference them from the main skill.

Collapse the 5-phase analysis framework into a concise checklist of what to extract, rather than describing each phase with sub-bullets — Claude knows how to analyze text.

Add a concrete validation step after file creation (e.g., 'Read back the file to verify YAML frontmatter parses correctly') integrated into the workflow sequence rather than in a separate abstract section.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Includes extensive sections Claude doesn't need explained (confidence indicators, uncertainty handling, success metrics, learning and adaptation). The verification protocols, emotional context analysis, and pattern learning sections are abstract filler that inflate token cost without adding actionable value. The template alone is massive and could be significantly condensed.	1 / 3
Actionability	The file path conventions, YAML formatting examples, and output template are concrete and useful. However, much of the 'analysis framework' (Phase 1-5) is descriptive rather than instructive — it lists what to identify without showing how. The competitive intelligence template is concrete but the verification protocols and learning sections are entirely abstract with no executable guidance.	2 / 3
Workflow Clarity	The numbered process flow (steps 1-6) provides a clear sequence, and the pre-flight check with timestamp retrieval is well-structured. However, there are no validation checkpoints after file creation (e.g., verify the file was written correctly, check YAML parses). The 'Verification Protocols' section describes what to verify but doesn't integrate into the workflow as actual checkpoints — they're aspirational rather than procedural.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files for detailed content. The massive output template, competitive intelligence template, all analysis phases, verification protocols, and learning sections are all inline. The competitive intelligence section, verification protocols, and analysis framework could easily be separate reference files. No bundle files exist to offload any of this content.	1 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: huytieu/COG-second-brain
Commit: 034af4c

Reviewed: 18 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.