authentication-setup
Design and implement authentication and authorization systems. Use when setting up user login, JWT tokens, OAuth, session management, or role-based access control. Handles password security, token management, SSO integration.
90
88%
Does it follow best practices?
Impact
97%
1.19xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes a comprehensive set of natural trigger terms that developers would use, explicitly states both what the skill does and when to use it, and carves out a distinct niche in the authentication/authorization domain.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design and implement authentication and authorization systems', 'password security', 'token management', 'SSO integration'. Covers both design and implementation aspects with concrete technical capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Design and implement authentication and authorization systems', 'Handles password security, token management, SSO integration') AND when ('Use when setting up user login, JWT tokens, OAuth, session management, or role-based access control') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'user login', 'JWT tokens', 'OAuth', 'session management', 'role-based access control', 'password security', 'SSO'. These are all terms developers naturally use when discussing auth systems. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on authentication/authorization with distinct triggers like 'JWT', 'OAuth', 'SSO', 'role-based access control'. Unlikely to conflict with general coding skills due to the specific security/auth domain focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable authentication skill with excellent executable code examples and clear workflow structure. The main weaknesses are verbosity (meta-descriptions, explanations of obvious concepts) and the monolithic structure that could benefit from progressive disclosure to separate reference files. The security guidance and troubleshooting sections add practical value.
Suggestions
Remove meta-commentary like 'Specifies the step-by-step task sequence to follow precisely' and 'Lists specific situations where this skill should be triggered' - these waste tokens
Move detailed code examples (full API routes, complete middleware) to separate reference files and keep SKILL.md as a concise overview with links
Trim the 'When to use this skill' section - Claude can infer when authentication is needed from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose in places. Sections like 'When to use this skill' and 'Input Format' explain things Claude would infer. The code examples are valuable but some explanatory text (e.g., 'Specifies the step-by-step task sequence to follow precisely') is unnecessary padding. | 2 / 3 |
Actionability | Excellent actionability with fully executable TypeScript/SQL code examples throughout. Every step includes copy-paste ready code for password hashing, JWT generation, middleware, and complete API endpoints. The examples are complete and production-ready. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow with explicit tasks and checklists. Each step builds on the previous one logically. The middleware section includes a checklist format, and the examples section shows the complete integration process. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's a monolithic document (~400 lines) that could benefit from splitting detailed code examples into separate reference files. References to external docs are present but the main content is dense and inline. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (667 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.