Name: purple-sonar
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

purple-sonar

Purple Sonar integration. Manage Organizations. Use when the user wants to interact with Purple Sonar data.

Quality

65%

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/purple-sonar/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 content is actionable and well-sequenced with real validation feedback loops, but it is marred by a leaked LLM-refusal line, a broken "Step 2" reference, and minor redundancy. Cleaning the noise and fixing the cross-reference would raise conciseness and workflow clarity.

Suggestions

Delete the leaked refusal line ("I don't have enough information to do that...") and other filler so the body is lean.

Fix the broken "Step 2" reference and make section numbering consistent (the connect→ready flow references a step that is never defined).

Merge the redundant "Popular actions" section into "Searching for actions" to remove duplicated discovery instructions.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the leaked refusal line ("I don't have enough information to do that...") and filler like "Use action names and parameters as needed." add unnecessary tokens, fitting anchor 3 rather than 4.	3 / 5
Actionability	It provides many concrete, copy-paste commands (install, login, connection ensure, action run/list, request) with minor gaps such as the vague "Popular actions" section and unresolved placeholders.	4 / 5
Workflow Clarity	The install→auth→connect→poll-for-READY→search→run sequence is clear with state-check feedback loops, but the undefined "Step 2" reference and inconsistent numbering are minor gaps that keep it below 5.	4 / 5
Progressive Disclosure	With no bundle files, the single well-sectioned SKILL.md is appropriately organized; minor redundancy between "Popular actions" and "Searching for actions" keeps it just under 5.	4 / 5
	Total	15 / 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 covers what and when with a distinct named-product trigger, but is thin on specific actions and natural-term variations. Expanding the action list and trigger synonyms would lift specificity and trigger quality.

Suggestions

List more concrete Purple Sonar actions (e.g., search documents, fetch project details) instead of the single generic "Manage Organizations".

Add natural trigger variations and synonyms (e.g., "Purple Sonar data", "Sonar projects", "search Sonar documents") to broaden keyword coverage.

Tighten the when-clause with multiple concrete trigger scenarios to approach a comprehensive completeness score.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names the Purple Sonar domain with one concrete action, but coverage is not comprehensive — it lacks the several specific actions needed for a 4.	3 / 5
Completeness	It has both a clear what ("Manage Organizations") and an explicit when ("Use when the user wants to interact with Purple Sonar data"), but the single trigger phrase is not comprehensive enough for a 5.	4 / 5
Trigger Term Quality	"Purple Sonar", "Organizations", and "interact with Purple Sonar data" are relevant natural terms, but common variations and synonyms are missing, so it stops at anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The named product "Purple Sonar" creates a clear niche with low conflict risk, though the generic "Manage Organizations" leaves minor overlap with related skills, keeping it just below 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/purple-sonar/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.