Name: rapidoc
Rating: 46.400000000000006 (1 reviews)
Author: membranedev

rapidoc

RapiDoc integration. Manage data, records, and automate workflows. Use when the user wants to interact with RapiDoc data.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

58%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 delivers actionable, executable CLI commands with clear section structure, but it repeats content, explains concepts Claude already knows, and references an undefined 'Step 2' which breaks the workflow sequence.

Suggestions

Define or remove the undefined 'Step 2' reference so the connection -> search -> run workflow is a coherent sequence.

Remove the duplicate action-discovery command (it appears in both 'Searching for actions' and 'Popular actions') to reduce token cost.

Trim explanatory padding like 'so you can focus on the integration logic rather than auth plumbing' that restate what Claude can infer from the commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command snippets, but it explains concepts Claude already knows (e.g. 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing') and repeats the action-discovery command twice, so it could be tightened.	3 / 5
Actionability	It provides concrete, copy-pasteable commands (membrane login, connection ensure, action run, request) with flag tables and JSON examples; minor gaps like an undefined 'Step 2' reference and placeholder CONNECTION_ID keep it just below fully executable.	4 / 5
Workflow Clarity	There is a rough connect -> search -> run sequence with state-polling checkpoints, but it references a 'Step 2' that is never defined and lacks explicit validation/verification for operations that mutate state, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	Content is well-organized into headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to defer to; structure is clear though some inline material (the proxy flag table) could live separately.	4 / 5
	Total	14 / 20 Passed

Description

38%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 names the RapiDoc domain and includes a trigger clause, but its actions are generic ('manage', 'automate workflows') rather than describing concrete RapiDoc/OpenAPI capabilities, and it lacks natural trigger keywords like 'OpenAPI' or 'API spec'.

Suggestions

Replace generic verbs with concrete RapiDoc capabilities, e.g. 'Visualize and explore OpenAPI specifications, inspect REST API endpoints, and configure documentation settings.'

Add natural trigger terms users would say, such as 'OpenAPI', 'Swagger', 'API spec', or 'REST documentation', so the skill triggers on real phrasing.

Tighten the 'Use when' clause to specific scenarios, e.g. 'Use when the user wants to view or interact with an OpenAPI/Swagger spec in RapiDoc.'

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' — the domain (RapiDoc) is named but the actions ('manage', 'automate workflows') are generic and not tied to concrete RapiDoc capabilities like visualizing or exploring OpenAPI specs.	2 / 5
Completeness	It has a 'Use when the user wants to interact with RapiDoc data' clause (a weak 'when') and a vague 'what' ('Manage data, records, and automate workflows'), but the 'what' does not describe what the skill concretely does, capping completeness at 3.	3 / 5
Trigger Term Quality	The only user-facing term is 'RapiDoc data'; natural phrases a user would say (e.g. 'OpenAPI', 'Swagger', 'API spec', 'REST documentation') are absent, leaving generic language rather than natural keywords.	2 / 5
Distinctiveness Conflict Risk	Naming 'RapiDoc' provides some specificity, but 'Manage data, records, and automate workflows' is broad enough to overlap with general data/integration skills, so it is only somewhat distinct.	3 / 5
	Total	10 / 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/rapidoc/SKILL.md
Commit: f484c82

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