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

81%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable read-only skill body with a clear phased workflow and concrete output contract. Its main weaknesses are triply-duplicated tool listings and a monolithic single-file layout that could offload detailed reference material into bundle files.

Suggestions

Remove the redundant "Tools Used" prose section (or the inline tool mentions) since the frontmatter tools field plus contextual mentions already cover it.

Consider moving the Output Format template and Quality Rules into a references/ file linked from the body, reducing the monolithic length while keeping the overview tight.

Dimension	Reasoning	Score
Conciseness	The body is lean and free of concept-explanation padding, but the tool inventory is repeated three times (frontmatter tools, inline mentions in Phases, and the prose "Tools Used" section), so it could be tightened further.	2 / 3
Actionability	Despite being instruction-only, it gives concrete per-situation tool calls, a defined seven-bucket classification scheme, and a copy-ready output-format template — actionable guidance with no code penalty applying.	3 / 3
Workflow Clarity	Five phases are explicitly sequenced with real checkpoints: user disambiguation on shared phrases, entity-shape handoff to find_trajectory, and mandatory gap-labeling; the read-only nature means no destructive-validation cap applies.	3 / 3
Progressive Disclosure	External references (conventions/quality.md, docs/takes-vs-facts.md) are clearly signaled one-level callouts, but no bundle files exist and the ~195-line body keeps output format, quality rules, and anti-patterns inline in a single monolithic file rather than splitting detail into skill-local references.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 precise, well-scoped description that names concrete capabilities and an explicit use boundary, with strong distinctiveness. Its only weakness is that the most natural user trigger phrasings are segregated into the triggers field rather than woven into the description.

Suggestions

Fold one or two of the most natural user phrasings (e.g. "how has my thinking about X changed") directly into the description so trigger-term coverage does not depend on the separate triggers field.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete lineage actions — "first mention, best articulation, related concepts, reversals, contradictions, abandoned branches, and the current live version" — matching the comprehensive multi-action anchor rather than the partial domain-only anchor.	3 / 3
Completeness	It states both what ("Trace one idea's evolution through the brain...") and when ("Use for single-idea conceptual lineage, not broad concept-map synthesis or structured entity metrics"), satisfying the explicit what-and-when anchor.	3 / 3
Trigger Term Quality	Description carries relevant natural terms ("idea", "lineage", "evolution", "current live version") but the most common user phrasings ("how has my thinking about", "where did this idea come from") live in the triggers field rather than the description text, leaving common variations missing.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche by excluding "broad concept-map synthesis" and "structured entity metrics", making overlap with sibling skills unlikely.	3 / 3
	Total	11 / 12 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: 3fafb69

Reviewed: about 21 hours 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.