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

74%

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 ./plugin-variants/gbrain-coding/skills/concept-synthesis/SKILL.md

The canonical home for this skill is concept-synthesis in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-architected, highly actionable body with excellent sequencing and unusually thorough validation and reversibility for a destructive batch workflow — its strongest points. The weaknesses are repetition of the same guardrails in multiple sections (conciseness) and a monolithic single-file layout where the Phase 5 rubric and output templates would be better split into reference files (progressive disclosure).

Suggestions

State the distinctness-guard / qualitative-merge-band rules once (in the merge section) and have the anti-patterns and quality gates reference that statement instead of restating it — this would cut substantial duplicated text.

Split the Phase 5 cull rubric (axis tables, verdict/gate logic, merge mechanics) into references/cull-rubric.md and the output page templates into references/output-format.md, keeping SKILL.md as the phase overview and pointing to them explicitly.

Make Phases 1–4 as executable as Phase 5: specify the dedup procedure (Jaccard computation, substring rule) and the Phase 2 scoring/tier-assignment formula concretely, mirroring the precision of the Phase 5 verdict table.

DimensionReasoningScore

Conciseness

The body is mostly skill-specific, non-obvious content (verdict tables, merge mechanics, undo paths) rather than explanation of things Claude already knows, but it is noticeably repetitive: the distinctness-guard / don't-merge-on-similarity rule is stated at least four times ("Distinctness guard is a HARD VETO", "Finding merge candidates — qualitative bands", and two anti-patterns), and the Cull-quality gates restate rules already given inline. This matches anchor 3 (mostly efficient but could be tightened); it is not 2 because there is no padded generic explanation, and not 4 because the repetition is systematic rather than a couple of stray sentences.

3 / 5

Actionability

Phase 5 is fully executable — copy-paste `gbrain` command sequences, an exact weighted scoring formula ("(Insight + Originality + Specificity) × 2 + ... Max = 45"), verdict thresholds, and complete output templates. However, Phases 1–4 are only sketched: the Invocation block says the "agent applies Jaccard + substring locally" without a procedure or formula, and no composite_score computation or numeric tier-assignment thresholds are given. That matches anchor 4 (mostly executable, minor gaps) rather than 5.

4 / 5

Workflow Clarity

The five phases are clearly sequenced in the Architecture diagram and body, and — critical for a destructive batch operation — validation is extensive and explicit: test-before-bulk spot-check of 3–5 clusters, the merge-quality gate rejecting half-merges, hard-DELETE triggers and gates, full reversibility via `_merged/` archive + soft-delete + version history with undo commands, a quality-gates checklist, and an error-recovery protocol (cost cap resume, revision_conflict re-read). This matches anchor 5 (explicit validation, feedback loops, checklists); the destructive-operation cap does not apply because validation is present throughout.

5 / 5

Progressive Disclosure

Section structure is clear and the external references (conventions/quality.md, conventions/test-before-bulk.md, conventions/agent-operator-protocol.md) are well-signaled one-level-deep links. However, the entire skill is a single ~500-line SKILL.md with no bundle files at all: the full Phase 5 cull rubric (six axis tables, verdict logic, merge mechanics) and the output page templates are exactly the content that belongs in separate reference files. That matches anchor 3 (content that should be separate is inline); it is not 4 because the lack of any split is a structural gap, not a minor one, and not 2 because the inlined content is well-sectioned and references are clearly signaled rather than buried.

3 / 5

Total

15

/

20

Passed

Description

70%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 dense, highly specific description that clearly communicates what the skill does with strong domain distinctiveness. Its main weakness is the absence of an explicit "Use when..." clause inside the description field itself — routing guidance exists only in separate frontmatter fields. The description is also somewhat jargon-heavy in its third sentence, though the terms are skill-defined rather than vague.

Suggestions

Append a "Use when..." clause to the description field itself (e.g., "Use when the user asks to synthesize or cull their concepts, build their intellectual map, or trace idea evolution across notes") so the description self-containedly answers both what and when.

Mention the clustering/master-map output (Phase 4) explicitly — e.g., "clusters concepts into auto-named domains and builds a concepts/README.md master map" — to close the one coverage gap.

Fold one or two of the most natural user phrasings ("find patterns across my notes", "which concepts to keep") into the description to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Deduplicate and synthesize raw concept stubs into a tiered intellectual map (T1 Canon to T4 Riff)", "tracing idea evolution across sources over time", and 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" — with only a minor coverage gap (Phase 4 clustering is merely implied via "cluster budgets"). This sits at anchor 4 (several specific actions, minor gaps) rather than 5, since one phase of the pipeline is not explicitly named.

4 / 5

Completeness

The "what" is clearly and concretely answered across three dense sentences, but the description field itself contains no "Use when..." clause or equivalent trigger guidance — the when-guidance lives in separate `triggers` and `when_to_use` frontmatter fields, not in the description. Per the rubric guideline, a missing 'Use when...' clause caps completeness at 3; it is not 2 because the "what" is fully clear, and not 4 because no when-guidance appears in the evaluated field.

3 / 5

Trigger Term Quality

Natural keyword coverage is good: "synthesize... concept stubs", "intellectual map", "tracing idea evolution", and "curation cull" match phrases a user would plausibly say. A few natural terms from the skill's own trigger list ("find patterns across my notes", "canon vs riff", "concept quality rubric", "which concepts to keep") are missing from the description itself, which matches anchor 4 (good coverage, a few natural terms missing) rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — personal concept synthesis with T1–T4 tiering, a curation cull, and merge-with-backlinks — that is unmistakably distinct from sibling ingestion skills (signal-detector, idea-ingest, voice-note-ingest). Trigger terms like "synthesize raw concept stubs" and "curation cull" are unlikely to fire for the wrong skill, matching anchor 5 (clear niche, minimal conflict risk).

5 / 5

Total

16

/

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 (523 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

plugin-variants/gbrain-coding/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.