CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-book-to-skill

Turns authorized books into portable skill references with rights scoping, source mapping, synthesis, fidelity checks, and handoff. Use when asked to book to skill, book-to-skill, or convert a book to a skill.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exceptionally lean, well-sequenced overview with a genuinely progressive bundle structure and explicit validation checkpoints. Its main weakness is actionability: the guidance is directive but abstract, deferring most executable specifics to the reference files without inline anchors for the most common cases.

Suggestions

Add one concrete inline example per step (e.g., a sample rights-disposition table row, or the exact fields of a source-map entry) so the core loop is executable without opening a reference file.

Make the failure path explicit: state what to do when a fidelity sample, hash check, or installation test fails (fix, re-verify, or block the affected disposition) to close the feedback loop.

Expand the reference pointers with per-file scope hints (e.g., which step each reference serves) so the right file is chosen on first read.

DimensionReasoningScore

Conciseness

The 26-line body is lean with no padding and no explanations of concepts Claude already knows; every clause carries instruction (e.g., "A converter's software license grants no source-book rights", "A prompt is not a hard cap"). Nothing could be trimmed without losing guidance, matching anchor 5.

5 / 5

Actionability

The steps name concrete artifacts and checks (edition, identity/hash, page count, tokenizer, batch/usage limits, hash verification) but the how is abstract: "Give every source span a reasoned disposition and precise output anchor/locator" and "normalize shared identity once" lack the specific procedures or examples needed to execute. It exceeds anchor 2's high-level-hints level but is incomplete, matching anchor 3.

3 / 5

Workflow Clarity

A clear 5-step sequence (scope, pilot, map/synthesize, verify/freeze, handoff/test) with explicit validation checkpoints ("Independently sample fidelity and high-risk distinctions", "verify immutable packet/output hashes", "negative boundary cases"). It falls short of anchor 5 because error-recovery feedback loops (what to do when a fidelity or verification check fails) are not explicit.

4 / 5

Progressive Disclosure

The body is a concise overview pointing to four labeled, one-level-deep references ([rights and pilot], [mapping and synthesis], [large-source delegation], [verification and handoff]), all of which exist as real files in references/ with no nested references. Content is appropriately split and navigation is easy, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Description

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

A strong description: third-person, concise, with an explicit what/when structure and concrete trigger phrases. The only gap is that capability verbs are workflow-phase names and trigger coverage misses a few natural phrasings of the request.

Suggestions

Make the capability actions more concrete, e.g. "Turns authorized books into portable skill references: scopes rights per action, maps source spans to output anchors, checks fidelity, and hands off a tested skill".

Add trigger variations users would naturally say, such as "turn a book into a skill" or "make a skill from this book".

DimensionReasoningScore

Specificity

"Turns authorized books into portable skill references with rights scoping, source mapping, synthesis, fidelity checks, and handoff" lists several specific actions in a clearly named domain. It falls short of anchor 5 because the actions are named workflow phases rather than fully concrete operations, but exceeds anchor 3 by covering more than 1-2 actions.

4 / 5

Completeness

The description explicitly answers "what" ("Turns authorized books into portable skill references with rights scoping...") and "when" ("Use when asked to book to skill, book-to-skill, or convert a book to a skill") with concrete trigger phrases. The "when" clause is fully explicit, so anchor 4's "could be more explicit" does not apply.

5 / 5

Trigger Term Quality

"Use when asked to book to skill, book-to-skill, or convert a book to a skill" provides natural phrasings users would actually say. Common variations such as "turn a book into a skill" or "make a skill from this book" are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"authorized books into portable skill references" defines a clear niche with distinctive triggers ("book to skill", "convert a book to a skill") that no generic document- or file-handling skill would match. Conflict risk is minimal, matching anchor 5.

5 / 5

Total

18

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-book-to-skill/SKILL.md

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.