CtrlK
BlogDocsLog inGet started
Tessl Logo

white-swan

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/white-swan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 strong, executable CLI guidance with decent section structure, but is dragged down by a leftover AI placeholder line, inconsistent step numbering with a dangling 'Step 2' reference, and missing validation for destructive proxy/action operations.

Suggestions

Remove the placeholder line 'I don't have enough information about that app...' (line 17); it is nonsensical inside a skill and wastes tokens.

Fix the step numbering: label the connect step '1a' to match '1b', and add an explicitly labeled 'Step 2' section that the 'skip to Step 2' references point to.

Add a validation/verification checkpoint before destructive proxy requests (e.g., GET to preview before POST/PUT/DELETE) so the workflow clears the destructive-operation cap on workflow_clarity.

DimensionReasoningScore

Conciseness

Mostly efficient with command-focused examples, but includes a nonsensical placeholder line ('I don't have enough information about that app...') and minor fluff ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed.

3 / 5

Actionability

Provides many concrete, copy-paste-ready bash commands (install, login, connection ensure, action list/run, request) covering common cases; held below 5 by generic placeholders like 'Use action names and parameters as needed' and the leftover placeholder text.

4 / 5

Workflow Clarity

The connect-then-poll-state sequence has some checkpoints, but the proxy and action-run sections permit destructive operations (DELETE/PUT) with no validation step, capping clarity at 3; numbering is also inconsistent (a '1b' with no '1a', and a dangling 'Step 2' reference).

3 / 5

Progressive Disclosure

Well-organized into clear headed sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with a docs link; no bundle files exist and content is appropriately sectioned, with only minor organization gaps from the broken step numbering.

4 / 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 answers both 'what' and 'when' with an explicit trigger clause and is anchored to a distinct app, but its action verbs are generic and the trigger phrasing could be more varied and specific.

DimensionReasoningScore

Specificity

Names the domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') without specific concrete operations, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with White Swan data'); the 'Use when' clause is present, though the trigger is somewhat generic rather than fully specific.

4 / 5

Trigger Term Quality

Includes relevant keywords ('White Swan', 'data', 'records', 'interact') but lacks common variations or synonyms a user might naturally say; 'interact with White Swan data' covers some natural phrasing but is limited.

3 / 5

Distinctiveness Conflict Risk

Tied to a specific named application (White Swan) with an app-scoped trigger, giving it a clear niche with minor overlap risk; the generic 'manage data, records' actions keep it just below the most distinct anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.