skill-manifest

Generate standardized Extension Manifests for CIRCE and DELFOS frameworks.

99|28|Updated Oct 15, 2025

Search Tags:#automation #workflow #extension #manifest #copilot-studio #aldc #bc-mcp

Ready to run

npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-manifest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skill-manifest
Source: https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/packages/foundation/skills/skill-manifest
Command: npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a standardized Extension Manifest to communicate the extension's surface to CIRCE and DELFOS after the Conductor pipeline completes, reducing manual handoff errors and ensuring consistent metadata distribution.

Core Features & Use Cases

Automatically generates a manifest file named {extension-name}-manifest.md with sections for CIRCE, DELFOS, or both, including header metadata and repository references.
Validates the presence and references of al-spec.md, compiled AL objects, and app.json before finalizing the manifest.
Supports producing a single unified manifest or separate manifests depending on target selection, enabling streamlined handoffs in CI/CD pipelines.

Quick Start

Run the manifest generator after a successful extension build to generate the {extension-name}-manifest.md file in the project root or an output/ directory.

Frequently Asked Questions about skill-manifest

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

FAQPage Schema

How do I generate an Extension Manifest for ALDC workflows?▼

To generate an Extension Manifest for ALDC workflows, run the manifest generator after a successful extension build. It consumes al-spec.md, compiled AL objects, and app.json to produce a standardized {extension-name}-manifest.md file.

What is an ALDC Extension Manifest and when do I need one?▼

An ALDC Extension Manifest is a standardized file communicating an extension's surface to downstream frameworks like CIRCE and DELFOS. You need it after the Conductor pipeline completes to ensure consistent metadata distribution and reduce manual handoff errors.

Does the manifest generator support separate manifests for CIRCE and DELFOS?▼

Yes, the manifest generator supports producing separate CIRCE, DELFOS, or combined manifests. You can select the target to generate either a single unified manifest file or distinct manifests depending on your downstream framework requirements.

What files are required to validate before generating the ALDC manifest?▼

Before generating the ALDC manifest, the generator validates the presence and references of al-spec.md, compiled AL objects, and app.json. Ensuring these inputs are present finalizes the manifest with proper repository metadata and AL object references.

Where is the ALDC extension manifest file placed after generation?▼

The ALDC extension manifest file is placed in the project root or an output/ directory after generation. The generator automatically names the file {extension-name}-manifest.md for streamlined handoffs in CI/CD pipelines.

Can I use the manifest generator in CI/CD pipelines for ALDC extensions?▼

Yes, you can use the manifest generator in CI/CD pipelines for ALDC extensions. Running it after a successful extension build streamlines handoffs by automatically producing a validated manifest with proper spec references and repository metadata.