CtrlK
BlogDocsLog inGet started
Tessl Logo

exact-online

Exact Online integration. Manage Organizations. Use when the user wants to interact with Exact Online data.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/exact-online/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 copy-paste CLI commands and a well-validated connection workflow, and it is reasonably concise. Its main weakness is progressive disclosure: everything lives in one file with no references, including a large actions table that could be split out.

Suggestions

Move the 20-row 'Popular actions' table and the detailed connection-state/clientAction reference into a separate file (e.g. ACTIONS.md) and link to it from SKILL.md, keeping SKILL.md as an overview.

Fix step labeling so referenced steps exist as headings (label a 'Step 2' heading, add a '1a' counterpart to '1b') or renumber the connection workflow consistently.

Add an explicit verification step after write actions (e.g., re-fetch the created resource or check the response status) given create/update operations are involved.

DimensionReasoningScore

Conciseness

The body is mostly lean, command- and table-driven, with only minor over-explanation such as the opening paragraph defining Exact Online and editorializing like 'so you can focus on the integration logic rather than auth plumbing'. It is efficient with trimmable padding rather than verbose, so it sits at 4 rather than 3 or 5.

4 / 5

Actionability

It provides copy-paste-ready commands for every common case (install, login, connection ensure, --wait polling, action list/run with --input, proxy request) with clearly marked placeholders, plus a concrete actions table. Examples fully cover the common cases, matching the anchor 5 example.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→poll→search→run sequence with explicit state-check validation and a CLIENT_ACTION_REQUIRED feedback loop, but step labels are inconsistent ('skip to Step 2' with no labeled Step 2, '1b' with no '1a') and write actions lack an explicit verify step, keeping it below 5.

4 / 5

Progressive Disclosure

The 177-line SKILL.md is the entire manual inlined with no external file references, and the 20-row popular-actions table plus detailed connection-state docs are bulk reference content that belongs in separate files. Structure is good, but content that should be split out is inline, matching anchor 3 rather than 4.

3 / 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 cleanly names the niche and includes an explicit 'Use when' trigger, but its capability list is thin and generic ('Manage Organizations') rather than reflecting the concrete actions the skill actually exposes. Trigger-term coverage is limited to the product name without natural synonyms.

Suggestions

Replace 'Manage Organizations' with the concrete actions the skill exposes, e.g. 'List and create accounts, contacts, items, sales invoices, and journal entries in Exact Online'.

Broaden trigger terms to include natural user phrasings like 'Exact Online accounting', 'create an invoice in Exact Online', or 'Exact Online ERP data'.

Tighten the 'when' clause to name specific tasks (invoicing, account management, journal entries) rather than the generic 'interact with Exact Online data'.

DimensionReasoningScore

Specificity

Names the Exact Online domain plus a single generic action ('Manage Organizations'), which is minimal and does not match the body's actual actions (Accounts, Contacts, Items, Invoices). It falls at anchor 2 rather than 3 because only one vague action is given rather than 1-2 concrete ones.

2 / 5

Completeness

Both 'what' ('Exact Online integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Exact Online data.') are present; the 'Use when' clause avoids the 3-cap, but the 'what' is generic so it stops short of 5.

4 / 5

Trigger Term Quality

'Exact Online' is a natural product-name trigger and 'Use when the user wants to interact with Exact Online data' gives a usable phrase, but common variations users might say (accounting, invoicing, ERP, bookkeeping) are missing.

3 / 5

Distinctiveness Conflict Risk

Exact Online is a specific named SaaS product with distinct triggers, so it occupies a clear niche with minimal overlap risk against other skills.

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.

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.