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.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/brain-pdf/SKILL.md

Quality

Content

67%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 and highly actionable with a clear workflow and validation, but it suffers from noticeable repetition of two key messages and one uncertain command flag that prevent top scores on conciseness and actionability.

Suggestions

Consolidate the 'brain page is the source of truth' and 'no cover/no TOC by default' messages so each appears once; remove the redundant restatements in The rule, Defaults, and Delivery sections.

Replace the '# whatever flag exposes raw body' placeholder with the verified gbrain raw-body flag, or document the fallback path as the single supported method.

Add a final verification checkpoint (e.g., '[ -s "$OUT" ] || { echo 'render failed' >&2; exit 1; }') to close the workflow with an explicit success check.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no basic-concept padding, but the 'brain page is the source of truth' message and the 'no cover, no TOC' default are each restated ~3 times across the convention blockquote, The rule, Workflow, Common patterns, Defaults, and Delivery sections, so it could be tightened.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready bash, exact binary paths, a working sed frontmatter-strip command, and specific flags; the only gap is the hand-wavy '# whatever flag exposes raw body' comment on the gbrain raw-body call.	4 / 5
Workflow Clarity	A clear RESOLVE → STRIP → RENDER → DELIVER sequence with existence-validation checkpoints for the brain page and the make-pdf binary; no explicit verification that the rendered PDF was produced, though the operation is non-destructive so no cap applies.	4 / 5
Progressive Disclosure	Well-sectioned single file with clearly signaled one-level references (conventions/quality.md and related skills); at ~173 lines it exceeds the simple-skill threshold, and the full invocation script and font requirements could conceptually be referenced material, keeping it at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

63%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 is specific and actionable with a clear niche, but it lacks an explicit 'Use when' trigger clause and relies on niche internal terminology, which limits trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete user intents, e.g. 'Use when the user asks to export, publish, or share a brain page as a PDF.'

Broaden trigger terms with natural synonyms and extensions users might say, such as 'export brain page to PDF', '.pdf', or 'print brain page'.

Keep the strong action list but consider framing the closing sentence as a usage trigger rather than a restatement of the source-of-truth rule.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'Generate a publication-quality PDF', 'Strips YAML frontmatter', 'sanitizes emoji', 'applies running headers and page numbers' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clear and detailed, but there is no explicit 'Use when...' clause or equivalent trigger guidance; the 'when' is only weakly implied, capping completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Contains relevant natural terms ('PDF', 'brain page', 'make-pdf') but lacks synonyms and file extensions, and 'brain page'/'make-pdf' are niche internal terms rather than broadly natural user phrasing.	3 / 5
Distinctiveness Conflict Risk	The 'brain page → PDF' niche with 'gstack make-pdf' is mostly distinct with minimal conflict risk; minor overlap only with the related publish/HTML-rendering skill.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Path: skills/brain-pdf/SKILL.md
Commit: 7b7921d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.