weave-audit

Audit Weave graphs for integrity issues and generate remediation reports.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill weave-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weave-audit
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/weave-audit
Command: npx skills add https://github.com/AGM1968/weave --skill weave-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the Weave graph to identify integrity issues, stale work, and structural problems, enabling teams to maintain a healthy, reliable graph-driven workflow.

Core Features & Use Cases

  • Orphaned nodes detection and remediation guidance to prevent drift between planned work and execution.
  • Stuck active nodes detection, blockers, and circular-dependency checks to keep work flowing.
  • Metadata quality checks (type, priority, learnings) and automated health scoring to guide maintenance and pruning.
  • Generated health reports and actionable remediation steps for operators and engineers.

Quick Start

Run the weave-audit workflow to generate a health report for your current Weave graph.

Frequently Asked Questions about weave-audit

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

FAQPage Schema
How do I audit my Weave graph for health issues?

To audit your Weave graph health, run the weave-audit workflow to generate a structured health report. This identifies integrity issues across active, done, and todo nodes, enabling developers to maintain a reliable, graph-driven workflow.

How do I fix orphaned nodes and stuck active tasks in my workflow?

Fix orphaned nodes and stuck active tasks by applying the actionable remediation steps provided in the audit report. The audit detects orphaned nodes, blockers, and circular dependencies to prevent drift and keep work flowing.

What is graph health scoring and how does it check metadata quality?

Graph health scoring evaluates metadata quality by checking node type, priority, and learnings. This automated scoring guides maintenance and pruning by identifying incomplete learnings and missing metadata across your workflow graph.

Can I use this to detect circular dependencies and blocked edge scenarios?

Yes, you can use this audit to detect blocked edge scenarios and circular dependencies. It identifies structural problems and stuck active nodes, outputting recommended remediation steps to keep work flowing through the graph.

When should I run a graph health check on my workflow nodes?

Run a graph health check when you need to enforce end-to-end governance and identify stale work. It is necessary when preventing drift between planned work and execution, or when missing metadata and incomplete learnings degrade graph reliability.