http-method-helper
Http Method Helper - Auto-activating skill for API Development. Triggers on: http method helper, http method helper Part of the API Development skill category.
34
0%
Does it follow best practices?
Impact
99%
1.02xAverage 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/http-method-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 lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing detail. 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., 'Recommends appropriate HTTP methods (GET, POST, PUT, PATCH, DELETE) for API endpoints, explains method semantics, and validates RESTful method usage.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about which HTTP method to use, REST API design, choosing between PUT and PATCH, or HTTP verb conventions.'
Replace the duplicated trigger term with diverse natural keywords users would actually say, such as 'HTTP request', 'REST method', 'GET vs POST', 'API endpoint methods', 'HTTP verbs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Http Method Helper' and 'Auto-activating skill for API Development' are vague labels with no explanation of what the skill actually does (e.g., selecting HTTP methods, generating request templates, validating method usage). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explanation of capabilities and no explicit 'Use when...' clause—only a redundant trigger phrase and a category label. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'http method helper' repeated twice, which is not a natural phrase a user would say. Missing natural terms like 'GET', 'POST', 'PUT', 'DELETE', 'REST API', 'HTTP request', 'API endpoint', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'API Development' is extremely broad and could overlap with many other API-related skills. Without specific actions or clear scope, this skill would be indistinguishable 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 skill is an empty template/placeholder with no substantive content. It contains no actionable information about HTTP methods, no code examples, no concrete guidance, and no real workflow. Every section is generic boilerplate that could apply to any topic by swapping the phrase 'http method helper.'
Suggestions
Replace the entire body with actual content about HTTP methods (GET, POST, PUT, PATCH, DELETE) including when to use each, idempotency rules, and status code mappings — with concrete code examples.
Add executable code examples showing HTTP method usage in at least one framework (e.g., Express.js routes, FastAPI endpoints, or curl commands) that are copy-paste ready.
Define a clear workflow for choosing the correct HTTP method for a given API operation, including validation steps like checking idempotency and safety properties.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill itself rather than teaching the actual skill content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the trigger phrase 'http method helper' excessively, and provides zero domain-specific information about HTTP methods, API development, or any concrete topic. | 1 / 3 |
Actionability | There is no concrete guidance, no code, no commands, no examples, and no specific instructions. Every section is vague and abstract — 'Provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints — just generic claims about capabilities without any actual process described. | 1 / 3 |
Progressive Disclosure | No bundle files exist, no references to external documents, and the content itself is a shallow placeholder with no meaningful structure or organization of information across sections. | 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
3a2d27d
- 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.