CtrlK
BlogDocsLog inGet started
Tessl Logo

netsuite

NetSuite integration. Manage accounting and erp data, records, and workflows. Use when the user wants to interact with NetSuite 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/netsuite/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 highly actionable, with copy-paste commands, a flags reference, and a clear state-driven connection workflow with polling checkpoints. Its weaknesses are a redundant introductory explainer of what NetSuite/ERP is and a large inline actions table that could live in a reference file.

Suggestions

Remove or condense the opening paragraph explaining what NetSuite/ERP is; Claude already knows this and it costs tokens for no gain.

Add an explicit validation/verification step for write operations (create/update customer, vendor) so the workflow clears the destructive-operation bar.

Move the large popular-actions table into a references file (e.g. ACTIONS.md) and keep only a few representative examples inline to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean commands, tables, and code blocks, but the opening paragraph ('NetSuite is a cloud-based enterprise resource planning (ERP) software suite. It helps businesses manage...') explains a concept Claude already knows, and a few prose sentences could be tightened. It is not a 4 because the redundant NetSuite/ERP explainer is more than a minor trim, and not a 2 because the bulk is action-oriented rather than extensively padded.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready — install command, login commands, `membrane connection ensure`, `action list`/`action run` with `--json`, a proxy flags table, and a concrete popular-actions table with keys. It is not a 4 because concrete commands cover the common cases comprehensively with no real gaps.

5 / 5

Workflow Clarity

The connection workflow is clearly sequenced with state-based checkpoints and a polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED with re-poll after action). It is not a 5 because the 'skip to Step 2' reference points to no explicitly labeled Step 2 and the create/update record actions lack verification steps, and not a 3 because the main workflow does have explicit checkpoints rather than only implicit ones.

4 / 5

Progressive Disclosure

The body is well-organized with clear section headers and no nested references, and no bundle files exist so all content is appropriately inline. It is not a 5 because at ~165 lines with a large inline popular-actions table it is more than a concise overview pointing to deeper materials, and not a 3 because structure and organization are clearly more than 'some structure'.

4 / 5

Total

16

/

20

Passed

Description

73%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 states what the skill does and when to use it, with an explicit 'Use when' clause and a distinct, brand-anchored niche. Its main weakness is specificity: a single generic verb ('Manage') covers several object nouns instead of naming concrete operations.

Suggestions

Replace the single verb 'Manage' with 2-3 concrete actions (e.g. 'query and create NetSuite records, run accounting workflows, manage ERP data') to lift specificity.

Expand the 'Use when' clause with additional natural trigger phrases (e.g. 'when the user mentions NetSuite, financials, invoices, or sales/purchase orders').

DimensionReasoningScore

Specificity

The description names the domain ('accounting and erp data, records, and workflows') but relies on a single generic verb ('Manage') covering several object nouns rather than listing distinct concrete actions, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor. It is not a 4 because no specific discrete actions (e.g. 'create invoices', 'list customers') are enumerated, and not a 2 because the domain plus several objects exceed purely minimal coverage.

3 / 5

Completeness

It answers 'what' ('Manage accounting and erp data, records, and workflows') and includes an explicit 'Use when the user wants to interact with NetSuite data' trigger clause. It is not a 5 because the 'when' offers only a single narrow trigger phrase rather than multiple concrete triggers, and not a 3 because both what and when are explicitly present.

4 / 5

Trigger Term Quality

Natural terms a user would say are present — 'NetSuite', 'accounting', 'erp data', 'records', 'workflows' — giving good keyword coverage. It is not a 5 because common synonyms and variations (e.g. 'financials', 'ledger', 'purchase orders', file/record extensions) are missing, and not a 3 because the brand name plus multiple domain terms exceed 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

'NetSuite integration' and 'interact with NetSuite data' anchor the skill to a single named product, giving it a clear niche with minimal conflict risk. It is not a 4 because the brand-specific trigger is more distinct than the 'mostly distinct, minor overlap' anchor rather than less.

5 / 5

Total

16

/

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.