keystone:audit

Audit a Keystone charter with dual-flywheel learning and pruning phases.

42|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/tacoda/keystone --skill keystone-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keystone:audit
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-audit
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires keystone, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of auditing a Keystone charter, ensuring its health and compliance with standards by performing a dual-flywheel audit that includes learning and pruning.

Core Features & Use Cases

  • Dual-Flywheel Audit: Combines learning (capturing from review) and pruning (removing dead rules) to maintain charter health.
  • Automated Checklist: Follows a 12-category pruning checklist for stale rules, dead idioms, placeholders, and more.
  • Use Case: After a major refactor or stack change, or when the dashboard's debt count feels wrong, use this Skill to ensure the charter remains robust and efficient.

Quick Start

Run the keystone:audit skill to perform a dual-flywheel audit on your charter.

Frequently Asked Questions about keystone:audit

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

FAQPage Schema
How do I audit a Keystone charter for stale rules and dead idioms?▼

To audit a Keystone charter for stale rules and dead idioms, run the keystone:audit skill to perform a dual-flywheel audit that checks charter health and compliance.

What is a dual-flywheel audit in charter engineering?▼

A dual-flywheel audit combines learning to capture new rules from code review with pruning to remove dead idioms and placeholders, maintaining overall charter health.

Do I need the Keystone framework to run a charter audit?▼

Yes, you need the Keystone framework installed and an existing charter, because the audit skill depends on Keystone to evaluate rules and perform the learning and pruning phases.

When should I run a charter audit after a major refactor?▼

You should run a charter audit after a major refactor or stack change, or when the dashboard's debt count feels wrong, to ensure the charter remains robust and efficient.

What categories does the automated charter pruning checklist cover?▼

The automated charter pruning checklist covers 12 categories, checking for stale rules, dead idioms, placeholders, and other compliance issues to maintain charter efficiency.