conditional-request-helper
Conditional Request Helper - Auto-activating skill for API Development. Triggers on: conditional request helper, conditional request helper Part of the API Development skill category.
34
0%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/15-api-development/conditional-request-helper/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 with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Implements HTTP conditional requests using ETags, If-Modified-Since, and If-None-Match headers to optimize API responses and reduce bandwidth.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about ETags, conditional headers, HTTP caching, 304 responses, If-None-Match, or cache validation in API endpoints.'
Remove the duplicated trigger term and replace with varied natural language terms users would actually use when needing help with conditional HTTP requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Conditional Request Helper' is just a name repeated, with no explanation of what it actually does (e.g., implementing ETags, If-Modified-Since headers, caching logic). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states a name and a vague category ('API Development') without any functional detail or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'conditional request helper' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'ETag', 'If-None-Match', 'HTTP caching', '304 Not Modified', 'conditional headers', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Development' is extremely broad and could conflict with many other API-related skills. There is nothing distinctive that would help Claude differentiate this skill from other API development tools. | 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 is a placeholder/template skill with no actual content about conditional HTTP requests. It contains only generic boilerplate that repeats the skill name in various phrasings without providing any actionable information about ETags, If-None-Match, If-Modified-Since, cache validation, or any other conditional request concepts. It is entirely non-functional as a skill.
Suggestions
Add concrete, executable code examples showing how to implement conditional requests (e.g., ETag generation, If-None-Match handling, returning 304 Not Modified responses) in at least one language/framework.
Define a clear workflow for adding conditional request support to an API endpoint, including validation steps such as testing with curl to verify correct 304 responses.
Replace all generic boilerplate sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') with actual technical content covering HTTP conditional request headers (ETag, Last-Modified, If-None-Match, If-Modified-Since) and their correct usage patterns.
Include specific examples of common pitfalls (e.g., weak vs strong ETags, handling PUT with If-Match for optimistic concurrency) to provide value beyond what Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about conditional requests (ETags, If-Modified-Since, etc.). Every section restates the skill name without adding value. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of conditional request headers, no HTTP status codes, no implementation patterns. It only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. Sections exist but contain no real content differentiation. There are no references to detailed materials or external files. | 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.