customer-card-render Skill
Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline Published by microsoft in hve-core.
Decision snapshot
Is this a fit?
Documentation, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is customer-card-render Skill?
Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline Published by microsoft in hve-core. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Design and media
- Documentation use cases
- Design and media use cases
Declared skill metadata
- Declared license: MIT
- Compatibility: Requires Python 3.11+, uv, and the experimental powerpoint skill
- Source file: .github/skills/experimental/customer-card-render/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use customer-card-render Skill
- Use it for documentation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/hve-core
- Skill file: .github/skills/experimental/customer-card-render/SKILL.md
What it does
Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline
Skill instructions
Customer Card Render Skill Converts canonical Design Thinking markdown artifacts into PowerPoint skill content.yaml slide definitions and builds the final deck through the shared PowerPoint build pipeline. Overview This skill is a sibling to the experimental powerpoint skill. It handles the Design Thinking-specific mapping layer: extracting sections from canonical markdown artifacts and filling template-driven content.yaml files. The PowerPoint skill then owns layout rendering, theming, export, and validation. Keeping these concerns separate means: Customer-card mapping logic stays independent from general PowerPoint capabilities. The skill can be included in packages independently. Layout primitives, Invoke-PptxPipeline.ps1, theming, and validation behavior are not reimplemented here. For full PowerPoint pipeline documentation, activate the powerpoint skill by name. When it does not resolve, warn the user that the pipeline documentation and build behavior are unavailable and stop rath
Verified compatibility and discovery
Frequently asked questions
What is customer-card-render?
customer-card-render is a open-source AI agent skill with Copy skill directory. Generate customer-card PowerPoint content YAML from Design Thinking canonical artifacts and build using the shared PowerPoint skill pipeline
Who is customer-card-render best for?
customer-card-render is best for reusing agent instructions, scripts, and references, documentation workflows, design and media workflows.
How do I install customer-card-render?
Install or run customer-card-render using Copy skill directory. Check customer-card-render for the latest setup command.
Is customer-card-render actively maintained?
customer-card-render may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
