CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bitcoin-auth-diagnostics

Diagnose and troubleshoot bitcoin-auth token generation and verification issues. This skill should be used when users encounter authentication failures, signature verification errors, or integration problems with the bitcoin-auth library.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills_all/bitcoin-auth-diagnostics/SKILL.md
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.

The body delivers highly actionable, executable diagnostic guidance with a well-gated workflow, but it is undermined by dangling references to files that don't exist in the bundle and by inlined detail that belongs in those files. Redundant sections and verbose logging scaffolding also cost tokens.

Suggestions

Create the actual reference files (references/bitcoin-auth-api.md, references/common-issues.md) or remove the citations — the body currently points to files that are not in the bundle.

Move the "Common Error Patterns" and "Integration with Sigma Auth" detail into the referenced troubleshooting file so SKILL.md stays a lean overview.

Merge the redundant Overview and "When to Use This Skill" sections and trim the console.log scaffolding in Step 2 to the essential checks.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is code-centric, but it needs more than minor trimming: the Overview and "When to Use This Skill" sections duplicate the frontmatter description, and Step 2 is a wall of console.log diagnostic scaffolding that pads the token count. This fits anchor 3 ("mostly efficient but... could be tightened") better than anchor 4's "minor instances".

3 / 5

Actionability

The content is fully executable and copy-paste ready: real imports (parseAuthToken, verifyAuthToken, getAuthToken), concrete parameters (timePad 5, bodyEncoding 'utf8'), a valid example token, ❌/✅ wrong-vs-correct server patterns, and cause→solution mappings for each error message. It matches anchor 5's "specific examples cover the common cases".

5 / 5

Workflow Clarity

The 4-step diagnostic sequence is clearly ordered with conditional gates ("First, validate the token structure before checking cryptographic validity"; "If structure is valid, diagnose verification failures") and branch-by-branch failure diagnosis, matching anchor 4. It is not a 5 because there is no explicit fix→re-verify loop (recovery appears only as hints like "Try different encodings if utf8 fails") and Step 4 sits outside the gated sequence.

4 / 5

Progressive Disclosure

The "Reference Documentation" section clearly signals references/bitcoin-auth-api.md and references/common-issues.md, but neither file exists in the bundle — the navigation promise is broken — while ~200 lines of detailed error patterns and Sigma Auth integration content that belongs in those files is inlined. This lands at anchor 3 (structure present, content that should be separate is inline) rather than 4, because the intended split is not actually realized.

3 / 5

Total

15

/

20

Passed

Description

82%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 strong: it explicitly states both what the skill does and when to use it, with natural trigger phrases tied to a specific library that minimizes conflict risk. The only gaps are mildly generic action verbs and a few missing synonym trigger terms.

DimensionReasoningScore

Specificity

"Diagnose and troubleshoot bitcoin-auth token generation and verification issues" names the domain with two concrete actions, matching anchor 3's "1-2 concrete actions, but not comprehensive". It is not a 4 because "diagnose" and "troubleshoot" are near-synonymous generic verbs rather than several distinct specific actions like "extracts text, fills forms, converts pages".

3 / 5

Completeness

It clearly answers "what" ("Diagnose and troubleshoot bitcoin-auth token generation and verification issues") and explicitly answers "when" with concrete trigger conditions ("This skill should be used when users encounter authentication failures, signature verification errors, or integration problems with the bitcoin-auth library"), mirroring the anchor 5 example's structure.

5 / 5

Trigger Term Quality

"authentication failures", "signature verification errors", and "integration problems" are natural phrases users would say when hitting this issue, giving good keyword coverage. It falls short of anchor 5 because common variations users actually type — e.g. "invalid signature", "token expired", "time skew" — are absent.

4 / 5

Distinctiveness Conflict Risk

Naming the specific "bitcoin-auth library" establishes a clear niche with distinct triggers and minimal conflict risk, matching anchor 5. Although "authentication failures" alone is broad, the library qualifier disambiguates it from generic auth skills.

5 / 5

Total

17

/

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 possibly missing (references/bitcoin-auth-api.md, references/common-issues.md)

Warning

Total

14

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/bitcoin-auth-diagnostics/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.