CtrlK
BlogDocsLog inGet started
Tessl Logo

brain-pdf

Generate a publication-quality PDF from any brain page via the gstack make-pdf binary. Strips YAML frontmatter, sanitizes emoji, applies running headers and page numbers. Brain page is always the source of truth; PDF is a rendering.

63

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/brain-pdf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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 with a clear validated workflow and good sectioning, but actionability is held back by speculative/placeholder commands (the --raw flag and unexplained sed) and conciseness by repeated restatements of the source-of-truth rule.

Suggestions

Replace the speculative '# whatever flag exposes raw body' gbrain invocation with the verified, executable flag and a fallback, so the core path is fully copy-paste ready.

Add a one-line comment explaining the sed frontmatter-strip expression so it is unambiguous and reproducible.

Consolidate the source-of-truth rule to a single canonical statement to trim repeated restatements across the callout, 'The rule', 'Delivery', and 'Anti-Patterns' sections.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code and tight rationale, but it repeats the source-of-truth rule across the convention callout, 'The rule', 'Delivery', and 'Anti-Patterns', and includes some redundancy that could be tightened, matching the score-2 anchor.

2 / 3

Actionability

It provides mostly executable bash, but key steps are speculative or incomplete — "gbrain get "$SLUG" --raw > "$RAW" # whatever flag exposes raw body" and the unexplained frontmatter-strip sed — so it is not fully copy-paste ready, matching score-2.

2 / 3

Workflow Clarity

The RESOLVE→STRIP→RENDER→DELIVER workflow is clearly sequenced with an explicit validation checkpoint (confirming the brain page and make-pdf binary exist before proceeding) and an anti-patterns list, matching the score-3 anchor.

3 / 3

Progressive Disclosure

For a single-file skill under ~190 lines with no bundle files, content is well-organized into clearly signaled sections with one-level-deep links to conventions/related skills, satisfying the simple-skill scoring note for a 3.

3 / 3

Total

10

/

12

Passed

Description

82%

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, specific description with good natural-language triggers and a distinct niche. Its main weakness is the missing explicit "Use when..." clause in the description prose itself, which caps completeness at 2.

Suggestions

Add an explicit 'Use when...' sentence to the description (e.g., 'Use when the user asks to make/export a PDF from a brain page') so the when-guidance lives in the prose, not just the triggers list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Generate a publication-quality PDF", "Strips YAML frontmatter, sanitizes emoji, applies running headers and page numbers" — which matches the score-3 anchor of multiple specific concrete actions.

3 / 3

Completeness

It states clearly what the skill does, but there is no explicit "Use when..." trigger guidance in the description itself; the "when" lives only in the separate triggers list, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The triggers ("make pdf from brain", "brain pdf", "convert brain page to pdf", "publish this page as pdf", "export brain page") cover the natural phrasings a user would say, matching the score-3 good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The niche is clearly distinct — "brain page" + "gstack make-pdf" + PDF rendering — and unlikely to trigger for unrelated PDF skills, matching the clear-niche score-3 anchor.

3 / 3

Total

11

/

12

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