consuming-bc-standard-api

Consumes Microsoft standard Business Central APIs (v2.0) for customers, vendors, items, salesOrders, and other built-in entities. No AL coding required. Use when integrating external systems with BC data, building Power Automate flows, or querying BC from Postman/scripts.

Quality

85%

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

Quality

Content

82%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 HTTP examples, clear URL/placeholder structure, and sensible progressive disclosure via a real reference file. It is slightly verbose in the notes/concept sections and could strengthen its destructive-operation feedback loops.

Suggestions

Add an explicit validate→fix→retry loop for batch/POST/PATCH operations (e.g., re-GET after PATCH to confirm the change, or retry with backoff after 429) rather than relying on the troubleshooting table alone.

Tighten the 'Key Concept' and 'Important Notes' sections to one or two lines each, since the procedure and tables already convey these points.

Move the per-entity inline CRUD examples for customers into references/http-examples.md and keep only one representative GET/POST/PATCH/DELETE pattern in the body to reduce repetition.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — tables and code blocks carry the weight with no padding about what Business Central is — though sections like 'Important Notes' and 'Key Concept' restate points already implied by the procedure, which could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste-ready HTTP examples for every CRUD operation with full URL patterns, headers, JSON bodies, If-Match ETag handling, and concrete OData query syntax covering the common cases.	5 / 5
Workflow Clarity	A numbered Procedure (authenticate → URL structure → operations → query → pagination) plus an explicit 'Validation Gates' section gives a clear sequence with checkpoints, but destructive/batch operations lack a full validate→fix→retry feedback loop per step.	4 / 5
Progressive Disclosure	Body serves as an overview with a clearly signaled one-level-deep reference (references/http-examples.md, verified to exist) for bulk examples, and is organized into well-labeled sections; minor gaps as some inline operation examples could also live in the reference file.	4 / 5
	Total	17 / 20 Passed

Description

87%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 clearly and concisely states what the skill does and when to use it, with concrete trigger phrases and a sharp boundary against the custom-API sibling skill. Minor room to expand action verbs beyond 'Consumes'.

Dimension	Reasoning	Score
Specificity	Names the domain (BC standard APIs v2.0) and several concrete entities (customers, vendors, items, salesOrders) with a clear action (Consumes APIs), though it lists entity types rather than distinct operations, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (Consumes standard BC APIs for named built-in entities, no AL coding) and 'when' ('Use when integrating external systems... building Power Automate flows... querying BC from Postman/scripts') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('integrating external systems with BC data', 'building Power Automate flows', 'querying BC from Postman/scripts'), though it is missing common synonyms and BC shorthand variations.	4 / 5
Distinctiveness Conflict Risk	Clear niche — Microsoft-maintained standard APIs on built-in entities — with an explicit boundary ('No AL coding required', use al-custom-api for custom logic), minimizing conflict with related AL skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: emgreppi/Business-Central-AI-Skill
Path: consuming-bc-standard-api/SKILL.md
Commit: 52f8705

Reviewed: 1 day 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.