Name: swaggerhub
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

swaggerhub

SwaggerHub integration. Manage APIs, Domains, Organizations. Use when the user wants to interact with SwaggerHub data.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/swaggerhub/SKILL.md

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 highly actionable with concrete Membrane CLI commands and a well-sequenced, state-checked connection workflow, but it pads an intro explaining SwaggerHub's purpose and lacks external reference files for bulk detail.

Suggestions

Trim the introductory paragraph explaining what SwaggerHub is and the API lifecycle; Claude already knows this — lead with the integration mechanics.

Dedupe the repeated "Membrane handles auth" statements to a single concise mention near the Authentication section.

Consider moving the proxy flags table and detailed clientAction field reference into a reference file and linking to it, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens by explaining what SwaggerHub is ("SwaggerHub is a platform for designing, building, and documenting APIs... Essentially, it helps teams streamline the entire API lifecycle") and restates Membrane's auth-handling in several places, padding Claude already knows.	3 / 5
Actionability	Provides copy-paste-ready `membrane` commands throughout (connection ensure, action run with --input, request proxy) plus a flags table, covering common cases with only minor placeholder gaps.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, though the action discovery/run sections are loosely sequenced without equivalent checkpoints.	4 / 5
Progressive Disclosure	Single SKILL.md with no bundle files; content is well-sectioned by headers and reasonably organized, though sections like the full flags table and proxy options are inlined where a reference file could help.	4 / 5
	Total	15 / 20 Passed

Description

73%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 answers both what and when with a clear product niche and explicit trigger guidance, but its action verbs ("Manage") are generic and it omits natural synonyms users might say.

Suggestions

Replace generic "Manage" with 2-3 concrete operations (e.g., "Create and version APIs, manage domains and organizations") to lift specificity.

Add natural trigger synonyms users say, such as "OpenAPI specs", "API definitions", or ".yaml/.json OpenAPI files", to broaden trigger-term coverage.

Expand the "Use when" clause with concrete trigger phrases (e.g., "Use when the user mentions SwaggerHub, OpenAPI specs, or wants to version an API").

Dimension	Reasoning	Score
Specificity	"Manage APIs, Domains, Organizations" names the domain and three target objects, but "Manage" is a generic verb rather than distinct concrete operations, so it sits at the domain+1-2-actions level rather than comprehensive coverage.	3 / 5
Completeness	Both "what" (Manage APIs, Domains, Organizations) and "when" (Use when the user wants to interact with SwaggerHub data) are present and explicit, but the "when" clause is general rather than listing concrete trigger phrases as the 5-anchor does.	4 / 5
Trigger Term Quality	Includes the natural product name "SwaggerHub" plus "APIs, Domains, Organizations" and an explicit "Use when..." phrase, giving good keyword coverage though it lacks common synonyms like OpenAPI or file extensions.	4 / 5
Distinctiveness Conflict Risk	The SwaggerHub product niche is distinct and product-specific, with triggers unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	16 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/swaggerhub/SKILL.md
Commit: f484c82

Reviewed: 4 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.