Name: microsoft-dynamics-365-business-central
Rating: 55.2 (1 reviews)
Author: membranedev

microsoft-dynamics-365-business-central

Microsoft Dynamics 365 Business Central integration. Manage Companies. Use when the user wants to interact with Microsoft Dynamics 365 Business Central data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/microsoft-dynamics-365-business-central/SKILL.md

Quality

Content

67%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 concrete Membrane CLI commands, a useful actions table, and a clear connection-state workflow with feedback loops. Its main weakness is a padded introductory paragraph that explains Business Central itself, plus slightly loose workflow labeling and inlined reference material that could be split out.

Suggestions

Cut or condense the opening paragraph explaining what Business Central is; Claude already knows the product, so lead with the integration's purpose instead.

Fix the loose 'Step 2' reference by adding a matching '### Step 2: Search for actions' header, and add a validation/check step after running create actions before considering the task done.

Move the large 'Popular actions' table and proxy flag reference into a separate reference file (e.g. ACTIONS.md) and link to it, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient lean commands and tables, but the opening paragraph ('comprehensive business management solution for small and medium-sized businesses... streamline processes across finance, operations, sales, and customer service') explains what Business Central is — a concept Claude already knows — which is unnecessary padding. This fits the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action run, request) with flags and JSON examples, and an actions table covering common cases. Minor placeholders like CONNECTION_ID and the empty-string argument keep it just below fully self-contained 5.	4 / 5
Workflow Clarity	There is a clear install → login → connection ensure → poll-for-ready → search actions → run sequence with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop. It stays at 4 rather than 5 because 'Step 2' is referenced without a matching header and there is no validation step after running an action or before destructive create operations.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested or buried references, and the official-docs link is a clean one-level pointer. It is not a 5 because the large actions table and proxy-flag reference are all inlined rather than split into a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 identifies the product and includes an explicit 'Use when' trigger, but it undersells the skill's capabilities with only a single generic action ('Manage Companies') and lacks common synonyms like 'BC' or 'ERP'. It is distinct but thinner than ideal.

Suggestions

Replace the minimal 'Manage Companies.' with the concrete actions the skill actually exposes, e.g. 'List and create customers, sales orders, invoices, vendors, and accounts.'

Add natural trigger synonyms users say, such as 'Dynamics 365', 'BC', or 'ERP', alongside the full product name.

Sharpen the 'when' clause to name the triggering tasks (e.g. 'Use when the user wants to query or create Business Central records like customers, orders, or invoices').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Microsoft Dynamics 365 Business Central integration') but the only action stated is 'Manage Companies', which is minimal and generic; the body reveals many more actions (List/Get/Create for accounts, orders, invoices, etc.) that are not reflected here. It fits the 'names the domain but actions are minimal or generic' anchor better than the 3 anchor's '1-2 concrete actions'.	2 / 5
Completeness	It states both a 'what' ('integration. Manage Companies.') and an explicit 'when' ('Use when the user wants to interact with Microsoft Dynamics 365 Business Central data'), but the 'what' is thin and the 'when' could be more specific about which tasks trigger it, fitting the 'has both what and when; when could be more explicit' anchor rather than the fully concrete 5 anchor.	4 / 5
Trigger Term Quality	The full product name 'Microsoft Dynamics 365 Business Central' is a natural term a user would say, but common variations and synonyms (BC, Dynamics 365, ERP) are missing, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Microsoft Dynamics 365 Business Central' gives it a clear niche with minimal conflict risk, but the trigger 'interact with ... data' is somewhat broad, keeping it just below the 'clear niche with distinct triggers' 5 anchor.	4 / 5
	Total	13 / 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/microsoft-dynamics-365-business-central/SKILL.md
Commit: f484c82

Reviewed: 6 days 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.