CtrlK
BlogDocsLog inGet started
Tessl Logo

thru

Thru integration. Manage data, records, and automate workflows. Use when the user wants to interact with Thru 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/thru/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 body is a well-structured, actionable guide with concrete CLI commands, a clear connection state machine, and good sectioning. The main gaps are minor verbosity in the overview, abstract placeholders in a few examples, and no explicit validation steps before destructive action runs or proxy writes.

Suggestions

Trim the explanatory preamble ('Think of it as a secure alternative to email attachments and FTP servers') since Claude does not need the platform explained.

Replace abstract placeholders like 'QUERY' in the action-list examples with a concrete intent (e.g. 'send file') and show how to read inputSchema/outputSchema before running.

Add an explicit verify step before destructive or batch operations, e.g. confirm the chosen action and inspect its inputSchema before 'membrane action run', and check the proxy response status before treating it as success.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and only minor over-explanation (e.g. 'Think of it as a secure alternative to email attachments and FTP servers' and the overview preamble), so it lands just above the 'mostly efficient' midpoint but not fully lean.

4 / 5

Actionability

It provides concrete, mostly copy-paste-ready commands for install, login, connection, action listing, running, and proxying with a clear options table; minor gaps (e.g. abstract 'QUERY' intent placeholder, generic CONNECTION_ID) keep it just below fully executable.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling loop with feedback, but destructive or batch operations like 'action run' and proxy requests lack explicit pre-flight validation, so it sits at 'clear sequence with most checkpoints' rather than 5.

4 / 5

Progressive Disclosure

Content is well organized into clear sections (overview, install, auth, connecting, actions, popular actions, proxy, best practices) with no deep nested references; since no bundle files exist the overview is self-contained, with only minor bulk that could conceptually be split, placing it just above the 'good structure' anchor.

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 answers both what and when with a clear brand niche, but the capability verbs are generic and it lacks the natural trigger phrases users would actually say. Tightening the action list and adding concrete user-facing terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with specific Thru actions such as 'Send and receive large files, manage transfer jobs, and automate file workflows'.

Add natural user phrases to the trigger clause, e.g. 'Use when the user wants to send or receive large files via Thru, check transfer status, or automate Thru workflows'.

Include concrete trigger terms like 'large files', 'file transfer', and 'transfer jobs' so the description matches language users actually say.

DimensionReasoningScore

Specificity

The description names the domain (Thru) and a few concrete action categories ('Manage data, records, and automate workflows') but the actions are broad and generic rather than enumerating specific operations like send/transfer files, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It states what the skill does ('Manage data, records, and automate workflows') and provides an explicit trigger ('Use when the user wants to interact with Thru data'); both what and when are present, though the 'when' could be more specific.

4 / 5

Trigger Term Quality

It includes 'Thru' and 'data, records, workflows' but lacks the natural phrases and synonyms a user would actually say ('transfer files', 'send large files', 'Thru API'); relevant keywords are present but common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The brand name 'Thru' gives it a clear niche with minimal conflict risk, though the generic 'Manage data, records, and automate workflows' portion could overlap with other integration skills, keeping it just below a 5.

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.