Agent skill

Squid Implement Night

Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR.

Apache-2.0Auto-check passed

Install Squid Implement Night

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/squid-implement-night .claude/skills/squid-implement-night && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .claude/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/squid-implement-night .agents/skills/squid-implement-night && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .agents/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/squid-implement-night .cursor/skills/squid-implement-night && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .cursor/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iusztinpaul/squid.git --path skills/squid-implement-night

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/squid-implement-night .gemini/skills/squid-implement-night && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .gemini/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/squid-implement-night .github/skills/squid-implement-night && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .github/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iusztinpaul/squid --skill squid-implement-night -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iusztinpaul/squid squid-implement-night --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iusztinpaul/squid.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/squid-implement-night .opencode/skills/squid-implement-night && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "squid-implement-night" agent skill from https://github.com/iusztinpaul/squid/tree/main/skills/squid-implement-night into .opencode/skills/squid-implement-night/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "squid-implement-night", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: squid-implement-night
GitHub stars: 203
Token cost: ~1.2k tokens
SKILL.md length: 523 words
Files: 1
Skills in repo: 13
Repo updated: Sep 3, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR.

Works in 4 steps: Locate the branch worktree + tasks → Build the whole plan → Review (loop until clean) → …
After /squid-plan
SKILL.md covers Step 0 — Locate the branch…, Step 1 — Build the whole plan, Step 2 — Review (loop until… and Step 3 — Review CI, plus 2 more sections
Calls git

What it does

Squid Implement Night is an agent skill from iusztinpaul/squid. Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is Apache-2.0.

When your agent uses it

After /squid-plan
Tasks that involve End-to-end testing

Example prompts

“/squid-implement-night”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Locate the branch worktree + tasks
Build the whole plan
Review (loop until clean)
Review CI

What it can do on your machine

Read from SKILL.md and the folder at commit f5bf6b3. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Squid Implement Night loads about 1.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 523 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~55
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iusztinpaul/squid at commit f5bf6b3, republished under its Apache-2.0 licence (© iusztinpaul). 523 words, ~1,231 tokens.

Download SKILL.mdSave it as .claude/skills/squid-implement-night/SKILL.md (or your agent's skills folder).

name: squid-implement-night
description: Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Trigger after /squid-plan.
argument-hint: <plan-ref | feature-slug>

Implement Night — end-to-end feature pipeline (thin orchestrator)

Build an already-approved feature plan all the way to a validated, ready-to-merge PR. This skill is a thin orchestrator: the real work lives in the sub-skills it invokes — /squid-implement-task, /squid-review, /squid-review-ci — plus the agents those skills launch.

$ARGUMENTS is the approved Tasks Plan reference (path or feature slug) produced by /squid-plan. If empty, ask the human which plan to build (and remind them to run /squid-plan first if none exists).

You are the orchestrator — a MANAGER. You sequence the sub-skills, route rollback tasks, and enforce the gates. You do NOT write code, review the diff, or run tests yourself.

Read AGENTS.md first (tracker mode, the pipeline map, and the cross-cutting rules). Retry caps live in each sub-skill.

Input: an approved Tasks Plan + the feature branch/worktree /squid-plan created. Output: a CI-validated feature PR, ready for the human to squash-merge.

The pipeline blocks on the human only at the very end (squash-merge). (Plan approval already happened in /squid-plan.) Everything between is automated; failures route back into /squid-implement-task as rollup tasks rather than stopping the pipeline. Caps stop the pipeline: Tester FAIL 5/task, PA REJECT 3, PR-Reviewer 3, On-Call 5 — when a cap fires, surface USER ACTION REQUIRED and stop.

Critical rules:

Never rubber-stamp a sub-skill's result. When /squid-review reports "no blockers" or /squid-review-ci reports "green", confirm the evidence is real before advancing.
By name, never by path. Invoke /squid-implement-task, /squid-review, /squid-review-ci by their skill names so it works when installed as a plugin.

Step 0 — Locate the branch worktree + tasks

/squid-plan created the feature branch feat/{slug} — either in a dedicated worktree at ../{repo}-{slug} or in the current working tree — and wrote the feature's task files (tasks/<NNN>-*.md, status: pending) on it. Find where that branch is checked out:

bash

git worktree list          # find the working tree whose branch is feat/{slug}

Confirm that working tree exists and contains pending task files (tasks/<NNN>-*.md with status: pending); WORKTREE_PATH is its path (the dedicated worktree, or the repo root if the branch lives in the current tree). If there's no matching branch or no pending tasks, stop and tell the human to run /squid-plan first. Pass Working directory: {WORKTREE_PATH} to every sub-skill / agent so all work happens there.

Show full SKILL.md (167 more words)Show less

Step 1 — Build the whole plan

Invoke /squid-implement-task once with the feature's pending tasks. It loops over every task — SWE → Tester → commit on PASS → next. (Do NOT loop here yourself; the per-task iteration lives inside /squid-implement-task.)

invoke /squid-implement-task with: the feature's pending tasks (tasks/<NNN>-*.md, status: pending), Working directory: {WORKTREE_PATH}

Step 2 — Review (loop until clean)

invoke /squid-review with: feature {title}, Working directory: {WORKTREE_PATH}

/squid-review pushes, creates/updates the PR, and runs PA acceptance then PR-Reviewer.

Returns "clean" (no blockers) → proceed to Step 3.
Returns a rollup task (PA REJECT or PR-Reviewer Blockers) → invoke /squid-implement-task on that one rollup task (it builds + commits the fix), then re-invoke /squid-review. Repeat.

Step 3 — Review CI

invoke /squid-review-ci with: PR #{N}, Working directory: {WORKTREE_PATH}

/squid-review-ci watches CI and drives it green (On-Call diagnoses → SWE fixes → re-check).

CI green → the PR is validated and ready to merge. Proceed to the tail.

Tail — hand-off

The validated PR is ready. The orchestrator does NOT squash — per-task commits stay on the branch; the human uses GitHub's "Squash and merge".

Report the final summary:

markdown

## /squid-implement-night complete — {Feature title}

**PR:** {URL} (validated; ready to squash-merge)
**Branch:** feat/{slug} ({N} per-task commits)
**Worktree:** {WORKTREE_PATH}

**Tasks delivered ({N}):** {table — Tester / PA accept / PR-Reviewer / CI}
**Rollup tasks ({M}):** {list, or "none"}

Next: review the PR, then GitHub's **Squash and merge**. Remove the worktree with `git worktree remove {WORKTREE_PATH}` after merge.

/squid-implement-night ends here.

Notes on shape

/squid-review-ci handles its own CI fixes internally and does not re-enter /squid-review.
Don't add mid-pipeline gates.

Files

Just SKILL.md in skills/squid-implement-night of iusztinpaul/squid.

Open the folder on GitHubat commit f5bf6b3

Compare with similar skills

Squid Implement Night next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Squid Implement Night compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Squid Implement Night this skilliusztinpaul/squid	203	—	~1.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Web Application Testinganthropics/skills	180k	51 repos	~966	Automated safety check: Pass	Apache-2.0	3 days ago
Electron App Automationvercel-labs/agent-browser	44k	5 repos	~1.7k	Automated safety check: Pass	Apache-2.0	today
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
playwright-cli Browser Automationgithub/gh-aw	5.4k	24 repos	~2.8k	Automated safety check: Pass	MIT	today
Write and Verify Playwright Testsappsmithorg/appsmith	41k	—	~2.9k	Automated safety check: Notes	Apache-2.0	today

Similar skills

Web Application Testing
anthropics/skills
Official
Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.
180k GitHub starsUsed in 51 repos~966 tokens
Testing & QAAuto-check passed
Electron App Automation
vercel-labs/agent-browser
Official
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
44k GitHub starsUsed in 5 repos~1.7k tokens
Productivity & AutomationAuto-check passed
OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
playwright-cli Browser Automation
github/gh-aw
Official
Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.
5.4k GitHub starsUsed in 24 repos~2.8k tokens
Testing & QAAuto-check passed
Write and Verify Playwright Tests
appsmithorg/appsmith
Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.
41k GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check: notes
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
158k GitHub stars~682 tokensUpdated today
Testing & QAAuto-check passed

More from iusztinpaul/squid

All 13 skills in this repo

Squid Implement Task
iusztinpaul/squid
Implement one task — or a whole list / an approved Tasks Plan — via the inner SWE↔Tester loop, committing each task on PASS.
203 GitHub stars~1.3k tokensUpdated 1 mo ago
Auto-check passed
Squid Review
iusztinpaul/squid
Push the committed feature branch, create or update its PR, then run Product Architect acceptance and PR-Reviewer on it.
203 GitHub stars~873 tokensUpdated 1 mo ago
Auto-check passed
Squid Review CI
iusztinpaul/squid
Drive CI green on a pushed, review-clean feature PR — On-Call diagnoses failures and hands fix tasks to the SWE.
203 GitHub stars~607 tokensUpdated 1 mo ago
Auto-check passed
Squid Testing Python
iusztinpaul/squid
Write and evaluate effective Python tests using pytest. An agent skill from iusztinpaul/squid.
203 GitHub stars~1.3k tokensUpdated 1 mo ago
Auto-check passed
Squid Architecture Review
iusztinpaul/squid
Periodic architectural sweep — reads existing ADRs, maps modules/dependencies/layering, and reports up to 10 prioritised findings shaped as refactor proposals /squid-refactor can consume directly.
203 GitHub stars~2.6k tokensUpdated 1 mo ago
Auto-check passed
Squid Clean Harness
iusztinpaul/squid
Shrink an agent harness (.agents/ skills + resources) to the minimum tokens that keep the exact same logic.
203 GitHub stars~1.9k tokensUpdated 1 mo ago
Auto-check passed

Questions about Squid Implement Night

What does Squid Implement Night do?

Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR. Squid Implement Night is an agent skill from iusztinpaul/squid. Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR.

When should I use Squid Implement Night?

Squid Implement Night fits situations like: after /squid-plan; tasks that involve End-to-end testing.

How do I install Squid Implement Night in Claude Code?

Run `npx skills add iusztinpaul/squid --skill squid-implement-night -a claude-code`. Or copy the skill folder (skills/squid-implement-night in iusztinpaul/squid) into .claude/skills/squid-implement-night in your project. Claude Code loads it when a task matches its description.

How do I install Squid Implement Night in Codex?

Run `npx skills add iusztinpaul/squid --skill squid-implement-night -a codex`. Or copy the skill folder (skills/squid-implement-night in iusztinpaul/squid) into .agents/skills/squid-implement-night in your project. Codex loads it when a task matches its description.

Can I use Squid Implement Night in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iusztinpaul/squid --skill squid-implement-night -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/squid-implement-night, .gemini/skills/squid-implement-night, .github/skills/squid-implement-night and .opencode/skills/squid-implement-night in your project.

What does Squid Implement Night need to run?

Going by SKILL.md and its folder, Squid Implement Night needs the command-line tools its instructions call (git).

Does Squid Implement Night access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Squid Implement Night safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Squid Implement Night use?

Squid Implement Night is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Squid Implement Night use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Squid Implement Night?

Skills that share tags, products or a category with Squid Implement Night: Web Application Testing (anthropics/skills, 180k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars) and playwright-cli Browser Automation (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Squid Implement Night?

iusztinpaul (a GitHub user) maintains it in iusztinpaul/squid, which has 203 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 3, 2026.

Source: iusztinpaul/squid on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Squid Implement Night

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Implement Night — end-to-end feature pipeline (thin orchestrator)

Step 0 — Locate the branch worktree + tasks

Step 1 — Build the whole plan

Step 2 — Review (loop until clean)

Step 3 — Review CI

Tail — hand-off

Notes on shape

Files

Compare with similar skills

Similar skills

More from iusztinpaul/squid

Questions about Squid Implement Night