Name: whistic
Rating: 52.8 (1 reviews)
Author: membranedev

whistic

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

Quality

59%

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

Quality

Content

56%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 skill delivers executable, well-sequenced CLI guidance with real feedback loops for connection handling. Its biggest drag is a ~150-line padded entity list that bloats the context window and should either be moved to a reference file or removed.

Suggestions

Remove or move the ~150-item 'Whistic Overview' noun list into a separate references file (e.g. entities.md); it adds padding without actionable value.

Add one concrete end-to-end example that runs an actual Whistic action with real parameters (not just CONNECTION_ID placeholders) to lift actionability.

Add a validation/confirmation checkpoint before destructive proxy requests (e.g. -X DELETE) so the workflow clears the destructive-operation bar.

Dimension	Reasoning	Score
Conciseness	The 'Whistic Overview' is a ~150-item noun dump (Image, Video, Audio, Archive, Backup, Log, Risk Management…) that is pure padding Claude does not need, making the body noticeably verbose despite the rest of the doc being reasonably lean; it does not reach the 'severely verbose / explains known concepts' level 1, but the padded section is large enough to keep it below level 3.	2 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (npm install, membrane login, connection ensure, action run, request with a flags table), covering the common cases; it stays at level 4 rather than 5 because no example runs an actual Whistic action with real parameters — only placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checks (READY / BUILDING / CLIENT_ACTION_REQUIRED) and poll-then-re-poll feedback loops for error recovery, matching the 'clear sequence with most checkpoints present, minor gaps' anchor; it falls short of level 5 because there is no validation checkpoint before potentially destructive proxy calls (e.g. DELETE).	4 / 5
Progressive Disclosure	The body has reasonable section headers, but there are no bundle/reference files at all and the large entity list is inlined content that clearly belongs in a separate reference file, matching the 'some structure but content that should be separate is inline' anchor rather than the well-split level 4.	3 / 5
	Total	13 / 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 correctly pairs a 'what' with an explicit 'Use when...' trigger and is clearly anchored to the distinct Whistic platform. Its main weakness is generic, non-concrete action language and a thin set of trigger keywords beyond the product name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Whistic capabilities, e.g. 'Run vendor security questionnaires, track assessments, and pull framework findings'.

Broaden trigger keywords beyond just 'Whistic' to include natural phrases users say, e.g. 'vendor security assessments, questionnaires, third-party risk, TPRAs'.

Tighten the 'when' clause to name the triggering situations more specifically rather than the generic 'interact with Whistic data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Whistic integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Whistic-specific capabilities, so it sits at the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the more specific level 4.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Whistic data'), but the 'what' is generic, so it does not reach the fully concrete trigger-phrase level 5.	4 / 5
Trigger Term Quality	The only real keyword is 'Whistic' (reused in 'interact with Whistic data'); relevant but missing common variations or synonyms a user might naturally say, matching the 'some relevant keywords but missing variations' anchor rather than the fuller coverage of level 4.	3 / 5
Distinctiveness Conflict Risk	Anchoring to the specific Whistic platform gives it a clear niche with a distinct trigger and minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with adjacent data skills, keeping it just below level 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/whistic/SKILL.md
Commit: f484c82

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