How do I install the Claude Code CLI skill?

Run npx skillmds add majiayu000/claude-code-cli in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude Code CLI safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude Code CLI?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude Code CLI free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude Code CLI?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude Code CLI by majiayu000 — Agent Skill

Name: Claude Code CLI
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

executing-claude

Purpose

Use this skill to perform coding, research, or automation tasks using the claude CLI. It maps requests to Claude's native permission modes to balance automation with security.

Permission Tiers

Tier	Claude Mode	Capability	Approval Required	Typical Tasks
0	`plan`	Read-only access, analysis, research.	No	Code review, audits, web research.
1	`acceptEdits`	Auto-approves file edits; prompts for shell.	Yes	Refactoring, documentation, lint fixes.
2	`bypassPermissions`	Auto-approves ALL tools (edits + shell).	Yes (High Risk)	CI/CD, complex builds, automated testing.

Implementation Workflow

1. Analyze & Classify

Analyze the user's intent to determine the required permission tier.

Tier 0 (Plan): Does the task only involve reading code or searching for information?
Tier 1 (Accept Edits): Does the task involve modifying files but no command execution?
Tier 2 (Bypass Permissions): Does the task require running tests, build scripts, or managing dependencies autonomously?

2. Approval Protocol

If the task maps to Tier 1 or Tier 2, you MUST obtain user approval before executing the claude command.

Use the AskQuestion tool to confirm:

"I've detected that this task requires [Accept Edits/Bypass Permissions] permissions to [modify files/run shell commands]. OK to proceed?"

3. Execution

Execute claude using the mode determined by the tier.

# Tier 0 (Plan)
claude -p "<prompt>" --permission-mode plan

# Tier 1 (Accept Edits)
claude -p "<prompt>" --permission-mode acceptEdits

# Tier 2 (Bypass Permissions)
claude -p "<prompt>" --permission-mode bypassPermissions

Security Rules:

NEVER use --permission-mode bypassPermissions without explicit confirmation of the risks.
ALWAYS use the most restrictive mode possible (prefer plan).
If you are unsure, default to plan and escalate only if claude reports it cannot complete the task.

Configuration

This skill leverages native claude CLI flags to enforce the permission tiers. No additional configuration files are required.

Examples

Refer to references/usage-examples.md for concrete scenarios.

---name: claude-code-clidescription: Executes tasks using the Claude Code CLI (`claude`). Automatically determines the safest permission mode (plan, acceptEdits, or bypassPermissions) based on the task type.--- # executing-claude ## Purpose Use this skill to perform coding, research, or automation tasks using the `claude` CLI. It maps requests to Claude's native permission modes to balance automation with security. ## Permission Tiers | Tier | Claude Mode | Capability | Approval Required | Typical Tasks | | :---- | :------------------ | :------------------------------------------- | :------------------ | :---------------------------------------- | | **0** | `plan` | Read-only access, analysis, research. | **No** | Code review, audits, web research. | | **1** | `acceptEdits` | Auto-approves file edits; prompts for shell. | **Yes** | Refactoring, documentation, lint fixes. | | **2** | `bypassPermissions` | Auto-approves ALL tools (edits + shell). | **Yes (High Risk)** | CI/CD, complex builds, automated testing. | ## Implementation Workflow ### 1. Analyze & Classify Analyze the user's intent to determine the required permission tier. - **Tier 0 (Plan)**: Does the task only involve reading code or searching for information? - **Tier 1 (Accept Edits)**: Does the task involve modifying files but no command execution? - **Tier 2 (Bypass Permissions)**: Does the task require running tests, build scripts, or managing dependencies autonomously? ### 2. Approval Protocol If the task maps to **Tier 1** or **Tier 2**, you **MUST** obtain user approval before executing the `claude` command. Use the `AskQuestion` tool to confirm: > "I've detected that this task requires [Accept Edits/Bypass Permissions] permissions to [modify files/run shell commands]. OK to proceed?" ### 3. Execution Execute `claude` using the mode determined by the tier. ```bash # Tier 0 (Plan) claude -p "<prompt>" --permission-mode plan # Tier 1 (Accept Edits) claude -p "<prompt>" --permission-mode acceptEdits # Tier 2 (Bypass Permissions) claude -p "<prompt>" --permission-mode bypassPermissions ``` **Security Rules:** - **NEVER** use `--permission-mode bypassPermissions` without explicit confirmation of the risks. - **ALWAYS** use the most restrictive mode possible (prefer `plan`). - If you are unsure, default to `plan` and escalate only if `claude` reports it cannot complete the task. ## Configuration This skill leverages native `claude` CLI flags to enforce the permission tiers. No additional configuration files are required. ## Examples Refer to [references/usage-examples.md](./references/usage-examples.md) for concrete scenarios.

Frequently asked questions