CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

concept-synthesis

Deduplicate and synthesize raw concept stubs into a tiered intellectual map (T1 Canon to T4 Riff), tracing idea evolution across sources over time. Transforms thousands of raw concept pages into a curated intellectual fingerprint. Includes a reversible curation cull pass (Phase 5) with hard keep/delete/merge verdicts, substance gates, grounding labels, cluster budgets, and merge-with-backlinks salience promotion.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/concept-synthesis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

A strong, well-sequenced instruction skill: the five-phase pipeline is concrete and executable, and destructive operations are unusually well-guarded with validation gates, reversibility, and explicit error recovery. Its main costs are repetition (reversibility and test-before-bulk restated multiple times) and a monolithic inline Phase 5 rubric that inflates token cost without adding navigation value.

Suggestions

Move the Phase 5 cull rubric (6-axis tables, verdict thresholds, grounding labels, cluster budgets) into a reference file (e.g., references/cull-rubric.md) and keep a short summary plus the merge mechanics in SKILL.md, cutting the body roughly in half.

Deduplicate repeated assertions: state reversibility and test-before-bulk once each (plus one Anti-Patterns entry) instead of restating them across sections, and drop or compress the 'Contract'/'Output Format' conformance-test boilerplate.

Provide at least one concrete prompt template for the LLM distinctness judge and the T1/T2 synthesis pass so those steps are copy-paste executable like the gbrain commands.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific judgment criteria Claude could not know (6-axis cull rubric, grounding labels, cluster budgets), but it repeats itself: reversibility is restated roughly five times, test-before-bulk three times, and the distinctness-guard 'hard veto' appears both in the merge section and again in Anti-Patterns; the trailing 'Contract' and 'Output Format' sections exist only 'for the conformance test'. Not 4 — these are several padded passages, not minor trimmable instances.

3 / 5

Actionability

Concrete executable commands throughout ('gbrain query "type:concept" --limit 10000 --json', get/put/delete/restore/history/revert, 'gbrain pricing set'), plus exact frontmatter schemas, numeric verdict thresholds (≥85% ELITE, <55% DELETE), and full output templates. Not 5 because the LLM-judge and synthesis passes are directed ('LLM: are these the same idea?') without copy-paste-ready prompts, though the refusal to hardcode a similarity threshold is explicitly justified.

4 / 5

Workflow Clarity

Phases 1-5 are explicitly sequenced, and this destructive/batch skill has real validation checkpoints: the merge-quality gate that rejects half-merges, the logged distinctness-guard veto, spot-check count reduction, a 3-5-cluster test-before-bulk probe, three explicit undo paths, and per-error recovery (resume_command, revision_conflict re-read). Clear sequence with explicit feedback loops; the destructive-operation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and external references (../conventions/quality.md, test-before-bulk.md, agent-operator-protocol.md, _brain-filing-rules.md) are one level deep and clearly signaled in blockquotes at point of use, with well-organized section headers. Not 5 because the ~200-line Phase 5 cull rubric is inlined monolithically where a reference file would keep SKILL.md an overview, and the conformance-test boilerplate pads the tail.

4 / 5

Total

16

/

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.

A highly specific, well-voiced description that comprehensively enumerates the skill's capabilities and occupies a distinct niche. Its one structural weakness is the missing explicit 'when to use' guidance within the description itself, which caps completeness at 3 even though trigger phrases exist in the frontmatter triggers list.

Suggestions

Append a 'Use when...' sentence to the description (e.g., 'Use when the user asks to synthesize, cull, or map their concepts, trace how an idea evolved, or decide which concepts to keep') so both 'what' and 'when' are answered in the description text.

Fold 1-2 natural user phrasings (e.g., 'my notes', 'my ideas') into the description to broaden trigger-term coverage beyond the frontmatter triggers list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full pipeline — 'Deduplicate and synthesize raw concept stubs into a tiered intellectual map (T1 Canon to T4 Riff), tracing idea evolution across sources over time' plus 'hard keep/delete/merge verdicts, substance gates, grounding labels, cluster budgets, and merge-with-backlinks salience promotion' — in third-person voice. Comprehensive coverage of capabilities; not 4, which reserves room for coverage gaps.

5 / 5

Completeness

The 'what' is clear and detailed, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — usage timing lives only in the frontmatter triggers list. Per the rubric guideline this caps completeness at 3; not 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Good natural-keyword coverage ('concept stubs', 'synthesize', 'cull', 'intellectual map'), but common user phrasings like 'notes', 'ideas', or 'find patterns' appear only in the separate triggers list, not the description itself. Not 5 because synonym coverage within the description text is incomplete.

4 / 5

Distinctiveness Conflict Risk

'Concept stubs', 'tiered intellectual map (T1 Canon to T4 Riff)', and 'curation cull' carve out a clear niche distinct from sibling ingestion skills (signal-detector, idea-ingest, voice-note-ingest create stubs; this skill synthesizes them). Minimal conflict risk; not 4 because the vocabulary and function are unmistakably specific.

5 / 5

Total

17

/

20

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

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (522 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 5 missing, 6 suspicious

Warning

Total

13

/

16

Passed

Repository

garrytan/gbrain

Path

skills/concept-synthesis/SKILL.md

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.