vscode-httpyac-config

Configure VSCode with httpYac for API testing and automation. This skill should be used specifically when converting API documentation to executable .http files (10+ endpoints), setting up authentication flows with pre-request scripts, implementing request chaining with response data, organizing multi-file collections with environment management, or establishing Git-based API testing workflows with CI/CD integration.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%

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

A well-structured, highly actionable skill body with clear phased workflow and validation checkpoints. Its main weaknesses are some redundant sectioning that hurts token efficiency and broken/missing reference linkage (two referenced files absent, one bundle file orphaned).

Suggestions

Create or restore references/WORKFLOW_GUIDE.md and references/TROUBLESHOOTING.md (or repoint their links to the files that actually hold that content) so every '📖 Reference' link resolves.

Either reference references/REQUEST_DEPENDENCIES.md from the body (e.g. in the request-chaining/auth sections) or remove it from the bundle to keep the file set coherent.

Collapse the duplicate quality/syntax checklists (Post-Creation Checklist vs. Quality Checklist vs. Success Criteria) into one and trim the repeated inline syntax examples that the references already cover to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with templates, tables, and checklists rather than prose, but it retains redundant sectioning and restates guidance (e.g. repeated '📖 Reference' pointers, 'Common Issues' plus 'COMMON_MISTAKES.md', quality checklists appearing twice) that could be tightened; a couple of inline code blocks also re-teach syntax the references already cover.	2 / 3
Actionability	Provides executable httpYac snippets (real POST/GET blocks, exports patterns, .gitignore content), specific template-copy sequences, concrete grep navigation patterns, and copy-paste-ready decision tables — directly instructable rather than abstract.	3 / 3
Workflow Clarity	Sequenced into clear phases (Discovery → Template Creation → Authentication → … → CI/CD) with decision criteria, explicit validation checkpoints ('Verify syntax against references/SYNTAX.md', post-creation and quality checklists), and error-recovery guidance via the Common Issues table.	3 / 3
Progressive Disclosure	Good one-level-deep structure overall, but two heavily-signaled references (references/WORKFLOW_GUIDE.md and references/TROUBLESHOOTING.md) do not exist in the bundle, and one present file (references/REQUEST_DEPENDENCIES.md) is never referenced — navigation is partly broken and the bundle is under-utilized, so it falls short of clean, complete cross-file organization.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 description that explicitly states both capability and when-to-use triggers with concrete scenarios. Voice is appropriately third person and it avoids vague fluff, though trigger phrasing could include more natural lay variations of API-testing requests.

Suggestions

Add common-noun trigger variations a user might naturally say (e.g. 'test a REST API', 'API testing') alongside the httpYac-specific terms to broaden trigger term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'converting API documentation to executable .http files', 'setting up authentication flows with pre-request scripts', 'implementing request chaining with response data', 'organizing multi-file collections with environment management', and 'establishing Git-based API testing workflows with CI/CD integration'.	3 / 3
Completeness	Clearly answers 'what' ('Configure VSCode with httpYac for API testing and automation') AND 'when' with an explicit 'This skill should be used specifically when...' trigger clause enumerating concrete scenarios.	3 / 3
Trigger Term Quality	Uses relevant terms like 'API documentation', 'executable .http files', 'authentication', 'request chaining', 'CI/CD', but leans on technical/proper-noun framing ('httpYac', 'pre-request scripts') and omits the common lay variations a user might naturally say (e.g. 'API testing', 'test an API', 'REST endpoints').	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (VSCode + httpYac + .http files) with distinct triggers unlikely to fire for general API or testing skills; the specificity of 'httpYac' and '.http files' keeps it non-overlapping.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: libukai/awesome-agent-skills
Path: plugins/vscode-extensions-toolkit/skills/vscode-httpyac-config/SKILL.md
Commit: fef729a

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.