CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

article-enrichment

Transform raw article text dumps in the brain into structured pages with executive summary, verbatim quotes, key insights, why-it-matters, and cross-references. Replaces walls-of-text with quotable, actionable brain pages.

Quality

76%

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 ./skills/article-enrichment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

The body is a strong execution document: concrete commands, a validated six-step pipeline with feedback loops and error recovery, and a crisp quality bar. Its weaknesses are redundancy — the same six sections are stated three times across "What this does", the pipeline, and "Quality bar" — and two conformance-test-only tail sections that waste context.

Suggestions

Delete or relocate the "Contract" and "Output Format" sections; their own text admits they exist only for the conformance test and they add no execution value.

Consolidate "What this does" and "Quality bar" into one section — both enumerate the same six output requirements (executive summary, quotes, insights, why-it-matters, see-also, details block).

Give the two non-executable steps concrete form: the put_page call signature and an example back-link edit, so every pipeline step has a copy-paste-ready artifact.

DimensionReasoningScore

Conciseness

The core sections (pipeline, invocation, model selection, failure modes, anti-patterns) are lean, but "What this does" and "Quality bar" restate the same six sections, the pipeline appears in two parallel forms, and the "Contract"/"Output Format" tail sections (~14 lines) explicitly exist only "for the conformance test". Not 4 because this duplication and test-only meta content is more than minor trimming.

3 / 5

Actionability

Concrete commands are given ("gbrain query \"needs_enrichment: true type:article\" --limit 50", "gbrain get media/articles/<slug>", "gbrain write-request <request_id>") plus a precise quality bar with counts and a model-selection table. Not 5 because the put_page write and the cross-link steps name operations ("add a timeline back-link") without any syntax or example.

4 / 5

Workflow Clarity

A clearly sequenced six-step pipeline with an explicit quality-bar checklist, a spot-check feedback loop ("If quotes are paraphrased, switch to Opus for that batch"), and error-recovery protocols for revision_conflict and write_pending. Validation is present for the batch/mutating operation, so the cap does not apply, and all anchor-5 elements (checklist, feedback loop, error recovery) are present.

5 / 5

Progressive Disclosure

A single-file skill with well-organized sections and clearly signaled, one-level-deep references to conventions files at the top (quality.md, _brain-filing-rules.md, agent-operator-protocol.md). Not 5 because the Contract/Output Format meta sections add navigation noise and the body runs long for an overview, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

71%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 specific, third-person description that comprehensively lists the transformation outputs, but it answers only "what" — no "when to use" clause, and it omits the natural "enrich" keyword that the skill's own triggers rely on. Adding a Use-when clause with the enrich phrasing would lift the two weakest dimensions.

Suggestions

Append a "Use when..." clause, e.g. "Use when the user says 'enrich this article' or when an article page lands with needs_enrichment: true or is a wall of raw text."

Work the natural keyword "enrich" (and variants like "enrich pass", "batch enrich") into the description body so routing matches what users actually say.

Name the trigger conditions that distinguish this from media-ingest/idea-ingest (enriching existing pages vs. creating them) to reduce overlap risk.

DimensionReasoningScore

Specificity

The description enumerates the full set of concrete outputs — "executive summary, verbatim quotes, key insights, why-it-matters, and cross-references" — covering the skill's behavior comprehensively in third person. Not 4 because coverage of the skill's actions is complete rather than having minor gaps.

5 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or equivalent explicit trigger guidance in the description; per the judging guidelines this caps completeness at 3. Not 4 because the when is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms like "article", "text dumps", "walls-of-text", and "brain pages" are present, but "enrich" — the verb users would most naturally say and the one anchoring every frontmatter trigger — never appears in the description itself. Not 5 because that primary synonym is missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (brain article-page enrichment, "Replaces walls-of-text with quotable, actionable brain pages") and largely distinct from adjacent ingest skills. Not 5 because it sits next to media-ingest/idea-ingest in the same domain and the description carries no trigger phrases to disambiguate routing.

4 / 5

Total

16

/

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, 3 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

skills/article-enrichment/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.