Stripe Projects
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
AL event-driven architecture for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-events --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skill-events .claude/skills/skill-events && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .claude/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-eventsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-events --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skill-events .agents/skills/skill-events && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .agents/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-events --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skill-events .cursor/skills/skill-events && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .cursor/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/javiarmesto/ALDC-AL-Development-Collection.git --path skills/skill-events--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-events --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skill-events .gemini/skills/skill-events && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .gemini/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-eventsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skill-events .github/skills/skill-events && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .github/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install javiarmesto/ALDC-AL-Development-Collection skill-events --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/javiarmesto/ALDC-AL-Development-Collection.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skill-events .opencode/skills/skill-events && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "skill-events" agent skill from https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/skills/skill-events into .opencode/skills/skill-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-events", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skill-eventsAL event-driven architecture for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
Skill Events is an agent skill from javiarmesto/ALDC-AL-Development-Collection. AL event-driven architecture for Business Central. Use when creating EventSubscribers, IntegrationEvents, BusinessEvents, or implementing publisher/subscriber patterns in extensions.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Event-driven systems. The repository describes itself as: AL development toolkit for Business Central with specialist agents, skills and review workflows for Copilot, Claude Code and Codex. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4f99d7d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are al).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
learn.microsoft.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Skill Events loads about 2.5k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 658 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from javiarmesto/ALDC-AL-Development-Collection at commit 4f99d7d, republished under its MIT licence (© javiarmesto). 658 words, ~2,546 tokens.
.claude/skills/skill-events/SKILL.md (or your agent's skills folder).Discover, design, and implement event-driven patterns in AL Business Central extensions: event discovery via Event Recorder, subscriber/publisher creation, IsHandled patterns, and extensibility design.
This skill should be loaded when:
Before writing any subscriber, discover which events are raised during the business process:
1. Open the Event Recorder in VS Code ← VS Code command (not an agent tool)
2. Start recording
3. Execute the business process in BC (e.g., post a sales order)
4. Stop recording
5. Analyze the event list — filter by object or keyword
6. Identify the OnBefore/OnAfter event closest to your extension pointUse al_search_objects and al_get_object_definition to inspect publisher signatures.
Use al_find_references to see who else subscribes to the same event.
// Subscriber codeunit — name with "Handler" suffix
codeunit 50100 "Sales Document Events Handler"
{
// Attribute breakdown:
// ObjectType — Table, Codeunit, Page, Report, etc.
// ObjectId — Database::"Sales Header" or Codeunit::"Customer Management"
// EventName — exact name of the publisher procedure (e.g., OnBeforeInsert)
// ElementName — '' for table/codeunit events; field name for page field triggers
// SkipOnMissingLicense — false (recommended: always run)
// SkipOnMissingPermission — false (recommended: always run)
[EventSubscriber(ObjectType::Table, Database::"Sales Header",
OnBeforeInsert, '', false, false)]
local procedure OnBeforeInsertSalesHeader(
var SalesHeader: Record "Sales Header";
RunTrigger: Boolean)
begin
ValidateCustomFields(SalesHeader);
end;
}Subscriber rules:
localCommit inside a subscriber unless absolutely necessaryThe standard extensibility pattern: OnBefore allows interception, OnAfter allows reaction.
codeunit 50101 "Customer Management"
{
procedure CreateCustomer(var Customer: Record Customer): Boolean
var
IsHandled: Boolean;
begin
// 1. Raise OnBefore — subscribers can validate, modify, or skip
OnBeforeCreateCustomer(Customer, IsHandled);
if IsHandled then
exit(true);
// 2. Default logic
if not Customer.Insert(true) then
exit(false);
// 3. Raise OnAfter — subscribers can react (logging, integration, etc.)
OnAfterCreateCustomer(Customer);
exit(true);
end;
[IntegrationEvent(false, false)]
local procedure OnBeforeCreateCustomer(
var Customer: Record Customer;
var IsHandled: Boolean)
begin
// Empty body — subscribers provide the implementation
// IsHandled = true → skip default logic
end;
[IntegrationEvent(false, false)]
local procedure OnAfterCreateCustomer(var Customer: Record Customer)
begin
// Empty body — subscribers react after creation
end;
}IntegrationEvent attribute:
IntegrationEvent(IncludeSender, GlobalVarAccess)IncludeSender = false — recommended for clean API (no coupling to publisher internals)GlobalVarAccess = false — recommended (prevent subscribers from accessing publisher global vars)Business events are user-disablable — use for optional, non-critical functionality:
[BusinessEvent(IncludeSender)]
local procedure OnCustomerCreditLimitExceeded(
Customer: Record Customer;
RequestedAmount: Decimal)
begin
// Subscribers may send notification, log, or block — user can disable
end;| Attribute | Cannot be disabled | Use for |
|---|---|---|
IntegrationEvent | Correct | Critical business logic, posting interventions |
BusinessEvent | Can be disabled by user | Optional features, external integrations, notifications |
// ✅ Good — rich context, var where modification expected, IsHandled for OnBefore
[IntegrationEvent(false, false)]
local procedure OnBeforePostDocument(
var DocumentHeader: Record "Sales Header"; // var — subscriber may modify
var DocumentLines: Record "Sales Line"; // var — subscriber may modify
PostingDate: Date; // value — read-only context
var IsHandled: Boolean) // var — subscriber may skip default
begin
end;
// ✅ Good — results context for OnAfter
[IntegrationEvent(false, false)]
local procedure OnAfterPostDocument(
DocumentHeader: Record "Sales Header"; // value — read-only (already posted)
PostedDocumentNo: Code[20]; // result reference
PostingResult: Boolean) // success/failure
begin
end;Parameter design rules:
var Record — when subscribers should be able to modify the recordRecord — when record is read-only contextvar IsHandled: Boolean in OnBefore eventsOnAfter eventsal_get_object_definition to inspect publisher signaturesal_find_references to check existing subscribers (avoid conflicts)For subscribing to existing events:
"{Domain} Events Handler"For creating new integration events in your codeunit:
OnBefore event with IsHandled pattern before key operationsOnAfter event after key operations with result contextOnBefore{Action} / OnAfter{Action}IntegrationEvent (critical) or BusinessEvent (optional)Use the AL: Insert Event Subscriber VS Code command (not an agent tool) to scaffold subscriber/publisher structures, then fill the body:
// Subscriber handler codeunit
codeunit 50102 "Customer Validation Handler"
{
[EventSubscriber(ObjectType::Codeunit, Codeunit::"Customer Management",
OnBeforeCreateCustomer, '', false, false)]
local procedure ValidateOnBeforeCreate(
var Customer: Record Customer;
var IsHandled: Boolean)
begin
ValidateCustomerCreditLimit(Customer);
if ShouldSkipDefaultProcessing(Customer) then
IsHandled := true;
end;
}al_build — check for compilation errors (signature mismatches)al_debugObjectType / ObjectIdIsHandled = true before yours| Scenario | Event Source | Pattern |
|---|---|---|
| Validate before posting | OnBeforePost* on Codeunit "Sales-Post" | Subscriber + IsHandled |
| Add fields to sales order | OnAfterInsert on Table "Sales Header" | Subscriber (set defaults) |
| External integration trigger | OnAfterPostDocument (custom) | Publisher in your codeunit |
| Custom approval workflow | OnBeforeRelease* | Subscriber + IsHandled to block |
| UI field validation | Page trigger OnAfterValidate on field | Subscriber with ElementName |
| Master data change audit | OnAfterModify on Table "Customer" | Subscriber (log changes) |
al-events.instructions.md (auto-applied to all .al files)OnBefore + OnAfter pair at minimumCommit inside event subscribers unless absolutely requiredIsHandled = true without clear documentation of why default logic is skippedskill-debug.mdskill-performance.md© javiarmesto, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/skill-events of javiarmesto/ALDC-AL-Development-Collection.
Open the folder on GitHubat commit 4f99d7d
Skill Events next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Skill Events this skilljaviarmesto/ALDC-AL-Development-Collection | 109 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Stripe Projectsfossasia/eventyay | 1.7k | 5 repos | ~2k | Automated safety check: Notes | Apache-2.0 | |
| MQTTX CLIemqx/MQTTX | 5.1k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| AWS Serverless Edazxkane/aws-skills | 367 | 4 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Windmill Trigger Type Checklistwindmill-labs/windmill | 18k | — | ~4.7k | Automated safety check: Pass | Custom licence | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 |
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
emqx/MQTTX
Operates the `mqttx` command line client to connect, publish, subscribe, benchmark and simulate data against an MQTT broker, with TLS and MQTT 5 support.
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
windmill-labs/windmill
Checklist of every backend, frontend, CLI and capture change needed to add a new TriggerCrud-based trigger type, such as Azure, GCP or Kafka, to Windmill.
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
xiaotianfotos/homerail
Design, start, supervise, inspect, and continue HomeRail DAG workflows from any agent with CLI or HTTP access.
javiarmesto/ALDC-AL-Development-Collection
Generate, review, and optimize natural language instructions for Business Central agents (Designer or SDK).
javiarmesto/ALDC-AL-Development-Collection
AL API development patterns for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
javiarmesto/ALDC-AL-Development-Collection
AL Copilot capability development for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
javiarmesto/ALDC-AL-Development-Collection
AL version migration for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
javiarmesto/ALDC-AL-Development-Collection
Agent SDK task integration patterns for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection.
javiarmesto/ALDC-AL-Development-Collection
Build, configure, and integrate Business Central agents using the AI Development Toolkit and Agent SDK.
Categories
AL event-driven architecture for Business Central. An agent skill from javiarmesto/ALDC-AL-Development-Collection. Skill Events is an agent skill from javiarmesto/ALDC-AL-Development-Collection. AL event-driven architecture for Business Central.
Skill Events fits situations like: creating EventSubscribers; integrationEvents; implementing publisher/subscriber patterns in extensions.
Run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a claude-code`. Or copy the skill folder (skills/skill-events in javiarmesto/ALDC-AL-Development-Collection) into .claude/skills/skill-events in your project. Claude Code loads it when a task matches its description.
Run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a codex`. Or copy the skill folder (skills/skill-events in javiarmesto/ALDC-AL-Development-Collection) into .agents/skills/skill-events in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add javiarmesto/ALDC-AL-Development-Collection --skill skill-events -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-events, .gemini/skills/skill-events, .github/skills/skill-events and .opencode/skills/skill-events in your project.
SKILL.md names no scripts, command-line tools or credentials: Skill Events is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Skill Events is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Skill Events: Stripe Projects (fossasia/eventyay, 1.7k stars), MQTTX CLI (emqx/MQTTX, 5.1k stars), AWS Serverless Eda (zxkane/aws-skills, 367 stars) and Windmill Trigger Type Checklist (windmill-labs/windmill, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
javiarmesto (a GitHub user) maintains it in javiarmesto/ALDC-AL-Development-Collection, which has 109 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 7, 2026.
Source: javiarmesto/ALDC-AL-Development-Collection on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.