CtrlK
BlogDocsLog inGet started
Tessl Logo

publish

Share brain pages as beautiful password-protected HTML with zero LLM calls

56

Quality

64%

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/publish/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and clean sectioning, but the ~160-line length and restated encryption guidance keep conciseness from a 3, and the absence of explicit validation checkpoints before sharing private content caps workflow clarity at 2.

Suggestions

Consolidate the repeated 'always encrypt' guidance into one canonical section (Contract or 'Default: ALWAYS ENCRYPT') and have Anti-Patterns reference it, cutting roughly 30-40 lines.

Add an explicit validation checkpoint before sharing (e.g., confirm the output file is ciphertext-only and contains no frontmatter/source citations) to lift workflow clarity to 3.

Trim the option-by-option hosting workflows (A-D) to the two most common plus a one-line pointer, since the core publish command is already demonstrated in Quick Reference.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is well-organized, but the 'always encrypt / default encrypted' guidance is restated across Contract, 'Default: ALWAYS ENCRYPT', and Anti-Patterns, and at ~160 lines it could be tightened for a single-purpose skill.

2 / 3

Actionability

It provides concrete, copy-paste-ready `gbrain publish` commands with real flags (--password, --out, --title) across multiple worked workflows plus precise crypto parameters (AES-256-GCM, PBKDF2 100K), fully executable.

3 / 3

Workflow Clarity

Workflows A-D are clearly sequenced, but publishing private brain content externally is a risky operation with no explicit validation checkpoint (e.g., verify metadata was stripped / ciphertext-only before sharing), so checkpoints remain implicit.

2 / 3

Progressive Disclosure

No bundle files exist and the document references nothing external, yet it is cleanly sectioned with no deep nesting or broken references; for a self-contained single-file skill this meets the well-organized-sections bar.

3 / 3

Total

10

/

12

Passed

Description

57%

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 distinguishable but incomplete: it explains what the skill does without an explicit 'Use when...' trigger clause and relies on frontmatter triggers rather than natural in-description keywords. Adding a 'Use when the user wants to share or publish a brain page...' clause would lift completeness and trigger quality.

Suggestions

Append an explicit 'Use when...' clause naming user-trigger phrases (e.g., 'share this page', 'publish page', 'create shareable link') directly in the description so completeness and trigger term quality can reach 3.

List more discrete actions (strip private metadata, encrypt with AES-256-GCM, generate self-contained HTML) instead of one composite phrase to strengthen specificity.

Move or mirror the natural trigger terms currently only in frontmatter into the description field itself.

DimensionReasoningScore

Specificity

The description names a concrete domain and action ('Share brain pages as beautiful password-protected HTML') but offers a single composite action rather than a list of multiple specific concrete actions, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

It clearly states what the skill does (share brain pages as password-protected HTML) but has no explicit 'Use when...' clause answering when to invoke it, which the rubric caps at 2.

2 / 3

Trigger Term Quality

'share brain pages' and 'password-protected' are relevant natural terms, but the description omits common user variations like 'publish' or 'create shareable link' that appear only in the separate frontmatter triggers, leaving coverage partial.

2 / 3

Distinctiveness Conflict Risk

'Share brain pages as beautiful password-protected HTML' carves a clear, narrow niche tied to brain content that is unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

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.