CtrlK
BlogDocsLog inGet started
Tessl Logo

suitedash

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/suitedash/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 delivers concrete, executable Membrane CLI guidance with a well-sequenced connection workflow and status-based checkpoints. Main weaknesses are an undefined 'Step 2' cross-reference and a large inline entity list that would benefit from a separate reference file.

Suggestions

Resolve the dangling 'skip to Step 2' / '1b' references by either defining Step 1a/Step 2 explicitly or rewording to forward references like 'skip to Running actions'.

Move the 50-item SuiteDash entity inventory into a references/entities.md file and link to it, keeping the body to the most-used entity groups.

Add one complete proxy example (method, header, data) to make the proxy section as copy-paste ready as the action-run examples.

DimensionReasoningScore

Conciseness

The body is mostly efficient with command examples and a flag table, but the 50-item SuiteDash entity inventory and light explanations of Membrane auth are minor over-explanation that could be trimmed.

4 / 5

Actionability

Concrete executable commands (login, connection ensure, action run, request) with flag options and input examples cover the common cases; minor gaps remain around the placeholder QUERY and a missing full proxy example.

4 / 5

Workflow Clarity

Connection setup is a clear sequenced flow with status-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling loop, but the undefined 'Step 2' reference and '1b' without a '1a' leave minor gaps.

4 / 5

Progressive Disclosure

No bundle files are provided, so the single self-contained SKILL.md carries well-organized sections; the inline 50-item entity inventory is the one block that could be split into a reference, keeping this just below a 5.

4 / 5

Total

16

/

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 includes a 'Use when...' trigger and names a concrete domain, but the action wording ('Manage Organizations') is too generic to capture SuiteDash's actual scope. Expanding the trigger terms with concrete entity keywords would raise completeness and trigger quality.

Suggestions

Replace the generic 'Manage Organizations' with several concrete actions the integration supports, e.g. 'manage CRM leads, create invoices, update project tasks, and respond to support tickets'.

Broaden the trigger clause with natural user phrasing such as 'Use when the user wants to manage SuiteDash CRM leads, invoices, projects, tickets, or client data'.

Mention at least one file-type or synonym trigger if the integration handles imports/exports (e.g. 'import SuiteDash contacts from CSV').

DimensionReasoningScore

Specificity

Names the domain (SuiteDash) and one concrete action ('Manage Organizations'), but the single generic verb does not convey the breadth of capabilities (CRM, invoicing, tickets, projects) the body enumerates.

3 / 5

Completeness

Both 'what' (SuiteDash integration, Manage Organizations) and 'when' ('Use when the user wants to interact with SuiteDash data') are present, though the 'when' clause is generic rather than concrete.

4 / 5

Trigger Term Quality

The product name is a usable trigger and 'interact with SuiteDash data' is present, but it lacks the natural entity keywords (CRM, invoices, leads, tickets) users would actually say, so common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

The named product SuiteDash gives it a clear niche unlikely to trigger the wrong skill, with only minor overlap risk against other generic CRM/business-management 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.