CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-research

Structured data research: search sources, extract structured data, archive raw sources, maintain canonical tracker pages, deduplicate. Parameterized via YAML recipes for investor updates, donations, company updates, or any email-to-structured-data pipeline.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is data-research in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured operational skill: the 7-phase pipeline is clearly sequenced with genuine validation checkpoints and feedback loops, tool usage and error recovery are concrete, and detail is appropriately deferred to external files. The remaining gaps are modest — mild duplication of trigger/capability statements across intro and When-to-Use sections, a missing worked recipe example, and inconsistent external reference paths.

Suggestions

Trim the duplication between the intro paragraph, the 'Contract' section, and 'When to Use' — trigger phrases appear in the frontmatter, the intro, and When to Use, so one restatement suffices.

Include a short example recipe YAML (5–10 lines with source queries, classification rules, and extraction schema fields) so Phase 1's 'copy a built-in recipe and edit' has a concrete anchor without leaving the skill.

Unify the external reference paths to a single consistent form ('../conventions/agent-operator-protocol.md' vs 'skills/conventions/quality.md' currently mix relative and pseudo-absolute styles).

DimensionReasoningScore

Conciseness

The body is dense and operational with zero filler and no explanations of concepts Claude already knows, but the intro paragraph, 'Contract', and 'When to Use' sections each restate capabilities/trigger phrases already present in the frontmatter — minor duplication that could be trimmed, placing it at the 4 anchor rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is mostly executable within its tool environment: concrete tool names (put_raw_data, put_page, file_upload), paths (~/.gbrain/recipes/{name}.yaml), a specific recovery command (gbrain write-request <request_id>), and a worked output-table example; minor gaps remain — no example recipe YAML and no concrete search-query samples — so it falls short of fully copy-paste-ready.

4 / 5

Workflow Clarity

Seven clearly sequenced phases with explicit validation for batch/destructive operations (the extraction integrity rule mandates re-reading from saved files and never trusting LLM working memory; dedup runs before any tracker write), feedback loops for error recovery (revision_conflict → re-read and merge; rate_limited → back off and log the gap; LLM-fallback logging to improve regexes), and a numbered checklist — matching the top anchor.

5 / 5

Progressive Disclosure

A well-organized overview with details appropriately split out — recipes live as separate YAML files, error-protocol and citation rules are deferred to clearly signaled, one-level-deep docs — but the two conventions references use inconsistent path forms ('../conventions/agent-operator-protocol.md' vs 'skills/conventions/quality.md') and cannot be verified against the bundle (no references/ directory ships with it), a minor organization gap versus the 5 anchor.

4 / 5

Total

17

/

20

Passed

Description

80%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 strong description: five specific concrete actions, a named parameterization mechanism, and concrete use cases, with explicit when-to-use guidance present in the frontmatter. The main gaps are that natural trigger phrases and the 'Use when' clause live in separate frontmatter fields rather than in the description string itself, so systems surfacing only the description lose some of that signal.

Suggestions

Fold a brief 'Use when...' clause directly into the description string (e.g., 'Use when the user says "research", "track", or asks to extract structured data from email') so the trigger guidance travels with the description wherever it is surfaced.

Work natural trigger synonyms like "build a tracker", "extract from email", and "log expenses" into the description text itself, rather than relying solely on the separate triggers list.

Sharpen distinctiveness by leading with the niche phrase (email-to-structured-data tracking) before the generic word 'research', which risks overlap with general research skills.

DimensionReasoningScore

Specificity

The description lists five concrete, ordered pipeline actions — "search sources, extract structured data, archive raw sources, maintain canonical tracker pages, deduplicate" — covering the full workflow comprehensively, matching the top anchor rather than the 4 anchor with 'minor gaps in coverage'.

5 / 5

Completeness

The 'what' is explicit and concrete, and a 'when' exists as explicit frontmatter trigger guidance (when_to_use: "Use when the user asks: 'research', 'track'...") so the missing-'Use when' cap does not apply; however, the description string itself only weakly implies the when ("for investor updates, donations..."), fitting the anchor where the when could be more explicit.

4 / 5

Trigger Term Quality

"investor updates", "donations", "company updates", and "research" are natural user phrases, but the description string itself omits common variations like "track", "build a tracker", or "extract from email", which appear only in the separate triggers/when_to_use fields — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

"email-to-structured-data pipeline", "canonical tracker pages", and "YAML recipes" carve a distinct niche, but broad terms like "research" and "search sources" leave minor overlap risk with general research skills, fitting 'mostly distinct; minor overlap risk' rather than the minimal-risk 5 anchor.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-daily/skills/data-research/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.