Name: sage-300
Rating: 62.4 (1 reviews)
Author: membranedev

sage-300

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sage-300/SKILL.md

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 executable CLI commands and a sound connection workflow including state-based validation. It loses points mainly on a padded intro and a large inline entity list that could be trimmed or moved to a reference.

Suggestions

Remove or condense the opening paragraph explaining what Sage 300 / an ERP is, since Claude already knows this.

Move the 55-item entity list into a references file (e.g. ENTITIES.md) and keep only a short summary inline, improving token efficiency and progressive disclosure.

Renumber the connection steps consistently (1, 1b, 2 -> 1, 2, 3) so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening ERP explainer ('Sage 300 is an enterprise resource planning (ERP) software designed for small to medium-sized businesses...') states what Claude already knows and the ~55-item entity list pads the token budget.	3 / 5
Actionability	Provides copy-paste ready, executable commands throughout (install, login, connection ensure/get, action list, action run, request) plus a complete flags table, covering the common cases.	5 / 5
Workflow Clarity	The connect-then-search-then-run sequence is clear with validation via state polling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step labels are inconsistent ('Step 2', '1b') and a couple of checkpoints are implicit.	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections with no nested references, and no bundle files are present; the long inline entity list is the main organization gap that keeps it from a 5.	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 is well-targeted to a distinct product and includes both a what and a when clause, but its action wording is generic and the trigger guidance lacks concrete synonyms. It is solid but could be sharpened.

Suggestions

Replace generic verbs with concrete Sage 300 actions (e.g., 'create and post invoices, sync vendors and customers, pull GL reports').

Expand the 'Use when' clause with natural trigger phrases users actually say (e.g., 'Sage 300', 'AP/AR', 'general ledger', 'Sage 300 invoices').

Dimension	Reasoning	Score
Specificity	Names the Sage 300 domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor for domain plus 1-2 non-comprehensive actions.	3 / 5
Completeness	Provides both a 'what' (integration, manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Sage 300 data'), but the trigger clause is somewhat generic rather than comprehensive.	4 / 5
Trigger Term Quality	Includes the natural product term 'Sage 300' plus 'data' and 'records' that users would say, giving good keyword coverage though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named product (Sage 300) with distinct triggers, giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/sage-300/SKILL.md
Commit: f484c82

Reviewed: ~19 hours ago

Table of Contents

Discovery Implementation Validation

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.