CtrlK
BlogDocsLog inGet started
Tessl Logo

basiq

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

62

Quality

74%

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

Quality

Content

82%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 strong, executable guide with copy-paste commands and a largely clear connection workflow, weakened only by minor verbosity and a couple of broken step cross-references. It is high-quality and near-exemplary.

Suggestions

Fix the dangling cross-reference: either label the section referenced by "skip to Step 2" or replace it with a concrete section name.

Trim editorial padding such as "so you can focus on the integration logic rather than auth plumbing" to keep every token load-bearing.

Consider moving the proxy flags table and popular-actions catalog into a references file to deepen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable commands with light context, but contains minor editorial padding (e.g. "so you can focus on the integration logic rather than auth plumbing") and loosely relevant asides that could be trimmed without loss.

4 / 5

Actionability

Copy-paste-ready commands cover the common cases end to end — install, login, connection ensure/wait, action list/run with JSON input, and a full proxy flags table — meeting the fully-executable anchor.

5 / 5

Workflow Clarity

The connection flow is sequenced with state interpretation and a re-poll feedback loop, but it references an unlabeled "Step 2" and a "1b" without a "1a", leaving minor navigation gaps that keep it below the explicit-checklist level.

4 / 5

Progressive Disclosure

As a single self-contained file with no bundle references, it is well-organized into clear sections (Overview, Authentication, Connecting, Popular actions, Best practices); minor inlining of reference-style material like the flags table keeps it just below the ideal split-content level.

4 / 5

Total

17

/

20

Passed

Description

66%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 cleanly answers what and when in third person, anchored to a distinctive named platform, but its capability verbs are generic and its trigger vocabulary is thin relative to the skill's actual scope. It is solid above-average, not exemplary.

Suggestions

Replace generic verbs with concrete Basiq capabilities, e.g. "Connect to bank accounts, fetch transactions and account data, and initiate payments."

Broaden trigger terms to include natural user phrases like "bank accounts", "transactions", "financial data", or "open finance".

Tighten the Use-when clause with concrete trigger phrases mirroring the body's actual use cases.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Basiq domain plus 1-2 generic actions, but the actions are abstract and not comprehensive, matching the anchor that names a domain with 1-2 concrete actions.

3 / 5

Completeness

Both a "what" ("Basiq integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Basiq data.") are present, but the when clause is generic and could be more specific, so it sits below the concrete-multi-trigger level.

4 / 5

Trigger Term Quality

The natural terms are essentially limited to "Basiq" and "Basiq data"; common user variations the body later reveals (bank accounts, transactions, financial data) are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

"Basiq" is a specific named open-finance platform with distinct triggers, giving it a clear niche and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

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.