status

Diagnose metaswarm installation health with automated version, setup, and tooling checks.

Updated Apr 6, 2018
One-click install
npx skills add https://github.com/montoyaedu/Trish --skill status-montoyaedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/montoyaedu/Trish/tree/main/.claude/plugins/metaswarm/skills/status
Command: npx skills add https://github.com/montoyaedu/Trish --skill status-montoyaedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnostically assesses metaswarm installation health, project configuration, and potential issues to reduce downtime and confusion.

Core Features & Use Cases

  • Performs version discovery for plugin and environment, reports project setup state, and checks for required tooling availability.
  • Enumerates common issues and actionable remediation guidance, including legacy plugin conflicts and tool installation verification.
  • Use Case: A developer runs this skill on a CI runner or workstation to quickly verify that metaswarm is ready to operate and to pinpoint misconfigurations.

Quick Start

Run the status skill to generate a comprehensive health report for the current metaswarm workspace.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check metaswarm installation health and verify version setup?

Check metaswarm installation health by running an automated diagnostic skill that verifies version setup, plugin roots, project directories, and tool availability, returning a structured summary with remediation guidance.

What is the best way to diagnose metaswarm misconfigurations on a CI runner?

The best way to diagnose metaswarm misconfigurations on a CI runner is running an automated health check that enumerates common issues like legacy plugin conflicts and returns actionable remediation steps.

Why does my metaswarm workspace report setup errors and missing tooling?

Metaswarm workspace setup errors and missing tooling occur when required environment dependencies are absent or misconfigured; a diagnostic health check pinpoints these issues and provides remediation guidance.

Can I use a diagnostic report to verify runtime environments and project directories?

Yes, you can use a diagnostic report to verify runtime environments and project directories by performing automated checks that assess plugin roots, configuration state, and tool availability.

What steps are needed to troubleshoot legacy plugin conflicts in metaswarm?

Troubleshoot legacy plugin conflicts in metaswarm by running a health diagnostic that enumerates common issues, identifies conflicting plugins, and provides structured remediation guidance to resolve them.