actian
Actian integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actian data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill actian72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%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 adequately identifies the Actian platform and includes an explicit 'Use when' clause, which is good for completeness. However, the capabilities listed are vague ('manage', 'automate') rather than concrete actions, and the trigger terms lack Actian-specific vocabulary that would help distinguish it from generic data management skills.
Suggestions
Replace vague verbs with specific actions like 'query Actian databases, insert/update records, configure DataConnect pipelines, schedule automated data transfers'
Add Actian-specific trigger terms such as product names (Vector, Zen, DataConnect) or file formats users might mention when working with Actian
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Actian) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions - 'manage' and 'automate' are vague verbs without specifics like 'create tables', 'query records', or 'schedule jobs'. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with Actian data'), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Actian' as a key trigger term and generic terms like 'data', 'records', 'workflows', but lacks specific variations users might say such as database names, file types, or common Actian-specific terminology (e.g., Vector, Zen, DataConnect). | 2 / 3 |
Distinctiveness Conflict Risk | 'Actian' provides some distinctiveness as a specific platform, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other database or workflow automation skills. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for Actian integration via Membrane with good structure. However, it includes some unnecessary introductory content, lacks validation checkpoints in workflows, and the overview section with empty bullet points adds no value. The best practices section is helpful but the skill could be tightened.
Suggestions
Remove the introductory paragraph explaining what Actian is and the vague overview bullet points - Claude already knows this context
Add validation steps after key operations (e.g., verify connection was created successfully, check action output for errors before proceeding)
Include an example of handling errors or failed connections with a retry/fix workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., 'Actian is a database management and analytics platform' - Claude knows this). The overview section with bullet points is vague and adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No explicit verification steps after running actions or connecting - missing feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is in one file. The proxy request options table and best practices could potentially be split out. No references to external detailed documentation within the skill. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.