CtrlK
BlogDocsLog inGet started
Tessl Logo

orca-scan

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

61

Quality

71%

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

Quality

Content

76%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 is highly actionable with copy-paste-ready Membrane CLI commands and good structure, but it lacks validation/verification checkpoints for data and batch operations, capping workflow clarity despite strong actionability.

Suggestions

Add explicit validation steps after connection creation and action runs (e.g. 'Verify the connection id appears in `connection list` before running actions').

Add a verify/retry feedback loop for batch or mutating actions so failures are caught and corrected before proceeding.

Trim redundancy between the 'Searching for actions', 'Popular actions', and 'Running actions' sections to improve token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and short explanations, though the opening overview paragraph and the 'Popular actions' / 'Searching for actions' sections carry some redundancy that could be tightened.

4 / 5

Actionability

It provides fully executable, copy-paste-ready CLI commands covering connection setup, action discovery, running actions, and proxy requests, with a clear options table for common cases.

5 / 5

Workflow Clarity

Setup and connection steps are sequenced, but for batch/data operations there are no validation or verification checkpoints (e.g. confirming a connection succeeded, verifying an action result), which caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview under 130 lines with no bundle files and clear section structure, so progressive disclosure is fully satisfied by well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

66%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 identifies the Orca Scan niche and includes both a 'what' and 'Use when' clause, but its actions are generic and it omits natural trigger terms (barcodes, inventory, scanning) users would actually say.

Suggestions

Add concrete Orca Scan-specific actions like 'scan barcodes, manage sheets, and track inventory' to improve specificity.

Include natural user trigger terms such as 'barcodes', 'QR codes', 'inventory', or 'scans' so the description matches how users phrase requests.

Tighten the 'Use when' clause with concrete triggers, e.g. 'Use when the user wants to scan barcodes, manage Orca sheets, or query inventory records.'

DimensionReasoningScore

Specificity

It names the domain and a couple of concrete actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensive, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

It answers both 'what' (Orca Scan integration managing data, records, workflows) and 'when' ('Use when the user wants to interact with Orca Scan data'), though the 'when' could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

It includes relevant keywords ('Orca Scan', 'data', 'records', 'workflows') and a 'Use when' clause, but lacks common user variations/synonyms like 'barcodes', 'inventory', 'scanning', or 'sheets', leaving keyword coverage partial.

3 / 5

Distinctiveness Conflict Risk

It names a clear niche ('Orca Scan integration') with a distinct product-specific trigger, making conflict with other skills minimal and the trigger highly distinguishable.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.