prepare-extension-metadata

Automate preparation and validation of Extension Index metadata and CMakeLists.txt updates.

Updated Jan 25, 2026

Search Tags:#validation #extension #json #metadata #cmake #extension-index

Ready to run

npx skills add https://github.com/benzwick/SlicerMouseMaster --skill prepare-extension-metadata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prepare-extension-metadata
Source: https://github.com/benzwick/SlicerMouseMaster/tree/main/.claude/skills/prepare-extension-metadata
Command: npx skills add https://github.com/benzwick/SlicerMouseMaster --skill prepare-extension-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the preparation and validation of all metadata required for Slicer ExtensionsIndex submissions, reducing manual errors and ensuring schema compliance.

Core Features & Use Cases

Gathers required fields from the repository and user input for CMakeLists.txt and Extension Index JSON.
Guides schema validation by fetching the latest schema and ensuring consistency across all submission files.
Generates the JSON entry for the Extension Index and provides verification checks for URLs and assets.

Quick Start

Run the skill to prepare and update your extension's CMakeLists.txt and Extension Index JSON for submission.

Frequently Asked Questions about prepare-extension-metadata

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

FAQPage Schema

How do I prepare Extension Index metadata for a 3D Slicer extension submission?▼

This Skill automates preparing Extension Index metadata for 3D Slicer extensions by gathering required fields from your repository, generating the JSON entry, and updating CMakeLists.txt to ensure submission compliance.

How does schema validation work for 3D Slicer extension JSON metadata?▼

Schema validation for 3D Slicer extension JSON works by fetching the latest schema and enforcing consistency checks across all submission files. This ensures your metadata remains compliant before entering the Extension Index.

Can I use this metadata preparation process for multi-repository Slicer extension workflows?▼

Yes, this metadata preparation process supports multi-repository Slicer extension workflows. It applies to both single-extension and multi-repository setups, guiding schema validation and JSON generation seamlessly.

What is the best way to validate URLs and assets in Slicer extension metadata?▼

The best way to validate URLs and assets in Slicer extension metadata is to use an automated preparation tool that performs verification checks. This Skill reports any URL or asset validation failures during the JSON generation process.

Why does my Slicer extension submission fail metadata consistency checks?▼

Slicer extension submissions fail metadata consistency checks when required fields are missing or outdated schemas are used. This Skill enforces the latest schema, requests missing fields, and performs consistency checks to prevent these errors.