Agent skill

Completion Check

by parcadei in parcadei/Continuous-Claude-v3

Completion Check: Verify Infrastructure Is Wired. An agent skill from parcadei/Continuous-Claude-v3.

MITAuto-check passed

Install Completion Check

skills CLI

$ npx skills add parcadei/Continuous-Claude-v3 --skill completion-check -a claude-code

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

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 completion-check --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/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/completion-check .claude/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .claude/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check

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 parcadei/Continuous-Claude-v3 --skill completion-check -a codex

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

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 completion-check --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/completion-check .agents/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .agents/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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 parcadei/Continuous-Claude-v3 --skill completion-check -a cursor

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

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 completion-check --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/completion-check .cursor/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .cursor/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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/parcadei/Continuous-Claude-v3.git --path .claude/skills/completion-check

--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 parcadei/Continuous-Claude-v3 --skill completion-check -a gemini-cli

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

GitHub CLI

$ gh skill install parcadei/Continuous-Claude-v3 completion-check --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/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/completion-check .gemini/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .gemini/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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 parcadei/Continuous-Claude-v3 completion-check

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 parcadei/Continuous-Claude-v3 --skill completion-check -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/completion-check .github/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .github/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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 parcadei/Continuous-Claude-v3 --skill completion-check -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 parcadei/Continuous-Claude-v3 completion-check --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/completion-check .opencode/skills/completion-check && 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 "completion-check" agent skill from https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/completion-check into .opencode/skills/completion-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "completion-check", 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: completion-check
GitHub stars: 3.9k
Used in: 1 other repo
Token cost: ~733 tokens
SKILL.md length: 212 words
Files: 1
Skills in repo: 141
Repo updated: Jan 26, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Completion Check: Verify Infrastructure Is Wired. An agent skill from parcadei/Continuous-Claude-v3.

Works in 5 steps: Trace the execution path - Follow from… → Check hooks are registered, not just… → Verify database connections - Ensure… → …
SKILL.md covers Pattern, DO, DON'T and Completion Checklist, plus 2 more sections
Calls uv

What it does

Completion Check is an agent skill from parcadei/Continuous-Claude-v3. Completion Check: Verify Infrastructure Is Wired

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

The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.

Example prompts

“/completion-check”

Requirements

Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Trace the execution path - Follow from user intent to actual code execution
Check hooks are registered, not just implemented
Verify database connections - Ensure infrastructure uses the right backend
Test end-to-end - Run the feature and verify infrastructure is invoked
Search for orphaned implementations

What it can do on your machine

Read from SKILL.md and the folder at commit d07ff4b. 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:
- uv
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use uv, 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

Completion Check loads about 733 tokens when it runs. Until then it costs about 16 tokens; SKILL.md has 212 words of instructions outside code blocks.

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

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 parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 212 words, ~733 tokens.

Download SKILL.mdSave it as .claude/skills/completion-check/SKILL.md (or your agent's skills folder).

name: completion-check
description: Completion Check: Verify Infrastructure Is Wired
user-invocable: false

Completion Check: Verify Infrastructure Is Wired

When building infrastructure, verify it's actually connected to the system before marking as complete.

Pattern

Infrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.

DO

Trace the execution path - Follow from user intent to actual code execution:

bash

# Example: Verify Task tool spawns correctly
grep -r "claude -p" src/
grep -r "Task(" src/

Check hooks are registered, not just implemented:

bash

# Hook exists?
ls -la .claude/hooks/my-hook.sh

# Hook registered in settings?
grep "my-hook" .claude/settings.json

Verify database connections - Ensure infrastructure uses the right backend:

bash

# Check connection strings
grep -r "postgresql://" src/
grep -r "sqlite:" src/  # Should NOT find if PostgreSQL expected

Test end-to-end - Run the feature and verify infrastructure is invoked:

bash

# Add debug logging
echo "DEBUG: DAG spawn invoked" >> /tmp/debug.log

# Trigger feature
uv run python -m my_feature

# Verify infrastructure was called
cat /tmp/debug.log

Search for orphaned implementations:

bash

# Find functions defined but never called
ast-grep --pattern 'async function $NAME() { $$$ }' | \
  xargs -I {} grep -r "{}" src/

DON'T

Mark infrastructure "complete" without testing execution path
Assume code is wired just because it exists
Build parallel systems (Task tool vs claude -p spawn)
Use wrong backends (SQLite when PostgreSQL is architected)
Skip end-to-end testing ("it compiles" ≠ "it runs")

Completion Checklist

Before declaring infrastructure complete:

Traced execution path from entry point to infrastructure
Verified hooks are registered in .claude/settings.json
Confirmed correct database/backend in use
Ran end-to-end test showing infrastructure invoked
Searched for dead code or parallel implementations
Checked configuration files match implementation

Example: DAG Task Graph

Wrong approach:

✓ Built BeadsTaskGraph class
✓ Implemented DAG dependencies
✓ Added spawn logic
✗ Never wired - Task tool still runs instead
✗ Used SQLite instead of PostgreSQL

Right approach:

✓ Built BeadsTaskGraph class
✓ Wired into Task tool execution path
✓ Verified claude -p spawn is called
✓ Confirmed PostgreSQL backend in use
✓ Tested: user calls Task() → DAG spawns → beads execute
✓ No parallel implementations found

Source Sessions

This session: Architecture gap discovery - DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL

Files

Just SKILL.md in .claude/skills/completion-check of parcadei/Continuous-Claude-v3.

Open the folder on GitHubat commit d07ff4b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.

vibeeval/vibecosystemskills/completion-check

Compare with similar skills

Completion Check 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.

Completion Check compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Completion Check this skillparcadei/Continuous-Claude-v3	3.9k	1 repos	~733	Automated safety check: Pass	MIT	8 mo ago
Auditing Terraform Infrastructure For Securitymukul975/Anthropic-Cybersecurity-Skills	34k	—	~3k	Automated safety check: Pass	Apache-2.0	1 mo ago
RAG Infrastructuresickn33/agentic-awesome-skills	47k	1 repos	~2.2k	Automated safety check: Pass	MIT	yesterday
Implementing Infrastructure As Code Security Scanningmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Verification Before Completionforyourhealth111-pixel/Vibe-Skills	3.6k	—	~1.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
Verification Before Completionfarm-fe/farm	5.6k	46 repos	~1k	Automated safety check: Pass	MIT	16 days ago

Similar skills

Auditing Terraform Infrastructure For Security
mukul975/Anthropic-Cybersecurity-Skills
Auditing Terraform infrastructure-as-code for security misconfigurations using Checkov, tfsec, Terrascan, and OPA/Rego policies to detect overly permissive IAM policies, public resource exposure…
34k GitHub stars~3k tokensUpdated 1 mo ago
DevOps & CloudAuto-check passed
RAG Infrastructure
sickn33/agentic-awesome-skills
Build and operate Retrieval-Augmented Generation (RAG) infrastructure with vector stores, embedding pipelines, and hybrid search.
47k GitHub starsUsed in 1 repo~2.2k tokens
AI & LLM EngineeringAuto-check passed
Implementing Infrastructure As Code Security Scanning
mukul975/Anthropic-Cybersecurity-Skills
Implements automated security scanning for Infrastructure as Code using Checkov, tfsec, and KICS to detect misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts, plus…
34k GitHub stars~2.2k tokensUpdated 1 mo ago
DevOps & CloudAuto-check passed
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
3.6k GitHub stars~1.1k tokensUpdated 1 mo ago
Agent WorkflowsAuto-check passed
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
5.6k GitHub starsUsed in 46 repos~1k tokens
Agent WorkflowsAuto-check passed
Import Infrastructure As Code
github/awesome-copilot
Official
Import existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM).
40k GitHub starsUsed in 1 repo~4.7k tokens
DevOps & CloudAuto-check passed

Questions about Completion Check

What does Completion Check do?

Completion Check: Verify Infrastructure Is Wired. An agent skill from parcadei/Continuous-Claude-v3. Completion Check is an agent skill from parcadei/Continuous-Claude-v3.

How do I install Completion Check in Claude Code?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill completion-check -a claude-code`. Or copy the skill folder (.claude/skills/completion-check in parcadei/Continuous-Claude-v3) into .claude/skills/completion-check in your project. Claude Code loads it when a task matches its description.

How do I install Completion Check in Codex?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill completion-check -a codex`. Or copy the skill folder (.claude/skills/completion-check in parcadei/Continuous-Claude-v3) into .agents/skills/completion-check in your project. Codex loads it when a task matches its description.

Can I use Completion Check 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 parcadei/Continuous-Claude-v3 --skill completion-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/completion-check, .gemini/skills/completion-check, .github/skills/completion-check and .opencode/skills/completion-check in your project.

What does Completion Check need to run?

Going by SKILL.md and its folder, Completion Check needs the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Completion Check access the network?

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

Is Completion Check 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 Completion Check use?

Completion Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Completion Check use?

About 733 tokens (SKILL.md is roughly 2.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 Completion Check?

Skills that share tags, products or a category with Completion Check: Auditing Terraform Infrastructure For Security (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), RAG Infrastructure (sickn33/agentic-awesome-skills, 47k stars), Implementing Infrastructure As Code Security Scanning (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Verification Before Completion (foryourhealth111-pixel/Vibe-Skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Completion Check?

parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,940 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.

Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Completion Check

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Completion Check: Verify Infrastructure Is Wired

Pattern

DO

DON'T

Completion Checklist

Example: DAG Task Graph

Source Sessions

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from parcadei/Continuous-Claude-v3

Questions about Completion Check