claude-skill
Skill248 starsChanged 4 months agoMITView on GitHub
Delegate a task to the Claude Code CLI, typically a headless `claude -p` run. Use when the user wants the work executed through Claude Code rather than answered inline.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- YahyaLendani/opus-tuner-claude-skilltheir own version, first seen Nov 1, 2026
- myysophia/codex-configtheir own version, first seen Oct 8, 2026
- accelizero/claude-skilltheir own version, first seen Mar 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- myysophia/codex-config★ 195same name
- YahyaLendani/opus-tuner-claude-skill★ 14same name
- accelizero/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- brainstormingSkill
- code-simplifierSkill
- deep-researchSkill
- github-fix-issueSkill
- github-review-prSkill
- gpt-image-skillSkill
- grill-meSkill
- handoffSkill
- minimax-image-skillSkill
- nanobanana-skillSkill
- youtube-transcribe-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 26
Before execution, confirm the CLI is available and authenticated.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Claude Code Headless Mode
Build and run claude commands for work that should be executed through Claude Code itself.
| Reference | Read it when |
| references/flags-and-permissions.md | The command needs more than -p — permission modes, tool scoping, output formats, flag inventory, installation |
| references/examples.md | You want a worked command for a specific shape of task (read-only analysis, safe edit run, JSON report, resume, MCP, sandboxed unattended run) |
Requires the claude CLI installed and authenticated on the target machine.
Core rules
claude --helpon the target machine is the compatibility floor. CLI flags and permission-rule syntax move faster than docs and copied examples, and they differ between builds. Verify any uncommon flag there before emitting it.- Do not add
--modelunless the user asked for an override or the workflow must pin a model for reproducibility. The user's configured model is the right default. - Prefer
--append-system-promptover--system-promptunless replacing Claude Code's default behavior is the point. - Choose the least-permissive mode that still fits the task.
acceptEditsis the usual starting point for coding automation. For a truly unattended run, reach for explicit permission rules ordontAskfirst;bypassPermissionsis only for an already-isolated environment.
Check what the task needs
Before execution, confirm the CLI is available and authenticated. Consult claude --help for flags needed by this command; use version or diagnostic commands when compatibility or installation is in doubt. A request for a command example does not authorize running that task.
Basic shape
claude -p "summarize the repository architecture"
claude -p "review the auth layer for risks" --output-format jsonEverything else is a matter of scoping tools and permissions around that — see the references.
When to pause
Pause for missing credentials, unavailable required capabilities, or a permission expansion. If an equivalent supported command stays within the request, use it without adding an approval step.
What to return
For execution requests, run the authorized command and inspect its result and relevant artifacts; do not stop at printing a command or treat exit code zero as proof that the requested work is complete. Continue bounded follow-up within the existing scope when work remains. For command-only requests, return the command without executing it.
Report the command, outcome, relevant checks, and any permission or validation gaps. Include a resume command only when the workflow is meant to continue later.
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
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.