al-build
Skill115 starsChanged 14 days agoMITView on GitHub
Build, package, and deploy AL extensions to Business Central environments.
In this repository64 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- claude-plugin/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- instructions/copilot-instructions.mdCopilot instructions
- agent-builderSkill
- al-agent-createSkill
- al-agent-instructionsSkill
- al-agent-taskSkill
- al-agent-testSkill
- al-buildSkill
- al-context-createSkill
- al-initializeSkill
- al-memory-createSkill
- al-pr-prepareSkill
- al-spec-createSkill
- architectSkill
- auditSkill
- conductSkill
- developSkill
- presalesSkill
- reviewSkill
- skill-agent-instructionsSkill
- skill-agent-task-patternsSkill
- skill-agent-toolkitSkill
- skill-al-review-pipelineSkill
- skill-apiSkill
- skill-contribution-assistantSkill
- skill-copilotSkill
- skill-debugSkill
- skill-estimationSkill
- skill-eventsSkill
- skill-migrateSkill
- skill-pagesSkill
- skill-performanceSkill
- skill-permissionsSkill
- skill-testingSkill
- skill-translateSkill
- specSkill
- triageSkill
- al-agent-createSkill
- al-agent-instructionsSkill
- al-agent-taskSkill
- al-agent-testSkill
- al-context-createSkill
- al-initializeSkill
- al-memory-createSkill
- al-pr-prepareSkill
- al-spec-createSkill
- skill-agent-instructionsSkill
- skill-agent-task-patternsSkill
- skill-agent-toolkitSkill
- skill-al-review-pipelineSkill
- skill-apiSkill
- skill-contribution-assistantSkill
- skill-copilotSkill
- skill-debugSkill
- skill-estimationSkill
- skill-eventsSkill
- skill-migrateSkill
- skill-pagesSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 8 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Ask and confirm with the user before proceeding.
- Very specific: line 21
Build: Use al_build to compile the project
- Very specific: line 23
Deploy: Use al_incremental_publish for rapid iteration (requires approval)
- Distinctive: line 24
Verify: Check for any compilation errors
- Very specific: line 27
Build: Use al_build with full validation
- Very specific: line 28
Package: Create .app file with al_package
- Very specific: line 30
Deploy: Use al_publish to deploy with debugging enabled (requires approval)
- Distinctive: line 31
Test: Ensure all unit tests pass
- Very specific: line 34
Build: Use al_build with strict validation
- Very specific: line 35
Package: Create release package with al_package
- Distinctive: line 36
Validation: Verify package integrity and dependencies
- Distinctive: line 40
All production changes require explicit human authorization
- Very specific: line 43
Use al_publish_existing_extension when deploying pre-built .app files
- Distinctive: line 44
Verify package compatibility with target environment
- Very specific: line 47
Use al_full_package when creating packages with all dependencies
- Distinctive: line 61
Verify extension appears in Extension Management
- Distinctive: line 62
Check all functionality works as expected
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build and Deploy AL Extension
Values in angle brackets come from the text typed after the command; ask for any that are missing.
Your goal is to build and deploy the AL extension for <DeploymentType> environment.
Select Deployment Strategy
Based on #codebase select the appropriate deployment strategy Ask and confirm with the user before proceeding.
Deployment Types
Based on the deployment type, use the appropriate strategy:
Development Environment
- Build: Use
al_buildto compile the project - Review: Present build results for human approval
- Deploy: Use
al_incremental_publishfor rapid iteration (requires approval) - Verify: Check for any compilation errors
Testing Environment
- Build: Use
al_buildwith full validation - Package: Create .app file with
al_package - Review: Present package details for human approval
- Deploy: Use
al_publishto deploy with debugging enabled (requires approval) - Test: Ensure all unit tests pass
Production Environment
- Build: Use
al_buildwith strict validation - Package: Create release package with
al_package - Validation: Verify package integrity and dependencies
- Documentation: Generate deployment checklist and present for review
- Human Gate: MANDATORY - Manual approval required before any production action
- Note: Automated deployment to production is intentionally disabled as safeguard
- All production changes require explicit human authorization
Existing Package Deployment
- Use
al_publish_existing_extensionwhen deploying pre-built .app files - Verify package compatibility with target environment
Full Dependency Package
- Use
al_full_packagewhen creating packages with all dependencies - Useful for offline installations or isolated environments
Error Handling
Monitor the output for:
- Compilation errors
- Dependency conflicts
- Publishing failures
- Permission issues
Post-Deployment Verification
After deployment:
- Verify extension appears in Extension Management
- Check all functionality works as expected
- Validate permissions are correctly applied
- Monitor for any runtime errors
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

