claude-architect

Diagnose failing skills from failure reports and propose generalizable upgrades.

Updated Apr 16, 2026

Search Tags:#versioning #self-improvement #plugin #root-cause-analysis #audit-trail #upgrades

Ready to run

npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill claude-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: claude-architect
Source: https://github.com/duylinhdang1998/claude-template-agent/tree/main/plugins/vfm-agent-company/skills/claude-architect
Command: npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill claude-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-skill helps maintainers systematically improve plugin skills by diagnosing failures, deriving generalizable principles, and upgrading abilities without hardcoding, ensuring long-term reliability across projects.

Core Features & Use Cases

Diagnose user-reported failures for specialists or skills and extract root causes.
Propose generalizable upgrades that codify principles, avoiding hard-coded fixes across different sections, projects, or URLs.
Document upgrades with a formal rubric, bump plugin versions, and maintain an auditable upgrade log.
Apply upgrades to affected SKILL.md and related files, updating UPGRADES.md with traceable evidence.
Score upgrades using a 10-criteria rubric to ensure quality and prevent regressions.

Quick Start

Provide a failure report to trigger an upgrade, then review the resulting UPGRADES entry and updated SKILL.md.

Frequently Asked Questions about claude-architect

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

FAQPage Schema

How do I diagnose root causes from skill failure reports?▼

Diagnosing root causes from skill failure reports involves feeding the failure details into a systematic extraction process that identifies underlying issues and proposes generalizable upgrades without relying on hard-coded fixes.

What is the best way to upgrade plugin skills without hardcoding fixes?▼

Upgrading plugin skills without hardcoding fixes requires deriving codified principles from failure analysis, applying generalizable rules across any project or URL to ensure long-term reliability.

How do I maintain an audit trail for skill version bumps and upgrades?▼

Maintaining an audit trail for skill version bumps requires logging upgrades in an UPGRADES.md file with traceable evidence and scoring changes using a standardized 10-criteria rubric to prevent regressions.

How does a 10-criteria rubric score skill upgrades to prevent regressions?▼

A 10-criteria rubric scores skill upgrades by evaluating proposed changes against standardized quality metrics, ensuring generalizable upgrades maintain reliability and prevent regressions across projects.

Can I apply generalizable skill upgrades across different projects and URLs?▼

You can apply generalizable skill upgrades across different projects and URLs because the process codifies principles from root-cause analysis rather than relying on hard-coded, project-specific fixes.

Why do I need to log traceable evidence when bumping plugin versions?▼

Logging traceable evidence when bumping plugin versions is needed to maintain an auditable upgrade history, documenting how root-cause diagnoses led to specific principled upgrades in SKILL.md files.