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 critically underdeveloped. It consists entirely of a skill name, a duplicated trigger phrase, and a generic category label, providing no information about what the skill actually does or when it should be selected. It would be nearly impossible for Claude to correctly choose 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.'
Include natural keyword variations users would actually say, such as 'GET request', 'POST vs PUT', 'REST methods', 'HTTP verbs', 'API request method', '.http files'.
| 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 distinct triggers, 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 with no substantive content. It repeatedly references 'http method helper' without ever defining what it does, providing examples of HTTP methods, showing code, or giving any actionable guidance. It fails on every dimension as it contains zero useful information for Claude to act on.
Suggestions
Replace the boilerplate with actual content: include a reference table of HTTP methods (GET, POST, PUT, PATCH, DELETE, OPTIONS, HEAD) with their semantics, idempotency, and safe/unsafe classification.
Add concrete, executable code examples showing how to implement each HTTP method in at least one framework (e.g., Express.js or FastAPI), with request/response examples.
Include a decision workflow: 'When to use which HTTP method' with specific criteria and validation steps (e.g., checking idempotency requirements, status code selection).
Add references to related detailed files (e.g., REST best practices, status code guide, authentication patterns) rather than just listing tags.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'http method helper' excessively, and provides zero actual technical content about HTTP methods or API development. | 1 / 3 |
Actionability | There are no concrete instructions, no code examples, no commands, and no specific guidance. 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 | The content is a flat, uninformative document with no references to detailed materials, no links to examples or API references, and no meaningful structure beyond boilerplate headings. | 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.