al-research

Verifies AL and Business Central facts against authoritative sources with verbatim quotes and citations.

4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace --skill al-research-fbakkensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: al-research
Source: https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace/tree/main/plugins/al-agentic-dev/skills/al-research
Command: npx skills add https://github.com/FBakkensen/bc-agentic-dev-tools-marketplace --skill al-research-fbakkensen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AL and Business Central knowledge drifts fast — renamed events, removed procedures, and changed signatures make recalled facts unreliable. This Skill arbitrates conflicting sources and verifies BC-specific claims against authoritative references before they land in durable design artifacts. ## Core Features & Use Cases - Cross-family verification: Confirms every claim against at least two source families (Microsoft Learn, bc-code-intelligence MCP, AL symbols, workspace grep) before returning a finding. - Verbatim quoting with citations: Returns exact symbols, signatures, and attribute values with one-line citations instead of paraphrased claims. - Conflict surfacing: When authoritative sources disagree, it presents both quotes and names the conflict rather than silently picking one. - Use Case: While writing an event-model.md, you need to confirm whether a specific subscriber signature exists in the current BC release. Invoke this Skill to fetch the exact signature from workspace symbols and Microsoft Learn, and receive a cited findings note. ## Quick Start Ask the assistant to verify whether a specific AL procedure signature exists in the current Business Central release and quote the authoritative source.

Frequently Asked Questions about al-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify AL signatures against the current Business Central release?

Query the workspace's compiled symbols via al-symbols-mcp or the LSP for the actual signature, then cross-check against Microsoft Learn. The skill returns verbatim signatures with one-line citations from both source families.

What sources are authoritative for Business Central development facts?

Microsoft Learn covers platform constructs and AppSourceCop rules, AL symbols reflect the compiled dependency graph, and bc-standard-reference mirrors shipped BaseApp code. Agreement across two different source families counts as verification.

When should I use al-research instead of a direct documentation lookup?

Use it when two sources disagree, when a fact lands in a durable design artifact like event-model.md or an ADR, or when a fuzzy question needs framing plus cross-family verification. Single-fact lookups should go direct.

Does al-research work if MCP servers are not installed?

Yes, it degrades gracefully. Missing MCP servers simply have no effect; the skill falls back to Microsoft Learn for platform constructs and bc-standard-reference for shipped code names, and never blocks on an absent server.

What happens when Microsoft Learn and workspace symbols disagree?

The skill surfaces both quotes with citations and explicitly names the conflict instead of silently choosing one. The caller, who holds the architectural context, decides which source to trust.