Change how visibly Claude surfaces analytical work during L3+ analyses.

MITAuto-check passedAgent Workflows

Install Pace

skills CLI
$ npx skills add ai-analyst-lab/ai-analyst --skill pace -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ai-analyst-lab/ai-analyst pace --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pace .claude/skills/pace && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pace
GitHub stars
304
Token cost
~1.4k tokens
SKILL.md length
512 words
Files
1
Skills in repo
43
Repo updated
First seen
Licence
MIT

At a glance

Change how visibly Claude surfaces analytical work during L3+ analyses.

  • Works in 6 steps: Resolve the target mode. If the argument… → Validate. If the argument is anything… → Read existing state. Load… → …
  • The user invokes /pace
  • SKILL.md covers Purpose, Modes, Invocation and Behavior, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pace is an agent skill from ai-analyst-lab/ai-analyst. Change how visibly Claude surfaces analytical work during L3+ analyses. Three modes — guided (announce each phase and pause for /continue), narrated (announce each phase and run end-to-end), autopilot (silent end-to-end, final output only). Use this skill whenever the user invokes /pace, /pace guided, /pace narrated, /pace autopilot, or says things like "slow down and walk me through", "pause between steps", "just run it silently", "narrate each step", "don't stop to ask me", "stop narrating". Pace is orthogonal…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Session handoff and End-to-end testing. The repository describes itself as: AI Product Analyst — Claude Code-powered data analysis toolkit. The licence is MIT.

When your agent uses it

  • The user invokes /pace
  • /pace autopilot
  • Says things like slow down and walk me through
  • Pause between steps

Example prompts

  • “slow down and walk me through”
  • “pause between steps”
  • “just run it silently”
  • “/pace”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the target mode. If the argument is one of guided|narrated|autopilot,
  2. Validate. If the argument is anything else, echo the three valid modes
  3. Read existing state. Load working/session_state.yaml if it exists;
  4. Write atomically. Write the updated YAML to
  5. Confirm to the user. One line
  6. Apply on next phase boundary. If an analysis is already in flight, the

What it can do on your machine

Read from SKILL.md and the folder at commit 52c0744. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pace loads about 1.4k tokens when it runs. Until then it costs about 212 tokens; SKILL.md has 512 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~212
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ai-analyst-lab/ai-analyst at commit 52c0744, republished under its MIT licence (© ai-analyst-lab). 512 words, ~1,373 tokens.

Download SKILL.mdSave it as .claude/skills/pace/SKILL.md (or your agent's skills folder).
name
pace
description
Change how visibly Claude surfaces analytical work during L3+ analyses. Three modes — guided (announce each phase and pause for /continue), narrated (announce each phase and run end-to-end), autopilot (silent end-to-end, final output only). Use this skill whenever the user invokes `/pace`, `/pace guided`, `/pace narrated`, `/pace autopilot`, or says things like "slow down and walk me through", "pause between steps", "just run it silently", "narrate each step", "don't stop to ask me", "stop narrating". Pace is orthogonal to complexity level — it changes surfacing, not which agents run. Full spec and phase-banner format live in the question-router skill. This skill is the write-side: it persists the user's explicit pace choice to `working/session_state.yaml` so it survives across phases, across `/resume-pipeline`, and across sessions.

Skill: Pace

Purpose

Persist the user's explicit choice of pace mode — how visibly the analytical machinery surfaces during L3+ analyses. Pace is orthogonal to complexity level (L1–L5). Level decides which agents run; pace decides how visible the work is.

Modes

ModeBehavior
guidedAnnounce each phase, run it, pause and wait for /continue before the next phase
narratedAnnounce each phase, run it, announce the result, continue to the next phase without pausing (the safe default)
autopilotSilent end-to-end. No phase banners. The final message is the user's first look at the work: open with the outcome, then findings, then what is next, written for a reader who saw none of the run.

Invocation

The user types one of:

  • /pace guided
  • /pace narrated
  • /pace autopilot
  • /pace (no argument) — show the current mode and the three options
  • Natural language: "slow down, pause between steps" → guided; "just run it silently" → autopilot; "narrate but don't stop" → narrated

Behavior

  1. Resolve the target mode. If the argument is one of guided|narrated|autopilot, use it. If no argument, print the current mode (read from working/session_state.yaml → pace_mode) and the three options. Stop.
  2. Validate. If the argument is anything else, echo the three valid modes and ask which one the user wants. Do NOT guess or silently fall back.
  3. Read existing state. Load working/session_state.yaml if it exists; otherwise start with an empty dict. Preserve every other key.
  4. Write atomically. Write the updated YAML to working/session_state.yaml.tmp, then rename to working/session_state.yaml. This prevents corruption if the process is interrupted mid-write.
  5. Confirm to the user. One line:
    • guided → "Pace set to guided. I'll pause after each phase and wait for /continue."
    • narrated → "Pace set to narrated. I'll announce each phase and run end-to-end."
    • autopilot → "Pace set to autopilot. I'll run silently and show you the final output."
  6. Apply on next phase boundary. If an analysis is already in flight, the new mode takes effect starting with the next phase. Tell the user so. Never switch mid-phase — it produces inconsistent banner state.
Show full SKILL.md (177 more words)Show less

Failure Handling

  • Write fails (permissions, disk full, working/ missing): honor the mode in the current session in memory and warn: "Pace set to {mode} for this session, but I couldn't write working/session_state.yaml ({reason}). Run /pace {mode} again after resume to restore it."
  • YAML parse fails on existing file: back up the broken file to working/session_state.yaml.broken-{timestamp}, write a fresh one with just pace_mode, and tell the user. Never overwrite without backing up.
  • No working/ directory: create it (mkdir -p working), then proceed.

Implementation

Use Python for atomic write and YAML safety. Keep it minimal:

python
import yaml, os, pathlib, datetime

STATE_PATH = pathlib.Path("working/session_state.yaml")

def set_pace(mode: str) -> tuple[bool, str]:
    assert mode in {"guided", "narrated", "autopilot"}
    STATE_PATH.parent.mkdir(parents=True, exist_ok=True)

    state = {}
    if STATE_PATH.exists():
        try:
            state = yaml.safe_load(STATE_PATH.read_text()) or {}
        except yaml.YAMLError:
            bak = STATE_PATH.with_suffix(
                f".yaml.broken-{datetime.datetime.now().strftime('%Y%m%dT%H%M%S')}"
            )
            STATE_PATH.rename(bak)
            state = {}

    state["pace_mode"] = mode
    tmp = STATE_PATH.with_suffix(".yaml.tmp")
    try:
        tmp.write_text(yaml.safe_dump(state, sort_keys=False))
        os.replace(tmp, STATE_PATH)
        return True, ""
    except OSError as e:
        return False, str(e)

Edge Cases

  • Mid-phase invocation: honor at next phase boundary, not immediately. Tell the user.
  • No L3+ analysis running: still persist the mode. It applies to the next one.
  • User types /pace during a guided pause: show current mode + options, do not consume the pause.
  • working/session_state.yaml already has other keys (from session-handoff, resume-pipeline): preserve them all; only touch pace_mode.

See Also

  • Full pace-mode spec and auto-detection rules: .claude/skills/question-router/SKILL.md → "Step 3.5: Pace Mode Selection" and "Phase Banner Format".
  • Session state schema and other persisted keys: .claude/skills/session-handoff/SKILL.md.

© ai-analyst-lab, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/pace of ai-analyst-lab/ai-analyst.

Open the folder on GitHubat commit 52c0744

Compare with similar skills

Pace next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pace compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pace this skillai-analyst-lab/ai-analyst304—~1.4kAutomated safety check: PassMIT
V2 Model Supportmirage-project/mirage2.5k—~5.3kAutomated safety check: PassApache-2.0
Absolute Workmaddhruv/absolute218—~5.3kAutomated safety check: PassMIT
Edt MCP New ToolDitriXNew/EDT-MCP295—~2.1kAutomated safety check: PassAGPL-3.0
Sebastian ThrunK-Dense-AI/mimeo282—~1.7kAutomated safety check: PassMIT
Ship Featuretheexperiencecompany/gaia308—~2.7kAutomated safety check: NotesCustom licence

Similar skills

  • V2 Model Support

    mirage-project/mirage

    End-to-end pipeline for adding or porting a model to MPK Runtime-V2 — from a compute-graph spec (shapes + draw.io graph + HF checkpoint + TP/EP plan) to a working multi-GPU demo.

    2.5k GitHub stars~5.3k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed
  • Absolute Work

    maddhruv/absolute

    End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge.

    218 GitHub stars~5.3k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Edt MCP New Tool

    DitriXNew/EDT-MCP

    Canonical, battle-tested checklist for adding a new MCP tool to the EDT-MCP plugin the right way — the IMcpTool surface, shared resolvers, schema, registration, MANIFEST, the two MANDATORY test…

    295 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Sebastian Thrun

    K-Dense-AI/mimeo

    Applies the reasoning, principles, and mental models of Sebastian Thrun (robotics and self-driving cars pioneer, founder of Google X, Waymo, Udacity, Stanford University).

    282 GitHub stars~1.7k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Ship Feature

    theexperiencecompany/gaia

    Autonomously ship a feature end-to-end with zero human intervention: plan it, implement it, review it with a team of subagents, boot the full stack, drive it in a real browser like a user…

    308 GitHub stars~2.7k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Build Feature End To End

    FerroxLabs/wayland

    Orchestrates the full software feature development lifecycle from specification through production deployment, chaining five engineering skills into a cohesive build pipeline.

    608 GitHub stars~4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from ai-analyst-lab/ai-analyst

All 43 skills in this repo
  • Always Compare

    ai-analyst-lab/ai-analyst

    Never present a metric or number in isolation; anchor every number to a comparison (prior period, benchmark, or another segment) or state that none is available.

    304 GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check passed
  • Archaeology

    ai-analyst-lab/ai-analyst

    Retrieve proven SQL patterns, table cheatsheets, and join patterns from .knowledge/query-archaeology/ so past work gets reused.

    304 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Archive Analysis

    ai-analyst-lab/ai-analyst

    Save completed analyses to the knowledge system's analysis archive for future reference.

    304 GitHub stars~2.7k tokensUpdated 7 days ago
    Auto-check passed
  • Auth Preflight

    ai-analyst-lab/ai-analyst

    Verify Google Workspace MCP authentication at the start of any session that needs Google APIs (Docs, Slides, Drive).

    304 GitHub stars~3.1k tokensUpdated 7 days ago
    Auto-check passed
  • Causal

    ai-analyst-lab/ai-analyst

    Causal inference toolkit for when experiments are not possible: estimate treatment effects from observational data with assumption checks and mandatory caveats.

    304 GitHub stars~1.8k tokensUpdated 7 days ago
    Auto-check passed
  • Chart To Drive

    ai-analyst-lab/ai-analyst

    Standardized workflow for uploading local chart PNGs to Google Drive and making them available for insertion into Google Docs and Slides.

    304 GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check passed

Questions about Pace

What does Pace do?

Change how visibly Claude surfaces analytical work during L3+ analyses. Pace is an agent skill from ai-analyst-lab/ai-analyst. Change how visibly Claude surfaces analytical work during L3+ analyses.

When should I use Pace?

Pace fits situations like: the user invokes /pace; /pace autopilot; says things like slow down and walk me through; pause between steps.

How do I install Pace in Claude Code?

Run `npx skills add ai-analyst-lab/ai-analyst --skill pace -a claude-code`. Or copy the skill folder (.claude/skills/pace in ai-analyst-lab/ai-analyst) into .claude/skills/pace in your project. Claude Code loads it when a task matches its description.

How do I install Pace in Codex?

Run `npx skills add ai-analyst-lab/ai-analyst --skill pace -a codex`. Or copy the skill folder (.claude/skills/pace in ai-analyst-lab/ai-analyst) into .agents/skills/pace in your project. Codex loads it when a task matches its description.

Can I use Pace in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ai-analyst-lab/ai-analyst --skill pace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pace, .gemini/skills/pace, .github/skills/pace and .opencode/skills/pace in your project.

What does Pace need to run?

SKILL.md names no scripts, command-line tools or credentials: Pace is instructions for the agent only. Our summary lists: Python 3.

Does Pace access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pace safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pace use?

Pace is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pace use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pace?

Skills that share tags, products or a category with Pace: V2 Model Support (mirage-project/mirage, 2.5k stars), Absolute Work (maddhruv/absolute, 218 stars), Edt MCP New Tool (DitriXNew/EDT-MCP, 295 stars) and Sebastian Thrun (K-Dense-AI/mimeo, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pace?

ai-analyst-lab (a GitHub organization) maintains it in ai-analyst-lab/ai-analyst, which has 304 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on September 30, 2026.

Source: ai-analyst-lab/ai-analyst on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.