idea-lineage

Trace one idea's evolution through the brain: first mention, best articulation, related concepts, reversals, contradictions, abandoned branches, and the current live version. Use for single-idea conceptual lineage, not broad concept-map synthesis or structured entity metrics.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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-organized, mostly lean instruction-only skill body with concrete tool guidance, a clear five-phase workflow, and an explicit output template. Tightening the narrative intro and providing a worked example would lift the borderline-4 dimensions toward 5.

Suggestions

Trim the 'What this solves' narrative paragraph and de-duplicate boundary statements that recur across 'What this is not', 'Contract', and 'Related Skills and Operations'.

Add one short worked example (e.g. a filled 'Lineage' section for a sample idea) so the output template is copy-paste-ready rather than placeholder-only.

Make the read-only validation checkpoint in Phase 3/4 explicit as a 'verify each claim cites evidence before writing' step to strengthen the feedback-loop framing.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-structured assuming Claude's competence, but the 'What this solves' narrative and some repeated boundary statements across 'What this is not', 'Contract', and 'Related Skills' could be trimmed.	4 / 5
Actionability	Concrete, tool-specific guidance ('Search for exact phrase variants with `search`', 'Run one semantic `query`') plus a templated output format give mostly executable direction; the placeholder template stops just short of copy-paste-ready examples.	4 / 5
Workflow Clarity	Phases 1-5 are clearly sequenced with decision-point checkpoints (entity/metric handoff, ambiguous-idea disambiguation, missing-evidence labeling); being read-only, the destructive/batch cap does not apply, though explicit validate-retry feedback loops are not needed here.	4 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and one-level signaled references (blockquotes to conventions/docs); no bundle files exist to split, and structure is good with only minor inline-vs-separable content questions.	4 / 5
	Total	16 / 20 Passed

Description

92%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 tight, third-person description that states a concrete action, enumerates comprehensive output buckets, and explicitly scopes when to use it versus adjacent skills. Minor trigger-term naturalness could be improved by surfacing user-style phrases directly in the description.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('Trace one idea's evolution through the brain') and enumerates comprehensive output buckets — 'first mention, best articulation, related concepts, reversals, contradictions, abandoned branches, and the current live version' — leaving no major coverage gap.	5 / 5
Completeness	Explicitly answers both what ('Trace one idea's evolution ...') and when ('Use for single-idea conceptual lineage, not broad concept-map synthesis or structured entity metrics'), with a concrete 'Use for' trigger clause.	5 / 5
Trigger Term Quality	Natural terms like 'idea', 'lineage', 'evolution', 'current live version', 'reversals', and 'contradictions' appear, but a few common phrasings users actually say (e.g. 'how has my thinking changed') are present only in frontmatter triggers, not the description itself.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche by negation — 'not broad concept-map synthesis or structured entity metrics' — minimizing overlap with sibling skills and giving distinct triggers.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: garrytan/gbrain
Path: skills/idea-lineage/SKILL.md
Commit: 43597b1

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