CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blackthorn

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

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

Quality

Content

61%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 solid, executable guide to driving Blackthorn through the Membrane CLI, with concrete commands and good state-handling for connection readiness. Its weaknesses are broken workflow references ('Step 2' that doesn't exist, an orphan '1b'), duplicated discovery instructions, and some filler that could be trimmed.

Suggestions

Fix the workflow numbering: either label the sections 'Step 1'/'Step 2' (and add the missing 1a) or drop the 'skip to Step 2' phrasing entirely

Merge the 'Searching for actions' and 'Popular actions' sections, which both document 'action list --intent' with slightly different command forms

Delete filler lines like 'Use action names and parameters as needed.' and show a concrete '--tenant' value in the login example

DimensionReasoningScore

Conciseness

Mostly efficient command documentation, but it includes filler ('Use action names and parameters as needed.'), a redundant duplicate of the 'action list --intent' instructions under both 'Searching for actions' and 'Popular actions', and padded best-practice prose, matching the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

Concrete copy-paste commands throughout (install, login, 'membrane connection ensure "https://www.blackthorn.io/" --json', action run with JSON input, proxy with a flag table). Minor gaps keep it below 5: the '--tenant' value is never demonstrated and placeholders like <actionId> and QUERY are left abstract.

4 / 5

Workflow Clarity

A real sequence exists (install → login → ensure connection → poll state → act → proxy fallback) with state handling, but 'skip to **Step 2**' references a step that is never labeled, '#### 1b.' dangles without a 1a, and there are no validation checkpoints before running actions against payment/record data — sequence present with implicit checkpoints.

3 / 5

Progressive Disclosure

A single-file skill with no bundle files, well-sectioned (install, auth, connect, actions, proxy, best practices) and content appropriately placed inline for this length. Minor gaps — the bare object-model list under Overview has no accompanying guidance — keep it at 4.

4 / 5

Total

14

/

20

Passed

Description

61%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 has an explicit 'Use when...' trigger and a distinctive niche name, but the capability statement is generic CRUD-speak that undersells the concrete domain (events, payments, registrations) and omits natural trigger synonyms. It reads as a template-generated description rather than one written for this integration.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete capabilities, e.g. 'Manage Blackthorn events, registrations, payments, transactions, and refunds in Salesforce'

Add natural trigger terms users would actually say: events, registrations, payments, refunds, Salesforce

Mention the Salesforce-native context in the description so users asking about 'our payment platform in Salesforce' match the trigger

DimensionReasoningScore

Specificity

The description names the domain (Blackthorn) but its actions are generic — 'Manage data, records, and automate workflows' lists no concrete capabilities such as events, payments, registrations, or refunds, matching the anchor for minimal or generic actions rather than the 1-2 concrete actions of level 3.

2 / 5

Completeness

Both parts are present: a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Blackthorn data'). It is not a 5 because the 'what' is vague and the 'when' could name concrete trigger phrases.

4 / 5

Trigger Term Quality

'Blackthorn', 'data', and 'records' are relevant keywords, but common variations users would naturally say — events, payments, Salesforce, registrations — are missing, matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

'Blackthorn' is a clear niche platform name and the trigger ('interact with Blackthorn data') is distinct, so the risk of firing for the wrong skill is minimal.

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

Validation — 15 / 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

Path

skills/blackthorn/SKILL.md

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.