api-expert
Expert API architect specializing in RESTful API design, GraphQL, gRPC, and API security. Deep expertise in OpenAPI 3.1, authentication patterns (OAuth2, JWT), rate limiting, pagination, and OWASP API Security Top 10. Use when designing scalable APIs, implementing API gateways, or securing API endpoints.
80
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 strong skill description that clearly defines its domain (API architecture and security), lists specific technologies and patterns, and includes an explicit 'Use when' clause with actionable triggers. The only minor issue is the use of 'Expert API architect specializing in' which is slightly persona-like rather than pure third-person action verbs, but it doesn't significantly detract from the description's effectiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: RESTful API design, GraphQL, gRPC, API security, OpenAPI 3.1, OAuth2, JWT, rate limiting, pagination, and OWASP API Security Top 10. | 3 / 3 |
Completeness | Clearly answers both what (API design across multiple paradigms, security patterns, specifications) AND when with explicit 'Use when' clause covering designing APIs, implementing gateways, and securing endpoints. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'API', 'REST', 'GraphQL', 'gRPC', 'OAuth', 'JWT', 'rate limiting', 'pagination', 'API security', 'API gateway' - these are all terms developers naturally use when seeking API help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on API architecture and security with distinct triggers like 'API gateway', 'OpenAPI', 'gRPC', 'OWASP API Security' that are unlikely to conflict with general coding or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable guidance with production-ready code examples and clear TDD workflows, but suffers significantly from verbosity. It explains concepts Claude already knows (REST basics, HTTP status codes, what JWT is), repeats information across sections, and includes an unnecessary 50-line anti-hallucination protocol. The content would be more effective at 30-40% of its current length.
Suggestions
Remove the entire 'Anti-Hallucination Protocol' section - Claude doesn't need meta-instructions about verification; focus on the actual API patterns
Eliminate explanatory text about what REST/JWT/OAuth are - keep only the implementation patterns and code examples
Move the OWASP table, performance patterns (sections 5-6), and detailed security examples to the referenced files (references/security-examples.md) rather than duplicating inline
Consolidate the repeated NEVER/ALWAYS lists and checklists into a single concise reference section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines, explaining concepts Claude already knows (what REST is, what HTTP status codes mean, basic JWT concepts). The anti-hallucination protocol section alone is ~50 lines of unnecessary meta-instruction. Multiple sections repeat the same information (e.g., 'NEVER/ALWAYS' lists appear in multiple places). | 1 / 3 |
Actionability | The skill provides fully executable code examples in Python/JavaScript with proper imports, complete function signatures, and copy-paste ready implementations. Test examples use real pytest/httpx patterns, and the FastAPI router examples are production-ready. | 3 / 3 |
Workflow Clarity | The TDD workflow is clearly sequenced with explicit steps (write failing test → implement minimum → refactor → verify). The pre-implementation checklist provides explicit validation checkpoints across three phases, and the verification commands are concrete (pytest, openapi-spec-validator, bandit). | 3 / 3 |
Progressive Disclosure | The skill references external files (references/advanced-patterns.md, references/security-examples.md, references/anti-patterns.md) appropriately, but the main file contains too much inline content that should be in those reference files. The OWASP table, performance patterns, and security standards could be split out to reduce the monolithic nature. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (600 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Repository
- martinholovsky/claude-skills-generator
- Commit
1086ef2
- 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.