CtrlK
BlogDocsLog inGet started
Tessl Logo

whaly

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

56

Quality

65%

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/whaly/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, actionable integration guide built around concrete Membrane CLI commands and a state-aware connection workflow. Its main weaknesses are marketing-style padding and a dangling "Step 2" reference that slightly muddies the sequence.

Suggestions

Trim promotional phrasing (e.g., "so you can focus on the integration logic rather than auth plumbing") to keep the guide lean.

Fix the dangling "skip to Step 2" reference by adding explicit numbered Step 1 / Step 2 headers so the connection workflow is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes padded/marketing prose such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed.

3 / 5

Actionability

It provides concrete, copy-paste-ready bash commands for install, auth, connection, action search/run, and proxying, with minor gaps where placeholders like CONNECTION_ID and QUERY must be substituted by the reader.

4 / 5

Workflow Clarity

The connection flow has a clear sequence with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/ERROR) and a poll-act-repoll feedback loop, but references a "Step 2" with no matching header, leaving a minor sequencing gap.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clear sections (Overview, Working with Whaly, Popular actions, Best practices) with no nested references and only an external docs link, giving good structure with minor organization gaps rather than file-level disclosure.

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 clearly names the Whaly product and includes an explicit "Use when" trigger, satisfying both what and when. It is held back by generic action verbs and limited trigger-term variation rather than comprehensive, concrete capability listing.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Whaly capabilities (e.g., "query datasets, build dashboards, enrich models").

Expand the trigger clause with natural variations users might say (e.g., "use when the user mentions Whaly, dashboards, or dataset queries").

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Whaly domain and a couple of actions, but the verbs ("manage") are generic rather than concrete like extracting or filling, matching the anchor that lists 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It states the "what" ("Whaly integration. Manage data, records, and automate workflows.") and an explicit "Use when the user wants to interact with Whaly data" clause, but the trigger phrase is less rich than the level-5 example, placing it at the both-present-but-could-be-more-specific anchor.

4 / 5

Trigger Term Quality

The "Whaly" keyword and "interact with Whaly data" are relevant natural triggers, but coverage lacks common variations or synonyms beyond data/records/workflows, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "Whaly" in both the what and when clauses gives a clear niche with minimal conflict, though the broad action language ("manage data, automate workflows") creates minor overlap risk with generic data/automation skills.

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.