pack-doctor

Diagnose Anteroom pack and artifact issues with non-destructive remediation steps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/troylar/anteroom --skill pack-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pack-doctor
Source: https://github.com/troylar/anteroom/tree/main/src/anteroom/cli/default_skills/pack-doctor
Command: npx skills add https://github.com/troylar/anteroom --skill pack-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and explains problems in anteroom pack and artifact ecosystems so teams can quickly understand impact and remediate without guessing. It aggregates artifact health checks, source status, lockfile mismatches, and common configuration conflicts into a single readable diagnosis.

Core Features & Use Cases

  • Interprets artifact health check output and explains why each issue matters, with category-specific remediation guidance.
  • Verifies pack sources and cache health, checks lock file presence and validity, and detects shadowing, duplicates, or orphaned artifacts.
  • Produces a concise summary with counts, prioritized issues, and a list of auto-fixable items while explicitly avoiding destructive actions unless the user requests them.
  • Use case: Onboarding a new developer who sees unexpected skill behavior because a pack collision is shadowing a built-in skill; run this Skill to locate the collision, explain the risk, and list exact non-destructive steps to fix it.

Quick Start

Run the pack-doctor on the current project to generate a prioritized, non-destructive report of pack and artifact issues with clear remediation steps.

Frequently Asked Questions about pack-doctor

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

FAQPage Schema
How do I diagnose pack and artifact issues in an Anteroom project?

Run a diagnostic health check on your Anteroom project to analyze pack sources, lock files, and installed artifacts. This produces a prioritized, non-destructive report explaining each issue and listing specific remediation steps to resolve conflicts.

Why does a pack collision shadow a built-in skill and cause unexpected behavior?

Duplicate artifacts override expected sources during installation, causing a pack collision that shadows built-in skills. Diagnosing the artifact ecosystem identifies the exact collision, explains the risk, and lists non-destructive commands to resolve the shadowing.

What is the best way to detect lock file mismatches and orphaned artifacts?

Run an artifact health check that verifies pack sources, validates lock file presence, and flags shadowing or duplicate artifacts. This produces a concise summary with prioritized issues and counts for quick remediation.

Can I automatically fix pack source and cache health issues during CI checks?

Automatic fixes are avoided unless explicitly requested. The diagnostic process identifies auto-fixable items but avoids destructive actions, providing specific non-destructive commands and next steps for safe remediation during CI checks.

How do I interpret artifact health check output and explain the impact?

Apply diagnostic analysis to each category within the artifact health check output to generate severity labels and human-readable explanations. This clarifies why each issue matters and produces actionable remediation guidance for the team.