creating-bc-custom-api

Creates custom API pages (CRUD) and API queries (read-only joins) in AL for Business Central. Use when exposing custom tables, adding business logic to APIs, creating reporting endpoints, or joining multiple tables for external consumption.

Quality

88%

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

88%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.

A high-quality, actionable reference skill with executable templates, well-mapped validation gates, and properly signaled bundle references. The main improvement is reducing redundancy between inline templates, the Required Properties table, and the Best Practices section.

Suggestions

Slim the inline Step 2-4 code blocks to minimal getting-started forms and defer the full versions to the reference files, removing overlap with the 'complete' templates in references/.

Consolidate the 'Required Properties' table and 'Best Practices' list, which currently restate the same property guidance (e.g., ODataKeyFields = SystemId, DelayedInsert = true) twice.

Dimension	Reasoning	Score
Conciseness	The body is dense, technical, and assumes Claude's competence (no padding about what CRUD or tables are), but 'Required Properties', 'Best Practices', and inline code comments overlap somewhat, leaving minor trimmable redundancy short of the fully-lean anchor 5.	4 / 5
Actionability	Provides copy-paste-ready, complete AL templates for API Page (CRUD), Subpage/navigation, API Query joins, and Read-Only pages, with placeholders documented in a dedicated table — fully executable and covering the common cases.	5 / 5
Workflow Clarity	A four-step Procedure is paired with explicit Validation Gates mapped to steps ('After Step 2: GET returns 200', 'Final: all CRUD operations work') plus a troubleshooting feedback loop ('Fix issue → Recompile → Test GET first → Then test POST/PATCH/DELETE'), satisfying validation for the destructive CRUD operations.	5 / 5
Progressive Disclosure	Clear section structure with two real, one-level-deep, clearly-signaled reference files (api-page-template.al, api-query-template.al) verified present, but the inline Step 2-4 templates are already fairly complete, creating minor redundancy with the 'complete' reference templates.	4 / 5
	Total	18 / 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.

A strong, well-scoped description that clearly states both capability and trigger conditions with natural phrasing. Minor room to broaden the enumerated actions and add a few common synonyms (OData, .al) for fuller trigger coverage.

Suggestions

Expand the 'what' clause beyond the two core actions (e.g., mention defining entity sets, OData key fields, navigation properties) to push specificity toward a comprehensive list.

Add widely-used synonyms such as 'OData', '.al files', or 'Business Central API endpoint' to the trigger clause for broader natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the AL/Business Central domain and two concrete actions with operation detail — 'Creates custom API pages (CRUD) and API queries (read-only joins)' — but lists only two core actions rather than a broad, comprehensive set, so it sits at anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Creates custom API pages (CRUD) and API queries (read-only joins) in AL for Business Central') and 'when' ('Use when exposing custom tables, adding business logic to APIs, creating reporting endpoints, or joining multiple tables for external consumption') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases a BC user would say ('exposing custom tables', 'adding business logic to APIs', 'creating reporting endpoints', 'joining multiple tables') with synonyms, but misses common variants like 'OData', '.al', or 'API endpoint', placing it just below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (custom BC APIs in AL) and the skill body even disambiguates from the standard-API skill, giving minimal conflict risk.	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: creating-bc-custom-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.