copilot-al-configs
AL and Business Central development skills and MCP tools for Codex, GitHub Copilot CLI, and VS Code Insiders.
Version 0.3.0 contains 29 focused skills and four MCP connection definitions. The 11 original AL skills form the common workflows; BC specialties load only when relevant.
Consolidated collection
The upstream AL-Copilot-Skills-Collection at commit f0ef89273477ec7f059bae3a53f62ce05fcdbd34 was reviewed and substantially consolidated. Duplicate debugging/review/testing/context and documentation workflows were merged; broken DOCX, deployment and foreign framework workflows were removed. Active content contains the corrections directly and does not require historical warning notes.
Read the final Czech report and all 50 dispositions for decisions, corrected defects, actual verification and rollout gaps. The initial audit records the previous 0.2.0 snapshot only.
Third-party notices preserve licensing and authorship. The provenance manifest separates pinned upstream blobs, historical imported bytes and maintained files. Run python -m pip install -r scripts/requirements-validation.txt, then python -X utf8 scripts/validate-skills.py. Optionally add --upstream C:/path/to/AL-Copilot-Skills-Collection to verify original Git blobs and license. After intentional skill edits, review the diff and run python scripts/record-skill-integrity.py --write to update only maintained hashes; this does not certify content quality.
Install in Codex
From this repository's root, using a Codex CLI with plugin marketplace and plugin add support:
codex plugin marketplace add .
codex plugin list --marketplace copilot-al-configs --available --json
codex plugin add copilot-al-configs@copilot-al-configs
Start a new Codex session after installation. In the desktop app, restart the app and look for AL Development in the AL Development Plugins marketplace. Verify that the skills and MCP tools are available in the consuming AL project.
Once these files have been pushed to GitHub, the Git-backed installation is:
codex plugin marketplace add hyzaDan/copilot-al-configs --ref main
codex plugin add copilot-al-configs@copilot-al-configs
For a local source, edit this repository, then reinstall or refresh the plugin using the consuming host's supported flow; restart the desktop app and start a new session. For a Git-backed source, first run codex plugin marketplace upgrade copilot-al-configs to fetch the updated Git snapshot, then refresh the installed plugin. Codex loads an installed cache copy; editing the source does not update an already running session.
The repo marketplace makes the plugin discoverable. Installation and enablement are host settings; this repository does not automatically enable it in every project.
Install in GitHub Copilot
VS Code discovers the root plugin.json as Agent Plugins 1.0 and loads custom agents from com.github.copilot/agents/. Copilot manifests remain in .github/plugin/, with matching .claude-plugin/ manifests for legacy discovery; their agent paths point to the same definitions.
For a local checkout in a supporting VS Code version, enable agent plugins and register the actual repository path in the experimental chat.pluginLocations user setting. See current VS Code plugin guidance.
"chat.pluginLocations": {
"C:/path/to/copilot-al-configs": true
}
Reload the VS Code window after changing the plugin layout. The plugin details should list 29 skills, four MCP servers, and eight agents. Six agents are available in the picker; al-developer and al-symbol-researcher are delegation-only. No separate chat.agentFilesLocations entry is needed for this plugin.
For GitHub Copilot CLI:
- Direct plugin install:
copilot plugin install hyzaDan/copilot-al-configs - Marketplace add:
copilot plugin marketplace add hyzaDan/copilot-al-configs - Git URL:
https://github.com/hyzaDan/copilot-al-configs
Package layout
| Path | Purpose |
|---|---|
plugin.json | Portable Agent Plugins 1.0 manifest and OpenAI presentation metadata |
mcp.json | Portable MCP configuration, with explicit transport types |
skills/ | Shared skills and their supporting references |
.codex-plugin/plugin.json | Codex compatibility manifest for clients using the older layout |
.agents/plugins/marketplace.json | Codex marketplace pointing to the plugin at the repository root |
.mcp.json | Legacy MCP configuration for Copilot and the Codex compatibility layout |
.github/plugin/, .claude-plugin/ | Copilot and legacy plugin/marketplace manifests |
com.github.copilot/agents/ | Optional Copilot custom agents, discovered by Agent Plugins 1.0 |
Portable clients discover skills/ and mcp.json automatically. Copilot discovers its custom agents in the com.github.copilot namespace; the root Agent Plugins manifest takes precedence over legacy manifests, so a root agents/ folder alone is not sufficient. Keep plugin identity/version synchronized across manifests, and keep the MCP server names, commands, arguments, and endpoints equivalent in mcp.json and .mcp.json; portable HTTP transport is streamable-http, while the legacy file uses http.
See the official OpenAI plugin packaging guide for the portable format, compatibility manifests, and marketplace behavior.
MCP servers and prerequisites
| Server | Connection | Prerequisites |
|---|---|---|
alcops | Local stdio: alcops-mcp | .NET 10, ALCops.Mcp on PATH, and BC Development Tools v18+; NuGet access for initial analyzer provisioning |
al-symbols-mcp | Local stdio: npx -y al-mcp-server | Node.js/npm with npx on PATH, initial npm registry access, and the consuming project's AL symbols |
context7 | Streamable HTTP: https://mcp.context7.com/mcp | Network access; service access/rate limits apply |
microsoft.docs.mcp | Streamable HTTP: https://learn.microsoft.com/api/mcp | Network access |
These are connections to existing servers. The plugin does not host or deploy a new MCP service. Keep the consuming AL project's context explicit when querying symbols; installing the plugin alone does not provide its .app dependencies.
ALCops project discovery
Install the global tools once if they are not already available:
dotnet tool install --global Microsoft.Dynamics.BusinessCentral.Development.Tools
dotnet tool install --global ALCops.Mcp
Ensure alcops-mcp is on the MCP host's PATH (global .NET tools normally live under the user's .dotnet/tools directory). The plugin invokes the command by name, so it works across user accounts and operating systems without embedding a Windows executable path.
The bundled configuration omits --projects and cwd. ALCops discovers app.json files below the working directory supplied by the consuming MCP host. Start it in the intended AL workspace, not the plugin cache directory. If the host uses another directory or the projects are elsewhere, configure --projects in that workspace's MCP settings and restart the server so it resolves project, analyzer, and ruleset settings at startup. Project paths belong to the consuming workspace rather than the shared plugin.
al_addproject can register a project with the Microsoft AL tool proxy after startup, but it does not refresh ALCops' startup analyzer and ruleset configuration. Use the workspace configuration and restart approach when the full analyzer behavior is required.
ALCops exposes analyzer/rule tools and code fixes, plus Microsoft's al_* tools through its almcp proxy. Code-fix tools can edit source files; build, publishing, and test prerequisites still apply. See the ALCops installation and CLI documentation.
Build validation requires an available AL compiler/build tool. Runtime tests require the project's configured runner and an identified BC test environment. AL Language and NAB editor tools are separate host capabilities, not servers bundled by this plugin.
Czech translation
al-translation-phase preserves the English-to-Czech workflow and its required isolated al-translator worker. That worker is currently defined as a Copilot custom agent with a provider-specific model and NAB tool allowlist. The Codex package declares skills and MCP connections; it does not register the Copilot agents or their model settings.
To execute translation in Codex, the consuming environment must provide an equivalent worker and the required translation tools. Until that integration exists, the skill reports the missing prerequisite. Its XML-editing fallback still runs within the required worker. It must not silently translate in the parent context. See model routing.
Daily use
Use the host's built-in planning and execution modes. AL skills load on demand; no custom orchestrator or full project bootstrap is required for every edit. Verify discovery in the consuming host's plugin/skill diagnostics.
Skills and optional agents
- Design and implementation: architecture and coding standards.
- Diagnosis and validation: debugging (with snapshot/profile reference), build validation, and AL testing.
- Review: solution review, with performance/security skills only when relevant.
- Tool workflows: symbol lookup and XLF translation.
- Onboarding: project context bootstrap, not an always-on prerequisite.
In Copilot, custom agents are useful for isolated review, runtime artifact analysis, translation, or bounded symbol research. Existing develop/fix/test orchestrator names remain as manual compatibility entrypoints and disable automatic model invocation. The developer and symbol-research workers are hidden from the picker and remain available for delegation in that host.
The symbol worker uses its configured provider-specific model identifier. This is not a portable guarantee of model availability or lower cost. See model routing for configuration, forked skills, and verification steps.
See taxonomy for ownership and the skill-first audit for the earlier Copilot migration. Historical migration documents are not runtime workflow dependencies.
Verify in a consuming project
- Confirm AL Development is enabled and the 29 skill names are discoverable in a new session.
- Confirm the four MCP servers initialize and list tools. Make a small documentation query and a bounded symbol query for the intended AL project; confirm ALCops has loaded that project before using its AL tools.
- Exercise build/test skills only with the actual compiler, runner, and authorized BC environment available.
- Exercise translation only after the isolated worker and translation tools have been integrated.
Configuration validation and MCP discovery are separate from AL compilation, executed BC tests, and translation. This repository has no BC app or runtime test fixture.