Agent skill · AI & Agents

headless-cli-agents

This skill provides comprehensive guidance for running AI coding agents in non-interactive (headless) mode for automation, CI/CD pipelines, and scripting. Use when integrating Claude Code, Codex, Gemini, OpenCode, Qwen, or Droid CLI into automated workflows where human interaction is not desired.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill headless-master-skill-alchimie-di-circe-extractor-desktop-ap --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/agent/headless-master-skill-alchimie-di-circe-extractor-desktop-ap/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Headless CLI Agents ## Overview This skill enables the use of AI coding agents in non-interactive mode for automation scenarios. It provides command references, safety considerations, and practical examples for integrating AI agents into automated workflows. ## Quick Reference | Agent | Basic Command | Automation Flag | Best For | |-------|--------------|----------------|----------| | Claude Code | `claude -p "prompt"` | Auto-approved by default | General coding tasks | | OpenAI Codex | `codex exec "prompt"` | `--full-auto` | Complex refactoring | | Google Gemini | `gemini -p "prompt"` | `--yolo` (if available) | Analysis tasks | | OpenCode | `opencode -p "prompt"` | Auto-approved by default | Multi-provider support | | Qwen Code | `qwen -p "prompt"` | `--yolo` | Local model support | | Factory Droid | `droid exec "prompt"` | `--auto <level>` | Controlled automation | ## When to Use Headless Mode ## Core Concepts ### 1. Agent Selection Choose the appropriate agent based on your requirements: **Claude Code CLI** - Best for general-purpose coding with excellent code understanding ```bash # Basic usage claude -p "Review this code for security issues" # With additional context claude

What's inside
Steps it walks through
  1. Overview
  2. Quick Reference
  3. When to Use Headless Mode
  4. Core Concepts
  5. 1. Agent Selection
  6. 2. Safety and Autonomy Levels
  7. 3. Input/Output Patterns
  8. Common Workflows
  9. Code Review Automation
  10. Test Generation
  11. Documentation Automation
  12. Integration Patterns
  13. CI/CD Integration
  14. Pre-commit Hooks
Ships with 1 file
  • metadata.json
Commands it runs
Basic usage
claude -p "Review this code for security issues"
With additional context
claude -p "Generate tests for authentication module" --add-dir ./tests
Automated refactoring
codex exec --full-auto "Refactor this module to use async/await"
Outside git repos
codex exec --skip-git-repo-check --full-auto "Create API documentation"
Analysis with structured output
gemini -p "Analyze codebase architecture" --output-format json
More from claude-skill-registry
All skills →
About this skill
What does the headless-cli-agents skill do?

This skill provides comprehensive guidance for running AI coding agents in non-interactive (headless) mode for automation, CI/CD pipelines, and scripting. Use when integrating Claude Code, Codex, Gemini, OpenCode, Qwen, or Droid CLI into automated workflows where human interaction is not desired.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill headless-master-skill-alchimie-di-circe-extractor-desktop-ap --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going