Audit Friction

Scan Claude Code project logs for friction patterns — repeated failures, approach loops, tool errors, misunderstanding cycles, and stuck workflows. Categorizes and counts friction events to surface what causes the most resistance. Use when user says "audit friction", "find friction", "friction audit", or "what keeps going wrong".

5 stars 1 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add TalonT-Org/AutoSkillit --skill audit-friction
Manual install
git clone --depth 1 https://github.com/TalonT-Org/AutoSkillit.git /tmp/AutoSkillit
mkdir -p ~/.claude/skills
cp -r /tmp/AutoSkillit/src/autoskillit/skills_extended/audit-friction ~/.claude/skills/audit-friction

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Friction Audit Skill

Mine Claude Code conversation logs to identify and categorize friction — repeated failures, stuck loops, tool errors, and misunderstanding cycles that cost the most effort. Surfaces patterns causing the most resistance and recommends concrete mitigations.

## When to Use

- User says "audit friction", "find friction", "friction audit", or "what keeps going wrong"
- User wants to know where workflows repeatedly stall or fail
- User wants to identify systemic tooling or workflow issues across sessions

## Arguments

The user may provide a "since" date (e.g., `2/7`, `2026-02-07`, `last month`). If not specified, use `AskUserQuestion` to ask what the earliest lookback date should be before proceeding. If the resulting window contains no logs, fall back to the last 30 days and note the adjustment.

## Critical Constraints

**NEVER:**
- Modify any source code files
- Create files outside `{{AUTOSKILLIT_TEMP}}/audit-friction/` directory
- Have subagents write files — they return all findings in response text only
- Analyze subagent log subdirectories (`*/subagents/`) — top-level session files only
- Run subagents in the background (`run_in_background: true` is prohibited)

**ALWAYS:**
- Use subagents heavily for parallel log analysis
- All output goes under `{{AUTOSKILLIT_TEMP}}/audit-friction/` (create if needed)
- Final report: `{{AUTOSKILLIT_TEMP}}/audit-friction/friction_audit_{YYYY-MM-DD_HHMMSS}.md`
Read the full skill on GitHub

Details

Skill name
audit-friction
Path
src/autoskillit/skills_extended/audit-friction/SKILL.md
License
MIT
Repo updated
8 November 2026

FAQ

What does the Audit Friction skill do?

Scan Claude Code project logs for friction patterns — repeated failures, approach loops, tool errors, misunderstanding cycles, and stuck workflows. Categorizes and counts friction events to surface what causes the most resistance. Use when user says "audit friction", "find friction", "friction audit", or "what keeps going wrong".

How do I install the Audit Friction skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add TalonT-Org/AutoSkillit --skill audit-friction. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Audit Friction popular?

It lives in TalonT-Org/AutoSkillit, which has 5 GitHub stars and 1 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.