CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

actian

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

Quality

73%

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/actian/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 lean, command-driven guide with a genuinely thorough connection state machine (polling, client-action handling, error states) that most skills lack. Its weaknesses are small coherence gaps — a dangling 'Step 2' reference, a content-free overview section, and placeholders never instantiated by a worked example.

Suggestions

Fix the dangling reference: 'skip to **Step 2**' points to no labeled section — either label 'Searching for actions' as Step 2 or rewrite as 'skip to Searching for actions'.

Add one worked end-to-end example with real values (a concrete action id, intent, and --input payload) instead of only CONNECTION_ID/QUERY placeholders.

Cut or flesh out the '## Actian Overview' bullet list and the filler line 'Use action names and parameters as needed', which add tokens without guidance.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands and stays lean, with only minor trimmable padding: the bare four-bullet '## Actian Overview' list that explains nothing, the filler line 'Use action names and parameters as needed', and a generic opening sentence about who uses Actian. This is efficient with minor over-explanation rather than noticeably verbose.

4 / 5

Actionability

Concrete, executable commands appear throughout — 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.actian.com/" --json', 'membrane action run <actionId> --input {...} --json' — plus a proxy options table. The gaps that keep it from fully copy-paste-ready are unfilled placeholders (CONNECTION_ID, QUERY, <actionId>) and no worked example with real values.

4 / 5

Workflow Clarity

The sequence (install → login → connection ensure → poll state → search actions → run → proxy fallback) is clear with explicit state checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop after user actions. Minor gaps hold it below the top anchor: the instruction 'skip to **Step 2**' references a section that is never labeled Step 2, and there is no validation guidance for action results.

4 / 5

Progressive Disclosure

No bundle files exist and the single-file body is modest in length with clear section headers (Install the CLI, Authentication, Connecting to Actian, Searching for actions, Running actions, Proxy requests, Best practices). Structure is good with minor organization gaps — the odd content-free Overview section and inline proxy flag table — so it does not reach the well-split, cleanly navigable top anchor.

4 / 5

Total

16

/

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 a clear, explicit trigger clause and is safely distinctive thanks to the Actian brand name, but it is let down by vague capability language. 'Manage data, records, and automate workflows' could describe almost any data tool and gives no concrete sense of what the skill actually does.

Suggestions

Replace the generic verbs with 2-3 concrete Actian capabilities, e.g. 'Run integration jobs, manage data sources and datasets, and query Actian records'.

Expand the trigger clause with natural user phrasings and synonyms, e.g. 'Use when the user mentions Actian, integration jobs, or wants to connect to their Actian data'.

Avoid abstract phrases like 'automate workflows' unless a specific workflow capability is named.

DimensionReasoningScore

Specificity

The description names the domain ('Actian integration') but the actions — 'Manage data, records, and automate workflows' — are entirely generic with no concrete Actian capabilities (e.g., running integration jobs or querying datasets). This matches the anchor for naming the domain with minimal or generic actions, and not the level above since no concrete, specific action is stated.

2 / 5

Completeness

It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Actian data'). The 'when' is present but generic and the 'what' is vague, matching the anchor where both exist but could be more explicit rather than the top anchor with concrete trigger phrases.

4 / 5

Trigger Term Quality

'Actian' is the natural term and appears in both the capability and trigger clauses, with related terms 'data', 'records', and 'workflows', but no synonyms or variations of what users might say. Some relevant keywords are present while common variations are missing, so it does not reach good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The description is keyed on 'Actian', a distinct niche platform, and the 'Use when' clause explicitly gates on interacting with Actian data. This gives clear niche triggers with minimal conflict risk against other skills; the generic verbs are subordinated to the Actian brand trigger.

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