Name: insomnia
Rating: 55.2 (1 reviews)
Author: membranedev

insomnia

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

Quality

63%

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/insomnia/SKILL.md

Quality

Content

63%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 content is highly actionable with copy-paste CLI commands and a clear connection workflow including state checkpoints. Its weaknesses are mild verbosity in the intro, an underdeveloped 'Popular actions' section, and a monolithic structure with no reference files for deeper material.

Suggestions

Trim the opening paragraph that explains what Insomnia is and remove filler like 'Use action names and parameters as needed' to improve conciseness.

Populate 'Popular actions' with actual common action examples instead of restating the discovery command, or move that detail into a reference file.

Split the proxy flag reference and extended action catalog into a separate references file (e.g., REFERENCE.md) and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation such as the opening product description of what Insomnia is and filler like 'Use action names and parameters as needed', fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request with a flag table), but relies on placeholders like CONNECTION_ID and the 'Popular actions' section only repeats the discovery command instead of showing actual popular actions, leaving minor gaps consistent with 'mostly executable guidance; minor gaps'.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll-for-ready → search → run sequence is clear with explicit state-based checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but references an undefined 'Step 2' and has minor validation gaps, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The content is section-organized with clear headers, but everything is inlined into a single SKILL.md with no bundle/reference files, so material like the proxy flag table and action discovery that could live in separate references is not split out, fitting 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

62%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 successfully pairs a clear trigger clause with a named domain, giving it solid completeness and distinctiveness. Its main weakness is vague capability language ('data, records, workflows') that lacks concrete, specific actions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Insomnia actions such as 'send REST/GraphQL/gRPC requests, manage request collections, and inspect responses'.

Expand the trigger clause to name natural user phrases like 'debug APIs', 'test endpoints', or 'work with request collections' to broaden trigger coverage.

Add file-format or feature synonyms (e.g., 'REST', 'GraphQL', 'gRPC', 'collections', 'environments') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The description names the Insomnia domain and lists several actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor; it does not reach 4 because the actions lack specificity.	3 / 5
Completeness	Both 'what' ("Manage data, records, and automate workflows") and 'when' ("Use when the user wants to interact with Insomnia data") are present and explicit, but the 'what' is only loosely concrete, so it fits 'has both what and when; when could be more explicit or specific' rather than the fully concrete 5.	4 / 5
Trigger Term Quality	It includes the strong brand keyword "Insomnia" and the natural phrase "interact with Insomnia data", but misses common variations or synonyms, matching the 'some relevant keywords but missing common variations' anchor rather than the comprehensive 4.	3 / 5
Distinctiveness Conflict Risk	The named app "Insomnia" and trigger "interact with Insomnia data" carve a clear niche with low conflict risk, but the generic 'Manage data, records, and automate workflows' phrasing introduces minor overlap risk, placing it at 'mostly distinct; minor overlap risk' instead of 5.	4 / 5
	Total	14 / 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/insomnia/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.