CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/article-enrichment/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is well-structured, mostly concise, and actionable with concrete commands, a clear pipeline, and validation/idempotency checkpoints for a batch mutation operation. Minor gaps in executable detail for the enrichment step and a couple of redundant sections keep it just below top marks.

DimensionReasoningScore

Conciseness

Content is mostly efficient and assumes Claude's competence; minor redundancy between the "pipeline" and "invocation" sections and a few explanatory sentences could be trimmed, but it is not padded with concepts Claude already knows.

4 / 5

Actionability

Provides concrete gbrain commands and a numbered pipeline, but the core enrichment step is described as the agent reading and writing rather than given as fully executable code, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 6-step sequence with an idempotency checkpoint (skip if needs_enrichment already false) and an LLM-judge spot-check feedback loop; one validation checkpoint is implicit rather than an explicit validate->fix->retry loop, so it stops short of 5.

4 / 5

Progressive Disclosure

Sections are well organized and external conventions (quality.md, _brain-filing-rules.md) are referenced one level deep and clearly signaled; no bundle files exist, and a small amount of guidance that could live elsewhere is inlined.

4 / 5

Total

16

/

20

Passed

Description

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

The description concretely describes the skill's outputs and occupies a clear niche, but it omits an explicit "Use when..." trigger clause, which caps completeness and limits trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming natural trigger phrases (e.g., "Use when an article brain page is a wall of text or marked needs_enrichment: true").

Include a couple of natural user-facing synonyms in the description ("article", "longread", "brain page", "wall of text") to improve trigger-term coverage.

Tighten distinctiveness by contrasting briefly with media-ingest so it cannot fire on raw ingest.

DimensionReasoningScore

Specificity

Lists several concrete outputs — "executive summary, verbatim quotes, key insights, why-it-matters, and cross-references" — giving clear, specific actions rather than vague language, but coverage is not exhaustive enough for a 5.

4 / 5

Completeness

It clearly answers "what" (transform raw dumps into structured pages) but provides no explicit "when" / "Use when..." trigger clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Relevant domain keywords ("article", "enrich", "brain pages") appear, but natural user-facing variations and synonyms are thin and there is no explicit trigger phrase list in the description.

3 / 5

Distinctiveness Conflict Risk

The niche is clear (article-enrichment in the brain) and triggers are fairly distinct with minor overlap risk against related ingest skills.

4 / 5

Total

14

/

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.

Validation14 / 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, 2 suspicious

Warning

Total

14

/

16

Passed

Repository
garrytan/gbrain
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.