bearer-token-validator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill bearer-token-validatorBearer Token Validator - Auto-activating skill for API Development. Triggers on: bearer token validator, bearer token validator Part of the API Development skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or meaningful trigger terms. The redundant trigger term and boilerplate category mention add no value for Claude's skill selection process.
Suggestions
Add specific actions the skill performs, e.g., 'Validates bearer token format, checks expiration, verifies JWT signatures, extracts claims from authorization headers'
Include a 'Use when...' clause with natural trigger scenarios like 'Use when validating API authentication, checking JWT tokens, parsing Authorization headers, or debugging token-related 401 errors'
Expand trigger terms to include variations users would naturally say: 'JWT', 'auth token', 'access token', 'Authorization header', 'token expired', 'validate credentials'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Bearer Token Validator') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of validating, parsing, checking expiration, verifying signatures, or any other specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('bearer token validator' listed twice) and overly specific. Missing natural variations users would say like 'JWT', 'auth token', 'validate token', 'token verification', 'authorization header', or 'access token'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Bearer Token Validator' is somewhat specific to a niche (token validation), the lack of detail about what distinguishes it from general API authentication skills or JWT handling skills creates potential overlap. The 'API Development' category is broad. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template that provides no actual guidance on bearer token validation. It contains only generic boilerplate text that could apply to any skill, with no executable code, specific implementation details, or actionable instructions. The content fails to teach Claude anything about validating bearer tokens.
Suggestions
Add executable code examples showing how to validate bearer tokens (e.g., JWT verification, token format checking, expiration validation)
Include specific validation steps: extract token from Authorization header, decode/verify signature, check claims, handle errors
Provide concrete error handling patterns and HTTP response codes for invalid/expired/missing tokens
Remove generic boilerplate sections ('When to Use', 'Example Triggers') and replace with actual implementation guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about bearer token validation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually validate a bearer token or implement any authentication logic. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only lists vague capabilities without any sequence of actions or validation checkpoints for implementing bearer token validation. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no meaningful structure. There are no references to detailed documentation, examples, or related files that would help with actual implementation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.