CtrlK
BlogDocsLog inGet started
Tessl Logo

sage-intacct

Sage Intacct integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sage Intacct 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/sage-intacct/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 an efficient, actionable CLI guide with a strong connection-state workflow including error-recovery feedback loops, weakened only by a redundant/empty 'Popular actions' section and broken step cross-references.

Suggestions

Make 'Popular actions' deliver on its title by listing 3-5 concrete Sage Intacct actions with example `action run` invocations and sample `--input` payloads, or rename it.

Fix step cross-references: label the 'Searching for actions' section as 'Step 2' (or remove the 'Step 2' / '1b' references) so navigation resolves.

Trim the introductory 'what is Sage Intacct' paragraph and the duplicated action-list command to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly lean command-focused content with every token roughly earning its place, but the marketing-style intro ('cloud-based accounting software platform...') and a duplicated action-list command in 'Popular actions' could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready CLI commands across install, auth, connection, search, run, and proxy with a flag table, but 'Popular actions' promises actions yet only repeats the discovery command and shows no concrete action id or input example.

4 / 5

Workflow Clarity

The connection workflow has an explicit state machine with validation and feedback loops (BUILDING poll, CLIENT_ACTION_REQUIRED act-then-poll, error handling), but cross-references like 'skip to Step 2' and a '1b' with no '1a' do not resolve to labeled sections.

4 / 5

Progressive Disclosure

A single cohesive CLI guide is well-organized into clear, navigable sections with no nested references, but the misplaced 'Popular actions' section and ~146-line length leave minor organization gaps.

4 / 5

Total

16

/

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 correctly pairs a what-statement with an explicit 'Use when' trigger and names a distinct product niche, but its action list and trigger keywords stay generic instead of naming concrete Sage Intacct entities users would mention.

Suggestions

Replace generic verbs with concrete Sage Intacct operations, e.g. 'Create and query bills, invoices, payments, journal entries, and general-ledger accounts.'

Expand the trigger clause with natural entity terms users say, e.g. 'Use when the user wants to manage Sage Intacct accounting data — invoices, bills, payments, or the general ledger.'

Keep third-person voice (already correct) but add file/format or entity synonyms to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Sage Intacct integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations like creating invoices or querying GL accounts.

3 / 5

Completeness

States both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Sage Intacct data'), though the trigger is generic rather than listing concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes the natural product name 'Sage Intacct' in the trigger clause, but coverage is thin and misses common accounting terms users would say (invoices, bills, payments, GL, accounting).

3 / 5

Distinctiveness Conflict Risk

Targets a specific named accounting platform ('Sage Intacct') with distinct triggers, giving it a clear niche and minimal conflict risk with other 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.