partnership-microdemo

Source 20-30 second proof clips and generate a provenance YAML manifest.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill partnership-microdemo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: partnership-microdemo
Source: https://github.com/dimagi-internal/ace/tree/main/skills/partnership-microdemo
Command: npx skills add https://github.com/dimagi-internal/ace --skill partnership-microdemo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the time-consuming work of manually creating custom demo clips for partnership pitches by first checking for reusable existing media, and only building lightweight tailored mocks when no suitable clip exists, while automatically tracking the provenance of every clip for evaluation and downstream video build teams.

Core Features & Use Cases

  • Reuse-First Sourcing: Queries the ace-web media library for existing clips that match the selected partnership angle's product beat, prospect sector, and required capability, cutting down on unnecessary custom work.
  • Lightweight Mock Fallback: Builds credible 20-30 second tailored clips via Nova app stub + canopy walkthrough or headless gstack browse capture when no existing media matches, keeping effort minimal while maintaining plausibility.
  • Full Provenance Tracking: Generates a machine-parsed YAML manifest recording each clip's source, origin, file ID, and caption, so downstream teams have full visibility into clip origins.
  • Use Case: For a partnership pitch targeting an education sector prospect, the Skill can quickly source an existing clip showing a CommCare education workflow, or build a quick mock of the relevant feature if no existing clip matches, and log all details for the video build team.

Quick Start

Use the partnership-microdemo skill to source a short proof clip for your selected partnership angle and target prospect, reusing existing media from the ace-web library or building a lightweight tailored mock if needed, and generate the required provenance manifest.

Frequently Asked Questions about partnership-microdemo

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

FAQPage Schema
How do I source short partnership sales demo clips without building from scratch?

Partnership micro-demo clips are 20-30 second proof clips demonstrating a specific product beat for a selected prospect. They are sourced by reusing existing media from the ace-web library or building lightweight mocks via Nova app stubs when no match exists. Each clip is tracked with full provenance metadata.

Can I track the source and origin of media clips used in partnership pitches?

Provenance tracking works by generating a machine-parsed YAML manifest that records each clip's source, origin, file ID, and caption. This manifest integrates with the ACE partnership lifecycle orchestrator via a phase write-back to the run state file, giving downstream teams full visibility into clip origins.

What happens if no existing media matches the partnership angle I need?

When no existing media matches your partnership angle, the system builds a lightweight tailored mock using Nova app stubs with canopy walkthroughs or headless gstack browse captures. This fallback creates a credible 20-30 second proof clip while keeping custom effort minimal.

Do I need the ACE partnership lifecycle orchestrator to use this micro-demo workflow?

The Skill writes a phase write-back to the run state file to integrate with the ACE partnership lifecycle orchestrator, so having that orchestrator active ensures proper lifecycle integration. The micro-demo workflow is designed specifically for partnership sales contexts and produces provenance manifests for downstream teams.

Best way to create tailored mock demo clips for partnership pitches?

Lightweight tailored mocks are best built using Nova app stubs with canopy walkthroughs or headless gstack browse captures. This approach creates credible 20-30 second clips with minimal effort and is triggered automatically when existing ace-web library media does not match your prospect sector or required capability.

Why does my partnership sales workflow need a provenance manifest for demo clips?

A provenance manifest is needed because it tracks each clip's source, origin, file ID, and metadata for downstream evaluation and video build teams. Without it, teams evaluating partnership pitches lack visibility into whether clips were reused from the ace-web library or built as lightweight custom mocks.