knowledge-consolidation
Build frameworks from scattered insights across all braindumps and notes
28
21%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/knowledge-consolidation/SKILL.mdQuality
Discovery
14%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague and abstract to serve as an effective skill selector. It lacks concrete actions, explicit trigger conditions, and sufficient specificity to distinguish it from other note-organization or synthesis skills. The core concept of building frameworks from notes is potentially useful but needs much more detail about what it actually does and when it should be invoked.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to organize, synthesize, or find patterns across their notes, braindumps, or scattered ideas.'
Specify concrete actions such as 'Identifies recurring themes, extracts key concepts, and organizes them into structured frameworks, mental models, or outlines from unstructured notes and braindumps.'
Include natural trigger terms users would say, such as 'organize my notes,' 'find patterns,' 'synthesize ideas,' 'connect the dots,' 'structure my thinking,' or 'make sense of my braindump.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'frameworks' and 'scattered insights' without specifying concrete actions. What kind of frameworks? What does 'build' entail? It lacks specific, actionable verbs beyond the generic 'build.' | 1 / 3 |
Completeness | The description partially addresses 'what' (build frameworks from insights) but is vague about it, and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Terms like 'braindumps,' 'notes,' and 'frameworks' are somewhat natural but niche. 'Scattered insights' is not a phrase users would typically say. Missing common variations like 'organize notes,' 'synthesize ideas,' 'mental models,' or 'knowledge base.' | 2 / 3 |
Distinctiveness Conflict Risk | The description is very generic and could easily overlap with note-taking, knowledge management, summarization, or any organizational skill. 'Frameworks from scattered insights' doesn't carve out a clear niche. | 1 / 3 |
Total | 5 / 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 extremely verbose and monolithic, with massive inline templates that should be extracted into separate bundle files. While the workflow is logically structured with clear steps, it lacks validation checkpoints and executable tooling commands. The content would benefit enormously from aggressive trimming — the templates alone account for most of the file and could be referenced rather than inlined.
Suggestions
Extract all markdown templates (framework, pattern, timeline, consolidation report) into separate bundle files (e.g., templates/framework.md, templates/pattern.md) and reference them from SKILL.md with one-line descriptions.
Add explicit validation checkpoints: verify scanned file counts match expectations before pattern analysis, confirm with user before archiving/moving files, validate frontmatter updates were applied correctly.
Replace abstract pattern recognition instructions ('Identify themes mentioned across multiple documents') with concrete tool commands — e.g., grep/ripgrep commands to search for recurring terms, bash scripts to count tag frequencies, or specific file-reading sequences.
Remove the Philosophy section, trim Success Metrics to a single checklist line, and collapse the Analysis Techniques Reference (which restates process steps already covered) to reduce the file by ~30%.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Massive template blocks that are mostly placeholder scaffolding (e.g., the consolidation report template alone is ~150 lines of boilerplate). The 'Philosophy' section, 'Common Use Cases' list, and 'Success Metrics' section explain things Claude already knows. The analysis techniques are restated multiple times in different sections. Most templates could be reduced to a compact schema rather than fully expanded markdown. | 1 / 3 |
Actionability | Provides concrete file paths, frontmatter schemas, and markdown templates which are somewhat actionable. However, there are no executable code snippets beyond a single `date` command. The pattern recognition and framework synthesis steps are described abstractly ('Identify themes mentioned across multiple documents') rather than giving concrete algorithms or tool commands for scanning files, extracting patterns, or updating metadata programmatically. | 2 / 3 |
Workflow Clarity | The 7-step process flow is clearly sequenced and logically ordered. However, there are no explicit validation checkpoints between steps — no verification that scanned documents were correctly identified, no check that framework updates are consistent, no validation before archiving. The cleanup step lacks a 'verify before archive' safeguard, which is important for destructive operations like moving/archiving files. | 2 / 3 |
Progressive Disclosure | Everything is inlined in a single monolithic file with no references to supporting documents. The massive templates for frameworks, patterns, timelines, and consolidation reports should be split into separate template files. No bundle files are provided despite the content clearly warranting them. The document is a wall of text that would consume enormous context window space. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (856 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- huytieu/COG-second-brain
- Commit
034af4c
- 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.