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.
35
Quality
3%
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
7%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 trigger terms, lacks any concrete capability descriptions, and provides no guidance on when Claude should select this skill. The description would be indistinguishable from any generic API skill.
Suggestions
Add specific capabilities like 'Creates request/response interceptors for HTTP clients, adds authentication headers, implements retry logic, logs API traffic'
Replace duplicate trigger terms with natural user phrases like 'axios interceptor', 'fetch middleware', 'API request hooks', 'HTTP interceptor', 'request middleware'
Add explicit 'Use when...' clause such as 'Use when the user needs to intercept, modify, or log HTTP requests/responses in JavaScript/TypeScript applications'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Request Interceptor Creator') without describing any concrete actions. There are no specific capabilities listed like 'intercepts HTTP requests', 'modifies headers', or 'logs API calls'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('request interceptor creator, request interceptor creator'). Missing natural user terms like 'middleware', 'HTTP interceptor', 'API hooks', 'request middleware', or 'axios interceptor'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'request interceptor' is somewhat specific to a particular programming pattern, the lack of detail about what kind of interceptors (HTTP, GraphQL, etc.) or which frameworks/languages could cause overlap with other API-related skills. | 2 / 3 |
Total | 5 / 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 describes what a request interceptor creator skill should do but provides absolutely no actual guidance, code, examples, or workflows. The entire content is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable code examples showing how to create request interceptors (e.g., Axios interceptors, fetch wrappers, or framework-specific implementations)
Define a clear workflow with steps: 1) Identify interception points, 2) Implement interceptor logic, 3) Register interceptors, 4) Test/validate behavior
Include specific patterns for common use cases: authentication headers, request logging, error handling, retry logic
Remove all generic boilerplate text and replace with actionable, copy-paste ready code snippets
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no specific commands, and no actual instructions on how to create request interceptors. The content only describes what the skill supposedly does without showing how. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a shallow placeholder with no meaningful structure. There are no references to detailed materials, no examples to follow, and no organized content to navigate. | 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
0c08951
- 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.