skill-creator-doctor_skill

This skill helps diagnose, repair, and consolidate Claude skills, ensuring healthy loading, registry correctness, and streamlined maintenance.
  • Python

648

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ananddtyagi/cc-marketplace --skill skill-creator-doctor

  • skill_inventory.json63.2 KB
  • SKILL.md40.5 KB

Overview

This skill creates, repairs, maintains, and consolidates modular skills across a Claude plugin ecosystem. It automatically detects and repairs common loading problems, manages registry entries and metadata, and provides workflows for merging or archiving duplicate or obsolete skills. Use it to keep a skill collection healthy and discoverable.

How this skill works

Inspect skill folders, manifest metadata, and the central registry to locate structural and formatting faults. Run automated diagnostics to detect missing registry entries, invalid frontmatter, broken directory structure, or category mismatches, and apply safe repairs or produce actionable diagnostics. Provide merge and archival workflows, duplicate detection, and packaging validation to maintain long-term ecosystem health.

When to use it

  • Create a new skill from a template and initialize its required files and resources
  • Fix a skill that fails to load or shows "unknown skill" errors
  • Diagnose system-wide issues across the skills registry and folder tree
  • Consolidate duplicate or obsolete skills into a single canonical package
  • Validate and package a skill for distribution after edits

Best practices

  • Initialize new skills from the provided template script to ensure correct structure and manifest fields
  • Validate metadata and registry consistency immediately after creating or editing a skill
  • Keep reusable resources (scripts, references, assets) separate from the manifest to minimize loading costs
  • Use the automated repair tool in diagnosis-only mode before applying fixes to review suggested changes
  • Maintain consistent naming between directory names and registry entries to reduce discovery issues

Example use cases

  • Create a new image-processing skill with scripts for deterministic tasks and assets for templates
  • Repair a skill that runtime fails to load because of malformed manifest metadata
  • Run a comprehensive health check to list all skills with issues prior to a platform release
  • Merge two near-duplicate skills into one consolidated package and update registry links
  • Archive an obsolete skill and update the registry to remove triggers and dependencies

FAQ

Run repairs in diagnose-only mode to preview changes. Repairs operate on well-defined fields (registry entries, YAML frontmatter, structural folders) and create backups or report errors before applying fixes.

When should I manually edit the registry?

Use manual edits for advanced customizations not covered by automation (complex category changes, custom triggers). Prefer the automated tools for routine fixes and validation to reduce human error.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational