CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bap-identity

Manage BAP (Bitcoin Attestation Protocol) identity files using bap-cli. This skill should be used when users need to create, decrypt, list, or extract BAP identity backups, work with .bep encrypted files, or generate test fixtures for Playwright tests involving BAP identities.

Quality

82%

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

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

A highly actionable, well-structured reference whose commands are copy-paste ready and whose workflows mostly include verification steps. Its two real weaknesses are verbosity — duplicated workflow sections and redundant bullet lists — and progressive disclosure that promises two reference files that are missing from the bundle.

Suggestions

Create the referenced files `references/bap-cli-reference.md` and `references/bbackup-reference.md` (or remove the Reference Documentation section) — currently the pointers are dangling and the detailed command/API/error material they should hold remains inlined in SKILL.md.

Merge or cut the "Common Use Case Patterns" section: Patterns 1 and 2 restate the "Inspect BAP Identity Using bbackup" / "Upgrade Security of BAP Backup" Combined Workflows almost command-for-command.

Trim the "Use cases:" and "This is useful for:" bullet lists that restate what the preceding command examples already demonstrate, and add a verify step to the create/change-password workflows.

DimensionReasoningScore

Conciseness

Command examples dominate and there is no filler explaining concepts Claude already knows, but padding is present: redundant "Use cases:" / "This is useful for:" bullet lists that restate section headers, and a ~60-line "Common Use Case Patterns" section that repeats the Combined Workflows nearly verbatim (e.g. Pattern 1 vs. the Inspect/Extract workflows). Not 2 because the majority of the ~455 lines are executable commands rather than explanation; not 4 because the duplication is substantial enough to noticeably tighten.

3 / 5

Actionability

Every operation ships a copy-paste-ready command with full flags — `bap new --type type42 --password <password> --name "<name>" --output <file.bep>`, `bbackup dec <input.bep> -p <password> [-o <output.json>]`, `bbackup upg ...` — plus a complete TypeScript programmatic example (createType42Backup → saveTo → getIdentityKeys → cleanup) and a worked encrypt/decrypt/diff verification cycle. Concrete error messages are paired with specific fixes.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced ("1. First run `bap list`... 2. Note the index... 3. Extract using that index") with validation checkpoints in several places — "Verify it works with bap-cli", `diff test.json out.json # Should match`, and a fallback escalation in the debug workflow ("If that fails, try bbackup"). Not 5: a few workflows (new identity creation, change-password, extract-and-transform) end without any verification step, and no destructive/batch operations trigger the cap.

4 / 5

Progressive Disclosure

Section structure is good (clear headers, logical ordering), and the Reference Documentation section signals references well with content summaries. However, the referenced files `references/bap-cli-reference.md` and `references/bbackup-reference.md` do not exist in the bundle — there is no references/ directory — so the promised offloading of detailed command/API material is broken and ~455 lines of it remain inlined in SKILL.md. Not 4 because the reference pointers are dangling, which defeats the split the structure advertises; not 2 because internal organization itself is far from minimal.

3 / 5

Total

15

/

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 voice, explicit 'use when' triggers with concrete phrases, and a clearly bounded niche. The only weakness is minor coverage gaps — encryption-side operations and the bbackup tool from the body are not mentioned.

DimensionReasoningScore

Specificity

Concrete verbs are enumerated — "create, decrypt, list, or extract BAP identity backups", "work with .bep encrypted files", "generate test fixtures for Playwright tests" — matching the 'several specific actions; minor gaps' anchor. Gaps (not 5): encryption/re-encryption operations and the bbackup tool covered in the body are absent, so coverage isn't comprehensive.

4 / 5

Completeness

It explicitly answers both questions: 'what' ("Manage BAP (Bitcoin Attestation Protocol) identity files using bap-cli") and 'when' ("This skill should be used when users need to create, decrypt, list, or extract BAP identity backups, work with .bep encrypted files, or generate test fixtures...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user phrasings are present — "BAP identity backups", ".bep encrypted files", "Playwright tests", "test fixtures" — plus the spelled-out "Bitcoin Attestation Protocol" and a file extension, giving good coverage. A few natural terms are missing ('encrypt', 'bbackup', 'change/rotate password', 'upgrade encryption'), so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — BAP identities, .bep encrypted backups, Playwright BAP fixtures — with virtually no overlap risk against generic crypto or file-management skills. Anti-drift check: neighbors 4 ('minor overlap risk') undersells how distinct BAP/.bep triggers are.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/bap-identity/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.