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
Quality
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 severely lacking across all dimensions. It provides no concrete actions, no natural trigger terms users would say, no explicit 'when to use' guidance, and is too generic to distinguish from other API-related skills. The description appears to be auto-generated boilerplate rather than a thoughtful explanation of the skill's purpose.
Suggestions
Add specific actions the skill performs, e.g., 'Implements HTTP conditional requests using ETag, If-None-Match, If-Modified-Since, and Last-Modified headers for efficient caching and bandwidth optimization.'
Include a 'Use when...' clause with natural trigger terms: 'Use when implementing HTTP caching, handling 304 Not Modified responses, working with ETags, or optimizing API bandwidth.'
Add concrete file types or protocols: 'Works with REST APIs, HTTP headers, cache validation, and conditional GET/PUT requests.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Conditional Request Helper' and 'API Development' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no 'Use when...' clause or explicit trigger guidance). Both components are missing or very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'conditional request helper' repeated twice, which is technical jargon. Missing natural terms users would say like 'ETag', 'If-Modified-Since', 'caching headers', '304 response', or 'HTTP caching'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Development' is extremely generic and would conflict with many other API-related skills. 'Conditional Request Helper' is vague without explaining what conditional requests are or how this differs from other API skills. | 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 essentially an empty template with no actual content. It describes what a conditional request helper skill would do but provides zero actionable guidance, code examples, or concrete instructions. The entire content is meta-description about the skill rather than the skill itself.
Suggestions
Add concrete code examples showing how to implement conditional requests using ETags, If-Match, If-None-Match, If-Modified-Since headers
Include specific HTTP status codes (304 Not Modified, 412 Precondition Failed) and when they apply
Provide a clear workflow for implementing conditional GET vs conditional PUT/PATCH/DELETE operations
Remove all meta-description boilerplate ('This skill provides...', 'When to Use...') and replace with actual implementation guidance
| 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 implement conditional requests. The content only describes what the skill supposedly does without teaching anything. | 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 for any process. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual implementation details, references, or examples. There's nothing to disclose progressively because there's no substantive content. | 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.