extension-manifest

Generate handoff manifests for CIRCE and DELFOS after ALDC pipeline completion.

Updated May 22, 2026

Search Tags:#extension development #manifest generation #CIRCE #DELFOS #ALDC pipeline

Ready to run

npx skills add https://github.com/javiarmesto/SampleDynamicsMinds --skill extension-manifest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extension-manifest
Source: https://github.com/javiarmesto/SampleDynamicsMinds/tree/main/.agents/skills/skill-manifest
Command: npx skills add https://github.com/javiarmesto/SampleDynamicsMinds --skill extension-manifest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of handoff manifests at the end of the ALDC pipeline, enabling CIRCE and/or DELFOS to consume an extension's published surface without sharing a workspace.

Core Features & Use Cases

Automated Manifest Generation: Generates a handoff manifest after the Conductor pipeline completes successfully.
User Interaction: Requires user input to select target consumers and provide connection details.
Manifest Structure: Outputs a manifest containing headers, sections for CIRCE and DELFOS, and a footer.
Use Case: For example, after compiling an extension, use this Skill to generate a manifest for consumption by CIRCE to build a Copilot Studio agent against the extension.

Quick Start

Run the extension-manifest skill after the Conductor pipeline completes successfully to generate the handoff manifest.

Frequently Asked Questions about extension-manifest

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

FAQPage Schema

How do I generate a handoff manifest for CIRCE and DELFOS after an ALDC pipeline build?▼

To generate a handoff manifest for CIRCE and DELFOS, run the extension-manifest skill after the ALDC pipeline completes successfully. It reads from spec files, source files, and metadata, then requires user interaction to select target consumers and provide connection details before outputting the final manifest.

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

An extension handoff manifest enables systems like CIRCE and DELFOS to consume an extension's published surface without sharing a workspace. You need this manifest at the end of the ALDC pipeline when you want to hand off compiled extension data to downstream consumers like Copilot Studio agents.

Can I use this manifest generation process if my Conductor pipeline failed?▼

No, manifest generation requires the Conductor pipeline to complete successfully before running. The skill reads from spec files, source files, and metadata produced by the pipeline, so a failed build will not provide the valid inputs needed to output the CIRCE and DELFOS manifest sections.

What inputs are required to create a handoff manifest for CIRCE?▼

Creating a handoff manifest requires spec files, source files, and metadata from the completed ALDC pipeline. During the process, user interaction is required to select target consumers and provide connection details, which are then structured into headers, CIRCE and DELFOS sections, and a footer.

Why does manifest generation require user interaction during the handoff process?▼

Manifest generation requires user interaction to select target consumers and provide connection details for CIRCE and DELFOS. This ensures the output manifest correctly routes the extension's published surface to the appropriate downstream systems without workspace sharing.

Are there limitations to automating handoff manifests for the ALDC pipeline?▼

The main limitation is dependency on successful ALDC pipeline completion; the manifest cannot be generated without valid spec files, source files, and metadata. Additionally, the required user interaction for target selection and connection details prevents fully automated, headless manifest generation.