cline-delegate
Lets your agent delegate coding tasks to the Cline CLI tool when asked. The main agent keeps responsibility for reviewing and finalizing the work.
What it does
This tool lets you delegate coding tasks to another tool called `cline`. The AI writes the code, but you review and approve the changes before they are applied.
When to use it
- ✓When you want the AI to write a piece of code and you want to review it before saving.
- ✓When the coding task is well-defined and separate from the rest of the work.
- ✓When you need the AI to work on a specific project already in a code repository.
Example of what to ask your AI
“Please write a Python function that calculates the average of a list of numbers.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
You write a clear instruction (called a 'brief') describing what needs to be done. The `cline` tool executes this instruction, makes the code changes, and returns the result for you to review.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill cline-delegateOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/cline-delegate/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Cline Delegate
When to Use
- You want to delegate a bounded coding task to a separate
clineimplementer (Cline) and then review its diff yourself. - The user explicitly asked for delegation to this implementer.
You are the orchestrator. Delegate a bounded coding task to a separate implementer - the Cline coding agent CLI - then review what it produced and land it yourself. You write the brief and own the judgment; the implementer makes changes in its own session in a clean working tree; you verify and commit.
The loop needs only a shell command and file access, so any comparable orchestrator can drive it.
When NOT to use this
- The task is small enough to do inline; delegation overhead is not worth it.
- The
clineCLI is not installed or authenticated. - You require the relay to configure a sandbox. Cline exposes sandbox controls, but this relay
leaves them to the CLI environment; use
--planwhen the run must be read-only.
Prerequisites (check once)
- Install
cline(npm or bundled binary; the relay probescline --version). - Authenticate: run
cline auth(interactive sign-in), or configureANTHROPIC_API_KEY/ an OpenAI-compatible base URL. - Confirm
cline --versionsucceeds. - Work in, or point
--cdat, the target git repository.
Choose the model (optional)
Cline picks a default model. To choose another, pass the separate --model <id> or --provider <name>
(e.g. anthropic, openai-native, openrouter). The relay accepts letters, digits,
and . _ : / - only (the value reaches a shell on Windows).
The loop
Run these five steps per task. Steps 1, 4, and 5 require judgment; 2 and 3 are mechanical.
1. Write a brief
Cline sees only the text you send. It cannot read your conversation: the brief must stand alone
with the goal, current state, what to change, what to leave untouched, the project's real
gates, and a report contract. Keep each brief to a single task. Write it to a file and pass it as
the relay's --brief. See references/writing-the-brief.md.
2. Dispatch
Use the bundled relay. It runs cline --json -v, streams the brief on stdin behind a fixed
positional instruction, captures the JSON event stream, and writes result.json.
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# choose a model / provider: add --model <id> --provider <name>
# read-only planning pass: add --plan (forces --auto-approve false)
# deny approval-required tools: add --auto-approve false
# hard time limit (watchdog): add --timeout 2h (the 30m default suits brief runs; most implementation briefs should be 1-2h)
# see all options: node .../relay.mjs --help
The child's cwd pins the workspace. The relay writes artifacts under the system temp dir by default and never commits. See references/dispatch-and-poll.md.
3. Wait for completion
The relay blocks until cline finishes. Run it with the orchestrator's background-command
facility, or background it in the shell and poll for result.json. A pre-run usage error exits 2
and writes no result; a missing cline exits 127 and writes status: "cline_unavailable".
Completion means the process exited and result.json exists - trust process state and the
working tree, not the progress display. Cline's final message is the finalMessage field of
result.json.
4. Review - do not trust the self-report
- Re-run the project's gates yourself.
- Read the diff against the brief, starting with
touchedFiles. - Run relevant guard skills if installed.
See references/review-and-land.md.
5. Land it
If the work is good, commit it. The relay never commits - the diff and result.json are the
record; run git status and git diff first to confirm exactly what changed. If the group has a
PR flow, make the commit and push a branch; let human review happen. If the diff is wrong or
incomplete, re-dispatch a corrected brief in a fresh run and review again.
Autonomy and permissions
The relay explicitly passes Cline's --auto-approve, defaulting to true in act mode. Cline
plan mode can request a switch to act mode, so --plan forces --auto-approve false; the relay
rejects --plan --auto-approve true. That pair is the read-only gate. Cline also exposes sandbox
…
FAQ
What is 'cline'?
It's a command-line tool that helps write and manage code. This skill uses `cline` to do the programming work.
Do I need to install anything?
Yes, you need to have `cline` installed and set up (authenticated) on your computer. The system checks if it's ready before using it.
Does the AI save the code automatically?
No. The AI makes the changes, but you decide whether to approve and save (commit) the final code after reviewing it.
Details
Original description by the author
Delegate coding tasks to the Cline CLI (`cline`) only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.
Popularity
- GitHub stars
- 48k
- Ranking position
- #2542
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC