braindump

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

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 skill is highly actionable thanks to concrete templates, paths, and the date command, but it is monolithic and verbose with verification steps detached from the main workflow. Progressive disclosure is absent — large templates should be factored into reference files.

Suggestions

Move the full braindump and competitive-intel output templates into separate reference files (e.g. references/braindump-template.md) and link to them, keeping SKILL.md as an overview.

Cut aspirational sections ('Success Metrics', 'Learning and Adaptation', 'Pattern Learning') that do not guide execution.

Embed validation checkpoints inside the Process Flow (e.g. after file creation, verify path/frontmatter) rather than listing them only in a separate Verification Protocols section.

Dimension	Reasoning	Score
Conciseness	The body runs ~350 lines for a 'quick capture' skill and includes aspirational padding such as 'Success Metrics' and 'Learning and Adaptation' that add tokens without guiding action; core templates are useful but the whole could be substantially tightened.	2 / 3
Actionability	Provides copy-paste-ready deliverables: an exact `date '+%Y-%m-%d %H:%M'` command, full YAML frontmatter spec, a complete braindump file template, and concrete save paths per domain — concrete and executable despite being instruction-only.	3 / 3
Workflow Clarity	A clear numbered Process Flow (1–6) with a pre-flight check exists, but verification ('Verification Protocols') lives in a separate post-hoc section rather than as embedded checkpoints/feedback loops within the flow.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and everything — including large output templates and the competitive-intel template — is inline in a monolithic SKILL.md; sections are well-organized but content that could be split out is not.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 conveys the skill's purpose and a few concrete capabilities but relies on vague language ('intelligent') and omits any explicit invocation triggers. It is decent but generic, capping most dimensions at 2.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers such as 'brain dump', 'capture thoughts', or 'get ideas out of my head'.

Drop the buzzword 'intelligent' and replace with concrete verbs describing what the classification actually does.

Tighten the action list to specific, observable outcomes (e.g. 'classify thoughts by domain, extract competitive-intel mentions, save a structured note').

Dimension	Reasoning	Score
Specificity	Names the domain (raw-thought capture) and three actions — 'capture of raw thoughts', 'domain classification', 'competitive intelligence extraction' — but they are high-level and padded with the buzzword 'intelligent', so not comprehensive concrete actions.	2 / 3
Completeness	It states what the skill does but has no 'Use when...' clause or explicit trigger guidance; per the judging guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	'capture of raw thoughts' is a reasonably natural phrase, but common user variations like 'brain dump', 'write down ideas', or 'get thoughts out of my head' are absent from the description.	2 / 3
Distinctiveness Conflict Risk	The braindump + competitive-intel niche is somewhat specific, but without explicit triggers in the description it could overlap with general note-taking or capture skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: huytieu/COG-second-brain
Commit: 5e9851c

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