validate-extension-submission

Validate extension repositories against Extension Index submission requirements.

Updated Jan 25, 2026

Search Tags:#extension #quality-assurance #validate #submission #extension-index #repo-checks

Ready to run

npx skills add https://github.com/benzwick/SlicerMouseMaster --skill validate-extension-submission

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validate that extensions meet all Extension Index submission requirements, preventing delays and back-and-forth remediation during submission.

Core Features & Use Cases

Checks repository structure and required files (CMakeLists.txt, LICENSE, README.md) and core metadata (HOMEPAGE, CONTRIBUTORS, DESCRIPTION, ICONURL, SCREENSHOTURLS) to ensure submission readiness.
Validates the presence (and if present, the conformity) of an Extension JSON file to the current schema, if included in the repository.
Verifies repository health indicators, such as the 3d-slicer-extension topic, license type, and URL accessibility for homepage, icon, and screenshots.
Provides remediation guidance and a concise validation report to streamline Extension Index submissions.

Quick Start

Run the validation script to verify readiness for Extension Index submission.

Frequently Asked Questions about validate-extension-submission

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

FAQPage Schema

How do I validate an extension for Extension Index submission?▼

Extension Index submission validation inspects your repository structure, metadata files, and URL accessibility for homepage, icon, and screenshots. It confirms required files like CMakeLists.txt and LICENSE are present and provides a concise report with remediation guidance for submission readiness.

What repository files are required for Extension Index submission?▼

Required files for Extension Index submission include CMakeLists.txt, LICENSE, and README.md. The validation also checks for metadata files like CONTRIBUTORS, DESCRIPTION, HOMEPAGE, ICONURL, and SCREENSHOTURLS to confirm the repository meets all submission requirements.

Does my extension need an Extension JSON file to pass submission validation?▼

An Extension JSON file is not mandatory for submission validation, but if present, the validator checks its conformity to the current schema. This ensures any included Extension JSON meets the required structural standards for the Extension Index.

Why does my extension submission validation fail on URL accessibility?▼

Submission validation fails on URL accessibility when the links for HOMEPAGE, ICONURL, or SCREENSHOTURLS are unreachable. The validator checks these URLs to ensure all extension resources are publicly available and accessible for the Extension Index.

Can I check my extension repository health before submitting to the Extension Index?▼

You can check repository health before submitting by validating indicators like the 3d-slicer-extension topic, license type, and URL accessibility for homepage, icon, and screenshots. The validator provides a concise report with remediation guidance to streamline Extension Index submissions.

What is the best way to prepare an extension for Extension Index submission?▼

The best way to prepare an extension for Extension Index submission is to run a validation script that inspects repository structure, metadata fields, licensing, and URL accessibility. This proactive check prevents delays and back-and-forth remediation during the submission process.