← DotfileCONTENT HISTORY

Update to Dotfile

Snapshot Nov 2, 2026 · 18:12 UTC · version 2026.10.301142

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Dotfile and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "What stands between your cases and automatic approval, and what to automate next",
  "included_files": [],
  "name": "automation-audit",
  "skill_md_contents": "---\nname: automation-audit\ndescription: 'What stands between your cases and automatic approval, and what to automate next'\nmetadata:\n  title: 'Automation Audit'\n  category: audits\n  order: '24'\n  plugin: 'true'\n---\n\n1. STRAIGHT-THROUGH RATE: share of cases decided with no human action at all, overall and per template. This is the headline and it goes first. 2. WHAT BLOCKS AUTO-APPROVAL, ranked by cases held: controls requiring manual completion, check types that never auto-approve, template rules forcing review, and cases that met every criterion but were not auto-approved for a configuration detail. Name the specific control or rule, not the category. 3. DEAD CONFIGURATION: controls defined and never completed, rules that never fire, rules that fire on almost everything. All three block or bloat approval without adding assurance. 4. HUMAN ACTIONS PER CASE: the distribution, and the most frequent repeated action sequences across cases. Where the same three or four actions recur on most cases, name that sequence — it is a routine waiting to be written. 5. AVOIDABLE REWORK: work redone rather than done — hits dismissed that an AI already judged, checks created then deleted, the same document requested twice. Quantify each. 6. AUTOMATION BACKLOG: rank candidates by the human actions they would remove, and say whether the platform can already do it. Close with the three changes that would move the straight-through rate most, each with the cases affected. Be honest when a blocker is a deliberate compliance choice — never recommend removing a control that exists for a reason.\n"
}

SHA-256 of public snapshot: 0302d0d5e7a6da1b374afa3c66182b5bbf53d1030202d06e539372618316bf9e