CtrlK
BlogDocsLog inGet started
Tessl Logo

harness-book-best-practice

Best practices for working on the Harness books repo. Use this skill when editing, restructuring, building, or exporting the books under `book1-claude-code/` and `book2-comparing/`, especially for Honkit, print HTML, Pandoc/XeLaTeX PDF export, build cleanup, TOC issues, naming conventions, and keeping source assets separate from generated outputs.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A dense, highly actionable skill body rich in repo-specific commands, validation protocols, and feedback loops. Its main weaknesses are conciseness (repeated TOC caveats) and progressive disclosure (large inline sections that could be externalized).

Suggestions

Consolidate the overlapping TOC sections (TOC And PDF Pitfalls, TOC Failure Modes, TOC Validation Protocol, Preferred Fix Order) into one sequenced block to remove repeated 'do not reintroduce' caveats and tighten the prose.

Move the detailed skinparam/palette tables and LaTeX TOC-macro internals into a reference file (e.g. references/diagram-and-toc-reference.md), keeping SKILL.md as an overview that links to it.

Move the long PDF Link Colors and Build Policy detail behind a short summary plus a pointer if the per-variable list is rarely needed at decision time.

DimensionReasoningScore

Conciseness

It mostly assumes Claude's competence (no generic explanations of PDF/Honkit/Pandoc) and captures hard-won repo-specific pitfalls, but the sprawling TOC/pitfall prose repeats caveats across multiple sections and could be tightened.

2 / 3

Actionability

Provides copy-paste-ready commands (`python3 tools/book-kit/export_pdf.py book1-claude-code --clean-generated`), exact file paths, concrete skinparam blocks, and specific Pandoc `-V` variables — fully executable guidance.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with validation checkpoints: 'Validation After Diagram Changes', 'TOC Validation Protocol' with explicit breakpoints, a 'Validation Checklist', and a 'Preferred Fix Order' with feedback loops.

3 / 3

Progressive Disclosure

Editorial references are correctly one-level-deep and the cited files exist, but the ~270-line body keeps large operational blocks (TOC pitfalls, diagram skinparams) inline that could be split into reference files.

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities and an explicit trigger covering a broad set of repo-specific tasks. It is specific, complete, and clearly distinguished from generic book/document skills.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'editing, restructuring, building, or exporting', 'Honkit, print HTML, Pandoc/XeLaTeX PDF export, build cleanup, TOC issues, naming conventions' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Best practices for working on the Harness books repo') and when ('Use this skill when editing, restructuring, building, or exporting...'), with an explicit 'Use when' trigger.

3 / 3

Trigger Term Quality

Covers natural terms a user of this repo would actually say (Honkit, print HTML, Pandoc/XeLaTeX PDF export, TOC issues, build cleanup, naming conventions), matching the 'good coverage' anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to the Harness books repo with a specific toolchain (Honkit, Pandoc/XeLaTeX, ctexbook, named book directories), giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wquguru/harness-books
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.