status

Generate a metaswarm diagnostic report by parsing JSON/YAML manifests and probing CLI availability.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Prekzursil/quality-zero-platform --skill status-prekzursil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/Prekzursil/quality-zero-platform/tree/main/.claude/plugins/metaswarm/skills/status
Command: npx skills add https://github.com/Prekzursil/quality-zero-platform --skill status-prekzursil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill produces a consolidated diagnostic report that reveals metaswarm installation state, project configuration status, missing or misrouted command shims, plugin conflicts, and external tool availability to accelerate troubleshooting and migration decisions.

Core Features & Use Cases

  • Checks plugin version from plugin.json or package.json and reports fallbacks or read errors.
  • Verifies project setup by inspecting .metaswarm/project-profile.json and reporting key fields or the absence of configuration.
  • Validates presence and routing of command shims, detects legacy embedded plugins, scans for BEADS plugin installations, probes bd and Node.js CLI availability, and summarizes external tool adapter configuration and coverage thresholds.
  • Use case: run before onboarding a repository or performing migrations to detect conflicts and provide prioritized remediation steps.

Quick Start

Run the status skill to generate a full metaswarm diagnostic report for the current working directory and environment.

Frequently Asked Questions about status

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

FAQPage Schema
How do I diagnose my metaswarm installation state and project configuration?

To diagnose a metaswarm installation, generate a consolidated diagnostic report that probes plugin versions, project configuration, and command shims. This report reveals missing components, misrouted shims, and configuration conflicts to accelerate troubleshooting.

Why are my metaswarm command shims missing or misrouted?

Command shims become missing or misrouted due to legacy embedded plugins or incorrect installation paths. Validating shim presence and routing detects these conflicts and provides prioritized remediation steps to resolve the misrouting.

Can I check metaswarm plugin versions and external tool availability in a CI context?

Yes, you can validate metaswarm plugin versions and external tool availability in CI contexts. The diagnostic process probes plugin manifests, checks bd and Node.js CLI availability, and summarizes external tool adapter coverage thresholds for local and CI environments.

What is the best way to detect plugin conflicts before migrating a repository?

The best way to detect plugin conflicts before repository migration is to run a diagnostic scan. This scans for BEADS plugin installations, checks fallbacks or read errors in plugin manifests, and surfaces missing components for prioritized remediation.

Does metaswarm diagnostic validation modify my project files during troubleshooting?

Metaswarm diagnostic validation performs non-destructive file checks only. It parses JSON/YAML project and plugin manifests to inspect configuration status without modifying your files, ensuring a safe troubleshooting and onboarding process.

How do I verify my .metaswarm/project-profile.json setup?

Verify your .metaswarm/project-profile.json setup by inspecting the file and reporting key configuration fields. This validation reports the presence or absence of project configuration to confirm your metaswarm project setup is correct.