api-key-auth-setup

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill api-key-auth-setup

What are skills?

Api Key Auth Setup - Auto-activating skill for API Development. Triggers on: api key auth setup, api key auth setup Part of the API Development skill category.

Overall
score

19%

Review — 4%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The duplicate trigger term suggests auto-generated content without human refinement.

Suggestions

Add specific actions the skill performs, e.g., 'Generates API key authentication middleware, configures key validation, sets up rate limiting and key rotation policies.'

Include a 'Use when...' clause with natural trigger terms like 'Use when setting up API authentication, securing endpoints with API keys, implementing key-based access control, or when user mentions API credentials or token authentication.'

Expand trigger terms to include variations users would naturally say: 'API keys', 'API authentication', 'secure API endpoints', 'API credentials', 'key-based auth'.

Dimension	Reasoning	Score
Specificity	The description only states 'Api Key Auth Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'generates', 'configures', 'validates', etc.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the title, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	The trigger terms are just the skill name repeated twice ('api key auth setup, api key auth setup'). Missing natural variations users would say like 'authentication', 'API credentials', 'secure API', 'add API key', etc.	1 / 3
Distinctiveness Conflict Risk	While 'API key auth' is somewhat specific to authentication setup, the lack of detail means it could overlap with general API development skills or security-related skills. The category mention helps slightly.	2 / 3
	Total	5 / 12 Passed

Implementation

This skill content is essentially a template placeholder with no actual instructional value. It contains only meta-descriptions about what the skill should do without any concrete implementation details, code examples, or actionable guidance for API key authentication setup. The content fails on all dimensions as it provides nothing Claude couldn't generate from the title alone.

Suggestions

Add concrete, executable code examples showing API key authentication implementation (e.g., middleware for validating API keys, secure storage patterns, header extraction)

Include a clear workflow with steps: generate key, store securely, validate on requests, handle invalid/expired keys

Provide specific patterns for different frameworks (Express.js, FastAPI, etc.) with copy-paste ready code

Remove all meta-descriptions about the skill and replace with actual technical content about API key auth best practices (key rotation, rate limiting, secure transmission)

Dimension	Reasoning	Score
Conciseness	The content is entirely filler text that explains nothing Claude doesn't already know. It describes what a skill does in abstract terms without any actual implementation details, wasting tokens on meta-descriptions like 'Provides step-by-step guidance' without providing any guidance.	1 / 3
Actionability	There is zero concrete guidance - no code, no commands, no specific steps for implementing API key authentication. The content only describes what the skill theoretically does rather than instructing how to do anything.	1 / 3
Workflow Clarity	No workflow is present. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for implementing API key authentication.	1 / 3
Progressive Disclosure	The content is a monolithic block of placeholder text with no meaningful structure. There are no references to detailed materials, no examples, and no organized sections containing actual content.	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

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

20 days ago

Table of Contents

Activation Implementation Validation

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.