CtrlK
BlogDocsLog inGet started
Tessl Logo

supercast

Supercast integration. Manage Persons, Organizations, Deals, Leads, Projects, Pipelines and more. Use when the user wants to interact with Supercast data.

64

Quality

76%

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/supercast/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.

A highly actionable, well-structured CLI integration skill with concrete commands and a clear connection workflow including validation checkpoints. The main weaknesses are a redundant action-discovery section and a dangling 'Step 2' reference that hurt conciseness and workflow clarity.

Suggestions

Remove or merge the 'Popular actions' section into 'Searching for actions' to eliminate the duplicated `membrane action list` command and reduce token overhead.

Replace the undefined 'skip to Step 2' references with an explicit, labeled second step (e.g. '### 2. Search for actions') so the workflow sequence is unambiguous.

Trim explanatory prose such as 'so you can focus on the integration logic rather than auth plumbing' that restates what the preceding clause already conveys.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but the 'Popular actions' section repeats the `membrane action list` command already shown in 'Searching for actions', and a few explanatory sentences could be trimmed.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action run, request) with a clear flag table covering the common proxy cases.

5 / 5

Workflow Clarity

The connection workflow is clearly sequenced with explicit state-checking checkpoints and a poll-retry loop, but 'skip to Step 2' references a Step 2 that is never labeled.

4 / 5

Progressive Disclosure

Well-organized into clear sections in a single self-contained file with no need for external references; minor gaps such as the duplicated action-discovery section and the undefined Step 2 reference keep it just below 5.

4 / 5

Total

16

/

20

Passed

Description

78%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.

A solid description that names the integration, lists concrete managed entities, and includes an explicit 'Use when' trigger. It is distinct and specific, with only minor room to sharpen the trigger phrasing and add synonyms.

DimensionReasoningScore

Specificity

Lists several concrete entities to manage ('Persons, Organizations, Deals, Leads, Projects, Pipelines'), though the trailing 'and more' leaves minor coverage gaps.

4 / 5

Completeness

Explicitly states both what ('Manage Persons, Organizations...') and when ('Use when the user wants to interact with Supercast data'), though the 'when' trigger is somewhat generic.

4 / 5

Trigger Term Quality

Good keyword coverage with the app name 'Supercast' plus entity names users would naturally say, but lacks synonyms or file-extension-style variations.

4 / 5

Distinctiveness Conflict Risk

Names a specific app ('Supercast') giving it a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

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.