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/response interceptors for adding authentication headers, logging, error handling, retry logic, and request transformation in API clients like Axios, Fetch, or similar libraries.'
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 varied natural language terms users would actually say, such as 'middleware', 'HTTP interceptor', 'API request handler', 'axios interceptor', 'request pipeline'.
| 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 shell with no substantive content. It consists entirely of generic boilerplate that repeats the skill name without providing any actual guidance on creating request interceptors—no code examples, no patterns (e.g., Axios interceptors, fetch wrappers, middleware patterns), no concrete instructions of any kind. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code examples for creating request interceptors in at least one framework (e.g., Axios interceptors, fetch wrappers, or Express middleware), showing auth token injection, error handling, and retry logic.
Define a clear workflow: 1) Identify the HTTP client in use, 2) Create the interceptor with specific patterns, 3) Register it, 4) Validate by testing a sample request—with explicit validation steps.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that describe the skill meta-information rather than teaching how to actually create request interceptors.
Add references to advanced topics like request/response transformation, logging interceptors, and retry strategies, either inline or via linked files for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'request interceptor creator' excessively, and provides zero actual technical content. Every token is wasted. | 1 / 3 |
Actionability | There is no concrete code, no commands, no executable guidance whatsoever. The skill only describes what it claims to do in abstract terms without providing any actual instructions for creating request interceptors. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill mentions 'step-by-step guidance' as a capability but never provides any steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization beyond empty section headers. | 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
c8a915c
- 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.