SkillAgentSearch skills...

cline-delegate

Delegate a coding task to the Cline coding agent CLI (`cline`) as a background implementer, then review its diff and land it yourself.

Install / Use

npx skills add amElnagdy/delegate-skills --skill cline-delegate

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Cline

Our assessment of cline-delegate

cline-delegate scores 89/100 on our quality scale, 1597th of 4,698 Development & Engineering skills we index (top 34%).

Its SKILL.md is 6.1 KB long, well organised into 18 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 2,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so cline-delegate is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the orchestrator to run the Cline relay with `--auto-approve` defaulting to `true` in act mode, which disables approval prompts for the delegated implementer agent.

AI review: risky

  • The skill instructs the orchestrator to run the Cline relay with `--auto-approve` defaulting to `true` in act mode, which disables approval prompts for the delegated implementer agent.
  • It tells the agent to execute a bundled relay script (`node "<skill-dir>/scripts/relay.mjs"`) and dispatch tasks to an external AI agent CLI, making the orchestrator drive a second agent with broad tool access.
  • While it includes review/verification steps, the default auto-approval and delegation pattern meaningfully weakens safeguards by allowing the child agent to act without per-tool user confirmation.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

cline-delegate compared with similar skills

All 4 of these similar skills score higher than cline-delegate; compare them before choosing.

SkillScoreStarsUpdatedFormat
cline-delegate (this skill)by amElnagdy892.2k57d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install cline-delegate?
Run npx skills add amElnagdy/delegate-skills --skill cline-delegate. The install tabs above show the steps for each supported agent.
Which AI agents does cline-delegate work with?
It is written for Cline, as a SKILL.md file. Other agents that read the same format can often use it too.
Is cline-delegate safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: The skill instructs the orchestrator to run the Cline relay with --auto-approve defaulting to true in act mode, which disables approval prompts for the delegated implementer agent. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is cline-delegate still maintained?
The repository was last updated about 2 months ago, so cline-delegate is actively maintained.

name: cline-delegate description: >- Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to implement/fix/refactor" - or wants to run a queue of coding tasks through Cline while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating. license: MIT compatibility: Requires the cline CLI installed and authenticated with cline auth, Node 18+, and git. The orchestrator must be able to run shell commands and read files. metadata: version: 0.5.0

Cline Delegate

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 cline CLI 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 --plan when the run must be read-only.

Prerequisites (check once)

  1. Install cline (npm or bundled binary; the relay probes cline --version).
  2. Authenticate: run cline auth (interactive sign-in), or configure ANTHROPIC_API_KEY / an OpenAI-compatible base URL.
  3. Confirm cline --version succeeds.
  4. Work in, or point --cd at, 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 through --data-dir / CLINE_SANDBOX, but the relay does not configure or override it. Plan-first for anything risky, then review the plan before a separate act-mode dispatch. Malformed or malicious briefs remain dangerous in act mode because commands run as the current user.

Authorization model

Delegation is something the human opts into. Once briefed, cline works as a tool you approved use of. The boundary is: do not accept conclusions from the self-report; verify everything on disk. For anything touching credentials, production data, or irreversible operations, stop and ask the human first instead of encoding it in a brief.

References

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryDevelopment
Updated1mo ago
Forks175

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
cline-delegate — Cline Skill: Install & Safety Check | SkillAgent