CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

httpyac

Work with httpyac .http files for HTTP, gRPC, GraphQL, and WebSocket API testing and contract validation. Use when creating or executing API test requests.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/httpyac/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, reasonably lean overview with concrete commands, a clear workflow, and useful troubleshooting guidance. Its critical defect is that HTTPYAC-RULES.md — referenced twice as the repository of all protocol rules and the first required step — does not exist in the bundle, leaving the skill an index without its target.

Suggestions

Add the missing HTTPYAC-RULES.md (or place it under references/ and update the links) so the body's primary reference resolves; the skill currently defers all protocol-specific content to a file that is not in the bundle.

Include one short inline example of an actual .http request (e.g., a named gRPC or REST request with variables and an assertion) so the common case is actionable even before opening the rules file.

Insert an explicit validation checkpoint in the Example Workflow, e.g., 'Execute and confirm the response status/assertions pass before adding further requests', to close the sequence's feedback loop.

DimensionReasoningScore

Conciseness

Mostly lean list-based content with no explanation of concepts Claude already knows; only minor trimmable redundancy remains (the CLI command 'httpyac -o=body -a ./path/to/file.http' appears verbatim twice, and 'When to Use This Skill' echoes the frontmatter description), matching anchor 4 rather than anchor 5.

4 / 5

Actionability

Provides concrete executable commands ('httpyac -o=body -a ./path/to/file.http'), exact syntax rules ('{{variable}} not {variable}'), and named MCP tools, matching anchor 4; it falls short of anchor 5 because no inline example of an actual .http request is shown for the common cases, leaving minor gaps.

4 / 5

Workflow Clarity

The 9-step Example Workflow is clearly sequenced and the Troubleshooting section covers error recovery for each failure mode, matching anchor 4; it is not anchor 5 because no explicit validation checkpoint (e.g., verify execution succeeded) appears before adding assertions, though no destructive/batch cap applies.

4 / 5

Progressive Disclosure

The body correctly structures itself as an overview pointing one level deep to HTTPYAC-RULES.md, but that file is absent from the bundle (no HTTPYAC-RULES.md, references/, scripts/, or assets/ exist), so the primary navigation target is dead and the skill's actual content is inaccessible; scored against the real bundle structure this lands at anchor 2, above anchor 1 only because the body itself is well-organized rather than a monolith.

2 / 5

Total

14

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed: it states a clear niche (httpyac .http files), enumerates four supported protocols, and includes an explicit 'Use when' trigger clause. Minor gaps in trigger-term synonyms and 'when'-clause breadth keep it just below the top anchors.

DimensionReasoningScore

Specificity

Names the domain ('httpyac .http files') plus several concrete actions ('API testing and contract validation', 'creating or executing') across four protocols, but 'Work with' is a generic verb and coverage is not comprehensive, matching anchor 4 rather than 5.

4 / 5

Completeness

Both 'what' and an explicit 'Use when creating or executing API test requests' trigger are present, but the 'when' clause is narrower than anchor 5's concrete trigger phrases (it omits triggers like mentions of .http files or debugging API requests), landing on anchor 4.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('.http files', 'API testing', 'gRPC', 'GraphQL', 'WebSocket'), but a few natural terms are missing such as 'REST', '.rest' (a httpyac-supported extension), or 'send requests', which fits anchor 4 and is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

'httpyac .http files' is a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5; it is not anchor 4 because the tool-specific trigger terms make overlap unlikely.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

forgoty/dotfiles

Path

dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/httpyac/SKILL.md

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.