CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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

50%

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

The body is well-organized and assumes Claude's competence, but it defers its core technical content to HTTPYAC-RULES.md, which is missing from the bundle, and lacks inline validation checkpoints in its main workflow.

Suggestions

Ship the referenced HTTPYAC-RULES.md (or move the protocol-specific rules inline) so the prominent [HTTPYAC-RULES.md] links resolve to real content.

Add explicit validation checkpoints inside the Example Workflow (e.g., 'verify the proto path resolves before adding the import'; 'check gRPC status code 0 before adding assertions') rather than relegating all checks to Troubleshooting.

Tighten or consolidate the Rule Categories Overview and Rule Severity Levels, which preview HTTPYAC-RULES.md content, to reduce duplication with that referenced file.

DimensionReasoningScore

Conciseness

The body is organized and mostly free of concepts-Claude-already-knows padding, but the Rule Categories Overview and Rule Severity Levels preview content that lives in HTTPYAC-RULES.md, and the detailed Troubleshooting section could be tightened or deferred.

2 / 3

Actionability

Concrete elements exist (CLI flags `httpyac -o=body -a`, named MCP tools, specific troubleshooting checks), but the core protocol-specific request syntax is deferred to HTTPYAC-RULES.md rather than present in the body, leaving key details incomplete.

2 / 3

Workflow Clarity

The Example Workflow gives a clear 9-step sequence and Troubleshooting provides error-recovery guidance, but validation checkpoints are not embedded inline in the workflow (e.g., 'verify path before proceeding'), so checkpoints are implicit rather than explicit.

2 / 3

Progressive Disclosure

The structure is well-designed — a clear overview signaling one-level-deep references to HTTPYAC-RULES.md — but that referenced file is not present in the bundle (no references/scripts/assets dirs), so the navigation link is a dead end.

2 / 3

Total

8

/

12

Passed

Description

90%

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

A strong, well-structured description that clearly answers both what and when, with distinct triggers tied to a specific tool. The only weakness is that the action verbs are somewhat abstract ('work with', 'testing') rather than concrete.

DimensionReasoningScore

Specificity

Names the domain (httpyac .http files) and enumerates four protocols plus 'testing and contract validation', but the action verbs ('Work with', 'testing') are abstract rather than concrete like 'extract', 'fill', 'merge'.

2 / 3

Completeness

Explicitly states both what it does ('Work with httpyac .http files for ... API testing and contract validation') and when to use it ('Use when creating or executing API test requests').

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'httpyac', '.http files', 'HTTP/gRPC/GraphQL/WebSocket', 'API testing', 'API test requests' — with good variation across protocols.

3 / 3

Distinctiveness Conflict Risk

The httpyac/.http-file niche is highly specific with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
forgoty/dotfiles
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.