request-interceptor-creator
Request Interceptor Creator - Auto-activating skill for API Integration. Triggers on: request interceptor creator, request interceptor creator Part of the API Integration skill category.
33
0%
Does it follow best practices?
Impact
95%
0.96xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/request-interceptor-creator/SKILL.mdQuality
Discovery
0%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 description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as its only trigger term, lacks any concrete capability descriptions, and has no 'Use when...' guidance. It would be nearly impossible for Claude to reliably select this skill from a pool of similar API-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates HTTP request interceptors for adding authentication headers, logging requests, handling retries, and transforming request/response payloads in frameworks like Axios, Fetch, or Express.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about middleware, HTTP interceptors, request hooks, axios interceptors, fetch wrappers, API request preprocessing, or response handling.'
Remove the duplicate trigger term and replace with diverse natural language variations users might actually use, such as 'middleware', 'request pipeline', 'API hooks', 'request preprocessing', 'response handler'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Request Interceptor Creator') and its category ('API Integration') but does not describe any concrete actions. There are no specific capabilities listed such as 'creates middleware functions', 'adds authentication headers', or 'handles request/response transformation'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' (no concrete actions described) and 'when should Claude use it' (no 'Use when...' clause or equivalent explicit trigger guidance). It only states the skill name and category. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('request interceptor creator, request interceptor creator'). There are no natural user keywords like 'middleware', 'HTTP interceptor', 'axios interceptor', 'fetch wrapper', 'API middleware', or 'request hooks' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'API Integration' is a broad category, and without specific actions or triggers, this could easily conflict with other API-related skills. The term 'request interceptor creator' is somewhat niche but the description provides no context to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It contains only generic boilerplate descriptions that repeat the skill name without providing any actual guidance, code examples, or actionable instructions for creating request interceptors. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples showing how to create request interceptors (e.g., Axios interceptors, Express middleware, or fetch wrappers) with copy-paste ready snippets.
Define a clear workflow: identify the HTTP client/framework, create the interceptor function, attach it, and validate it works with a test request.
Remove all generic filler text ('This skill provides automated assistance...') and replace with specific patterns like auth token injection, request logging, retry logic, and error handling interceptors.
Add references to supporting files for advanced patterns (e.g., PATTERNS.md for common interceptor patterns, EXAMPLES.md for framework-specific implementations).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'request interceptor creator' excessively, and provides zero domain-specific information or code. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no actual guidance on how to create a request interceptor. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is described. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.