request-interceptor-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill request-interceptor-creatorRequest Interceptor Creator - Auto-activating skill for API Integration. Triggers on: request interceptor creator, request interceptor creator Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and missing 'Use when...' clause make this description ineffective for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates request/response interceptors for HTTP clients, adds authentication headers, logs API calls, handles retry logic'
Include a 'Use when...' clause with natural trigger terms like 'intercept requests', 'add headers to API calls', 'middleware', 'axios interceptor', 'fetch wrapper'
Specify supported frameworks or contexts (e.g., 'for JavaScript/TypeScript projects using Axios, Fetch, or similar HTTP clients') to improve distinctiveness
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Request Interceptor Creator') without describing any concrete actions. There are no verbs explaining what the skill actually does - no mention of creating, configuring, modifying, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('request interceptor creator, request interceptor creator'). This is redundant and misses natural variations users might say like 'HTTP interceptor', 'middleware', 'request hooks', 'API middleware', or 'intercept requests'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'request interceptor' is somewhat specific to a particular programming concept, the lack of detail about what kind of interceptors (HTTP, GraphQL, etc.) or what frameworks/languages it supports means it could overlap with general API or middleware skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no substantive information. It contains only meta-descriptions of what a skill should do without any actual implementation guidance, code examples, or concrete instructions for creating request interceptors. The content fails every dimension by providing zero actionable value.
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 specific steps: 1) Identify interception points, 2) Implement interceptor logic, 3) Register interceptors, 4) Test/validate behavior
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific patterns like authentication header injection, request logging, retry logic, or error transformation
Add concrete examples of common interceptor use cases with before/after code snippets showing the interceptor implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for creating request interceptors. The entire content describes what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, no sequence, and no validation checkpoints for any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed materials, no examples, and no navigation to related resources despite mentioning 'Related Skills.' | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.