javiarmesto

Guide users through adding a new connector action to a Copilot Studio agent. Connector actions require UI-based connection setup, so this skill walks users through the Copilot Studio portal steps, then delegates to edit-action for YAML modifications.

Generate and insert an Adaptive Card into a Copilot Studio topic using AdaptiveCardPrompt. Use when the user asks to add an adaptive card, rich card, form card, info card, confirmation card, or interactive card to a topic.

Add generative answer nodes (SearchAndSummarizeContent or AnswerQuestionWithAI) to a Copilot Studio topic. Use this instead of /add-node when the user asks to add grounded answers, knowledge search, generative answers, or AI-powered responses — these nodes require specific patterns (ConditionGroup follow-up, knowledge source references, autoSend, responseCaptureType) that /add-node does not cover.

Add a knowledge source (public website or SharePoint) to a Copilot Studio agent. Use when the user asks to add a knowledge source, documentation URL, website, or SharePoint site for the agent to search.

Add or modify a node in an existing Copilot Studio topic. Use when the user asks to add a question, message, condition, variable, or other node to a topic. Do NOT use this for generative answers or knowledge search — use /add-generative-answers instead.

Add child agents, connected agents, or other multi-agent patterns to a Copilot Studio agent. Use when the user asks to create a sub-agent, child agent, connected agent, or call another agent.

Pre-built TaskDialog templates for common Business Central MCP operations. Provides ready-to-use action YAML files for customer balance, overdue invoices, payment creation, sales orders, incident creation, and item availability.

Complete agent blueprints for typical Business Central scenarios — ready-to-implement specifications that combine all BC Extension Pack skills (MCP setup, instructions, actions, topics) into end-to-end agent definitions. Covers collections, sales assistant, and customer support agents.

Generates a handoff manifest at the end of the ALDC pipeline, enabling CIRCE and/or DELFOS to consume the extension's published surface without sharing a workspace. Activates after the Conductor pipeline completes successfully.

Generates a handoff manifest at the end of the ALDC pipeline so CIRCE and DELFOS can consume the extension's published surface without sharing a workspace. Use when the Conductor pipeline has completed successfully (extension compiles, all tests pass, all HITL gates cleared) and you need to emit the extension manifest from al-spec.md and the compiled .al objects.

AL API development patterns for Business Central. Use when creating OData/REST API pages, HttpClient integrations, webhook implementations, or any external system integration via API.

AL Copilot capability development for Business Central. Use when implementing PromptDialog pages, AI generation features, or integrating with the Copilot toolkit.

AL debugging and diagnostics for Business Central. Use when performing snapshot debugging, CPU profiling, analyzing telemetry, or troubleshooting runtime issues.

AL event-driven architecture for Business Central. Use when creating EventSubscribers, IntegrationEvents, BusinessEvents, or implementing publisher/subscriber patterns in extensions.

AL version migration for Business Central. Use when upgrading extensions between BC versions, handling breaking changes, or implementing rollback strategies.

AL page design patterns for Business Central. Use when creating Card, List, ListPart, Document pages, implementing page extensions, or designing UX layouts.

Seeds the ALDC project setup that apm install does not deploy (Copilot entrypoint, aldc.yaml, plans/memory.md, tools/). Use when initializing a new Business Central project with ALDC, right after apm install, on any OS including Claude Code.

Generates a handoff manifest at the end of the ALDC pipeline so CIRCE and DELFOS can consume the extension's published surface without sharing a workspace. Use when the Conductor pipeline has completed successfully (extension compiles, all tests pass, all HITL gates cleared) and you need to emit the extension manifest from al-spec.md and the compiled .al objects.

Spec-Driven Development (SDD) contract templates for the ALDC framework. Use when an ALDC agent or workflow needs the canonical document template for an architecture doc, spec, test plan, planning findings, code review render, BCQuality task-context, phase/plan completion report, delivery note, or memory file. Loads the immutable template from assets/ on demand. Never edit a template in place — copy it to the target path and fill it.

AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.

Generate, review, and optimize natural language instructions for Business Central agents (Designer or SDK). Triggers on: agent instructions, InstructionsV1.txt, InstructionsV2.txt, MEMORIZE, qualification rules, agent behavior, instruction keywords, agent task instructions, iterate instructions, or improve agent accuracy. Single source of truth for the Responsibilities-Guidelines-Instructions framework and runtime keywords.

Agent SDK task integration patterns for Business Central. Triggers on: Agent Task Builder, Agent Task Message Builder, Public API, AssignTask, ExternalId, agent session detection, BindSubscription, TryFunction agent task, multi-turn agent conversation, agent attachment, task lifecycle management, OnPrem-only methods, AddToTask, SetRequiresReview, SetSkipMessageSanitization, runtime availability.

Build, configure, and integrate Business Central agents using the AI Development Toolkit and Agent SDK. Triggers on Agent SDK, Agent Metadata Provider, IAgentFactory, IAgentMetadata, IAgentTaskExecution, ConfigurationDialog, Agent Task Builder, Agent Session, Copilot Capability, agent instructions, or agent setup in BC context.

Perform a static audit of an AL workspace for Business Central against the project's copilot-instructions.md contract. Reports findings by class (Compliance, Code quality, Test coverage, Permissions) and severity (Blocker, Major, Minor, Nit) with file:line citations. Never modifies code. Never invents rules. Use when asked to audit a workspace, run a compliance check, review before PR, or diagnose contract drift.

Implements standard document attachments, links, and notes on custom Business Central tables. Creates setup fields for visibility control, extends Attachment Document Type enum, generates event subscribers (OnBeforeDrillDown, OnAfterOpenForRecRef, OnAfterInitFieldsFromRecRef) in attachment management codeunit, adds table lifecycle triggers for orphan prevention on delete/rename, and extends card and list pages with both legacy and modern factboxes. Handles SubPageLink configuration, control ID mapping for Links (Control1900383207) and Notes (Control1905767507) factboxes. Use when adding attachments to custom tables, implementing document management, enabling factboxes for documents, creating attachment integration on entities, adding links and notes to records, or preventing orphan attachment records on table operations.

AL App/Test project layout diagnosis for Business Central. Use when the main app compiles test sources, AL0297 appears on test object IDs, Library Assert or Library - Sales is missing, test/app.json is not recognized, or a multi-root workspace with app and test projects needs diagnosis.

Convert Markdown files to Word (.docx) documents using pandoc. Use when asked to "convert markdown to word", "export md to docx", "generate word document from markdown", "create docx from md", "formato Delfos", "documento para cliente", "generar word", or when working with .md files that need professional Word document output. Supports custom templates (including Delfos dark branded template), table of contents, metadata, cover pages, styles, headers/footers, page breaks, images, and batch conversions. Always use the Delfos template (templates/delfos-dark-template.docx) unless another template is explicitly requested.

Map Power BI star schema designs to Business Central data sources. Analyzes a Delfos architecture document, matches tables against BC API v2.0 standard entities, identifies coverage gaps, and generates ALDC-compatible requirement specs for custom API Pages. Use when a Power BI project needs data from Business Central and you need to determine which APIs exist and which must be built.