skill-extension-manifest

Generate validated handoff manifests for AL extensions consumed by CIRCE and DELFOS after pipeline completion.

99|28|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-extension-manifest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-extension-manifest
Source: https://github.com/javiarmesto/ALDC-AL-Development-Collection/tree/main/claude-plugin/skills/skill-extension-manifest
Command: npx skills add https://github.com/javiarmesto/ALDC-AL-Development-Collection --skill skill-extension-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Extension Manifest Generator automates the production of handoff manifests at the end of the ALDC pipeline, enabling CIRCE and/or DELFOS to consume an extension's published surface without exposing workspace details.

Core Features & Use Cases

  • Generates a structured manifest including MCP connection context, Published API Pages, Data Structure, and Star Schema Hints.
  • Supports targeting CIRCE, DELFOS, or both, with interactive gates to confirm consumers and environment details.
  • Validates inputs from AL sources (app.json, al-spec.md, and deployed AL objects) before emission and outputs a standardized filename and structure for downstream tooling.

Quick Start

Provide the extension inputs and trigger the Conductor to generate the manifest after the Conductor pipeline completes successfully.

Frequently Asked Questions about skill-extension-manifest

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

FAQPage Schema
How do I generate a handoff manifest for AL extensions?

To generate a handoff manifest for AL extensions, trigger the Conductor pipeline after providing extension inputs like app.json and al-spec.md. The manifest is auto-generated upon successful pipeline completion, producing a structured markdown file for downstream consumption.

What is an AL extension manifest and when do I need one?

An AL extension manifest is a structured markdown file documenting MCP connection context, Published API Pages, Data Structure, and Star Schema Hints. You need it when handing off completed AL objects to CIRCE or DELFOS to expose an extension's published surface without revealing workspace details.

Does the manifest generator validate AL sources before creating the handoff document?

Yes, the manifest generator validates inputs from AL sources, including app.json, al-spec.md, and deployed AL objects, before emission. This ensures all produced fields match actual repository objects and no endpoints or fields are invented.

Can I target the generated manifest for both CIRCE and DELFOS consumers?

Yes, you can target CIRCE, DELFOS, or both. The generator includes interactive gates to confirm consumers and environment details, ensuring the output manifest is correctly configured for your specified downstream tools.

How do I start the manifest generation after the Conductor pipeline completes?

Provide the extension inputs and trigger the Conductor to generate the manifest after the Conductor pipeline completes successfully. It reads the completed AL objects to produce a single {extension-name}-manifest.md with standardized sections for downstream tooling.