Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows; the only trimming opportunities are the "Contract" section and opening paragraph, which partially restate the frontmatter description.

Actionability

Guidance is concrete throughout — recipe file path ("~/.gbrain/recipes/{name}.yaml"), specific tool names (put_raw_data, file_upload), explicit dedup match rules, and a worked output-format example — but an example recipe YAML block would make the recipe scaffolding fully copy-paste ready.

Workflow Clarity

The 7-phase sequence is explicit with validation checkpoints where they matter for batch operations: the numbered EXTRACTION INTEGRITY RULE (save raw first, re-read from saved files, never trust LLM working memory), the dedup gate before tracker updates, and a fail-improve loop that logs LLM fallbacks for regex improvement.

Progressive Disclosure

Sections are well organized at overview altitude with a one-level reference to skills/conventions/quality.md, and no bundle files exist to misplace; the minor gap is that recipe schemas and the three built-in recipes are described inline and could be split into a reference file for a cleaner overview.

Specificity

The description lists five concrete, distinct actions ("search sources, extract structured data, archive raw sources, maintain canonical tracker pages, deduplicate") plus parameterization via YAML recipes, which matches the comprehensive multi-action anchor rather than the minor-gaps anchor below it.

Completeness

The "what" is clear and concrete, but the description itself contains no "Use when..." clause or equivalent; trigger guidance is delegated to a separate frontmatter triggers list, so per the rubric cap the "when" is only weakly implied and completeness is capped at 3.

Trigger Term Quality

Natural phrases like "investor updates", "donations", "company updates", and "email-to-structured-data" are terms users would actually say, but coverage stops short of the comprehensive anchor, which also includes synonyms and common variations (e.g., "log", "catalog", "spreadsheet", "keep a list of").

Distinctiveness Conflict Risk

The "email-to-structured-data pipeline" niche with YAML recipes and canonical tracker pages is mostly distinct, but generic triggers like "research" and "track" create minor overlap risk with general research or note-taking skills, fitting the mostly-distinct anchor rather than the minimal-conflict anchor.