twl:workflow-plugin-diagnose

Diagnose and fix TwL plugin structure, frontmatter, and architecture issues.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/shuu5/twill --skill twl-workflow-plugin-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twl:workflow-plugin-diagnose
Source: https://github.com/shuu5/twill/tree/main/plugins/twl/skills/workflow-plugin-diagnose
Command: npx skills add https://github.com/shuu5/twill --skill twl-workflow-plugin-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and repairs issues in existing TwL plugins, enabling reliable behavior and maintenance through a structured end-to-end workflow.

Core Features & Use Cases

  • Stepwise evaluation of plugin health: migrate-analyze, diagnose, plugin-phase-diagnose, fix, verify, and plugin-phase-verify.
  • Orchestrates detection of structure, frontmatter consistency, architecture patterns, orphan nodes, and deep validation.
  • Use Case: When a plugin doesn’t conform to expected patterns or shows regression, run this workflow to diagnose and automatically apply fixes.

Quick Start

Start the workflow by invoking /twl:workflow-plugin-diagnose to run the end-to-end plugin diagnose cycle.

Frequently Asked Questions about twl:workflow-plugin-diagnose

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

FAQPage Schema
How do I diagnose and fix architecture issues in an existing plugin?

To diagnose plugin architecture issues, run an end-to-end workflow that evaluates plugin health, detects structure inconsistencies, and automatically applies repairs to ensure correct behavior and validation.

What is the best way to repair orphan nodes and frontmatter problems in TwL plugins?

Repairing orphan nodes and frontmatter problems involves a stepwise evaluation process covering migrate-analyze, diagnose, fix, and verify phases to restore plugin consistency and resolve integration issues automatically.

How do I run a full plugin validation and verification cycle?

Run a full plugin validation cycle by invoking the end-to-end plugin diagnose workflow, which coordinates analyze, diagnose, fix, and verify steps to detect deep validation issues and apply necessary fixes.

When should I use an automated workflow for plugin diagnosis?

Use an automated plugin diagnosis workflow when your plugin doesn't conform to expected patterns, shows regression, or exhibits frontmatter and architecture issues that require structured detection and automated fixing.

Can I fix plugin integration problems and structure issues without manual inspection?

Yes, you can fix plugin integration and structure issues without manual inspection by running a coordinated workflow that handles migrate-analyze, diagnose, fix, and verify phases to automatically apply necessary repairs.