agentleFS
Sign inStart free
iansteitz1-engiansteitz1-eng/aria-skills/headless-claude/SKILL.md

headless-claude

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Run the `claude` CLI fast, with your hooks skipped, and unattended for automation — wraps `claude -p` with --setting-sources project (skip your user hooks + heavy auto-memory, ~2s not ~15s), --permission-mode bypassPermissions (no interactive approval prompt that would block a script), and a neutral cwd. Uses your own plan, no API key. Use when the user says "run claude headless", "scriptable claude", "claude -p keeps hanging / prompting", "call claude from a cron/agent", or is automating Claude Code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    --apply: run it, stream stdout. Missing claude / nonzero exit / timeout → FATAL + exit 2.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

headless-claude

The flags that make claude -p actually behave in scripts, agents, and cron.

python3 headless_claude.py "summarize CHANGES.md in 3 bullets"          # prints the command (dry)
python3 headless_claude.py --apply "summarize CHANGES.md in 3 bullets"  # runs it
python3 headless_claude.py --apply --cwd ~/proj "fix the failing test"  # in a repo

Why these flags

A bare claude -p in an automated context can hang on a permission prompt, fire your editor/notify/Stop hooks, and load your whole user memory (slow). For unattended use you almost always want:

flageffect
--setting-sources projectdon't load USER ~/.claude hooks/settings; skip auto-memory → fast, no side effects
--permission-mode bypassPermissionsno interactive approval gate — a script can't answer one
neutral --cwddon't drag in a project's CLAUDE.md / file tree

Escape hatches: --allow-hooks (keep your hooks), --safe (let it prompt). BYOK — uses your logged-in plan, no API key.

Behavior

  • Default: print the exact command (dry), exit 0.
  • --apply: run it, stream stdout. Missing claude / nonzero exit / timeout → FATAL + exit 2.

Requires

  • The claude CLI on PATH, logged in. No Python packages.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free