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
Quality
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 provides only a skill name and category without explaining what the skill actually does, what specific HTTP methods it helps with, or when Claude should select it. The repeated trigger term suggests auto-generated content that wasn't properly customized.
Suggestions
Add specific capabilities: describe what HTTP method operations this skill performs (e.g., 'Recommends appropriate HTTP methods (GET, POST, PUT, DELETE, PATCH) based on API operation intent, explains method semantics and idempotency')
Add a 'Use when...' clause with natural trigger terms like 'which HTTP method', 'REST API design', 'GET vs POST', 'API endpoint', 'HTTP verb'
Differentiate from other API skills by specifying the unique focus on HTTP method selection/guidance rather than general API development
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Http Method Helper' is just a name, and 'Auto-activating skill for API Development' is vague abstract language with no specific capabilities listed. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague category mention, and has no 'Use when...' clause or explicit trigger guidance. Both what and when are missing or very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'http method helper' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'GET', 'POST', 'REST', 'API request', 'HTTP verbs', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'API Development' is extremely broad and would conflict with many other API-related skills. There's nothing distinguishing this from other API tools, REST clients, or HTTP-related 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 entirely template boilerplate with no actual content about HTTP methods. It contains no executable code, no concrete guidance, and no real information - just self-referential descriptions of what the skill claims to do. The content fails every dimension of the rubric.
Suggestions
Replace the entire content with actual HTTP method guidance: include a quick reference table of GET, POST, PUT, PATCH, DELETE with their semantics and idempotency properties
Add concrete, executable code examples showing proper HTTP method usage in at least one language/framework
Include specific guidance on method selection criteria (e.g., when to use PUT vs PATCH, safe vs unsafe methods)
Remove all meta-descriptions about the skill itself and focus entirely on actionable HTTP method content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about HTTP methods. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual HTTP method information. The skill describes what it claims to do rather than providing any executable or actionable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. The content lists vague capabilities but provides no steps, sequences, or processes for actually helping with HTTP methods. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no structure pointing to detailed materials. There are no references to other files or organized sections for discovery. | 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.