CtrlK
BlogDocsLog inGet started
Tessl Logo

tisane-labs

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

57

Quality

66%

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/tisane-labs/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 is highly actionable with executable CLI commands and a solid connection-state workflow, weakened only by minor verbosity and an implied rather than explicitly numbered overall sequence. It is well-structured for a single-file skill.

Suggestions

Trim the marketing intro and 'rather than auth plumbing' filler to assume Claude's competence and save tokens.

Add a short numbered overview of the full flow (install → login → connect → search → run) so the end-to-end sequence is explicit, and reconcile the dangling 'Step 2' reference.

Consider moving the proxy flags table and clientAction state-machine detail into a separate reference file to keep the overview lean.

DimensionReasoningScore

Conciseness

The body is mostly concrete commands, but includes some padding such as the marketing-style intro ('understand the deeper meaning and impact of text data') and 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.

3 / 5

Actionability

Copy-paste ready commands cover the common cases end-to-end — install, login, connection ensure, polling, action list/run, and proxy — plus a concrete flags table for the proxy path.

5 / 5

Workflow Clarity

The connection state machine has explicit checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED by re-polling), but the overall install-to-run sequence is implied rather than a clearly numbered list and 'Step 2' is referenced without a matching header.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized into clear sections, but at ~140 lines with all content inline (including the proxy flags table and clientAction state detail) some material could be split into a reference.

4 / 5

Total

16

/

20

Passed

Description

57%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 successfully includes a 'Use when' trigger and a clear brand niche, but its capability verbs are generic rather than concrete. Tightening the action list to specific Tisane functions would lift specificity and trigger coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Tisane actions such as 'analyze text for opinions, emotions, and rhetorical devices'.

Add natural trigger synonyms users might say, e.g. 'text analytics', 'sentiment analysis', or 'opinion mining'.

Make the 'when' clause more specific than 'interact with Tisane Labs data' by naming the actual use cases.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Tisane Labs domain but the actions are minimal and generic ("manage", "automate") rather than concrete verbs like extract or analyze.

2 / 5

Completeness

Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Tisane Labs data") are explicitly present, though the "when" clause is somewhat generic.

4 / 5

Trigger Term Quality

"Tisane Labs" and "data, records" provide the natural brand trigger a user would say, but common synonyms or concrete variations (e.g. "text analytics", "sentiment") are missing.

3 / 5

Distinctiveness Conflict Risk

The distinctive "Tisane Labs" brand anchor gives a clear niche with minimal conflict risk, though the generic "manage data, records, automate workflows" phrasing introduces minor overlap with other data skills.

4 / 5

Total

13

/

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.