Agent skill

Conducty Verify

by robertbarclayy in robertbarclayy/conducty

The evidence gate. An agent skill from robertbarclayy/conducty.

MITAuto-check passed

Install Conducty Verify

skills CLI
$ npx skills add robertbarclayy/conducty --skill conducty-verify -a claude-code

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

GitHub CLI
$ gh skill install robertbarclayy/conducty conducty-verify --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/robertbarclayy/conducty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conducty-verify .claude/skills/conducty-verify && 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/

Facts

Skill name
conducty-verify
GitHub stars
176
Token cost
~950 tokens
SKILL.md length
224 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

The evidence gate. An agent skill from robertbarclayy/conducty.

  • SKILL.md covers The Gate, Calibrated Verification, Checkpoint Verification and Fix Verification, plus 2 more sections
  • Calls make

What it does

Conducty Verify is an agent skill from robertbarclayy/conducty. The evidence gate. Run the verification command via Bash, read the output, then make the claim. Use before marking ANY prompt complete, before any "done" / "passed" claim, or when the user asks to verify, confirm, or prove a result.

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

It works with Bash. The repository describes itself as: Stop context-switching. Start batch-planning. Conducty replaces the fragmented cycle of plan → prompt → wait → get distracted → review → fix → repeat with advanced batch planning. The licence is MIT.

Example prompts

  • “passed”
  • “/conducty-verify”

What it can do on your machine

Read from SKILL.md and the folder at commit 64aefd5. 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:

    • make

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Conducty Verify loads about 950 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 224 words of instructions outside code blocks.

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

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 robertbarclayy/conducty at commit 64aefd5, republished under its MIT licence (© robertbarclayy). 224 words, ~950 tokens.

Download SKILL.mdSave it as .claude/skills/conducty-verify/SKILL.md (or your agent's skills folder).
name
conducty-verify
description
The evidence gate. Run the verification command via Bash, read the output, then make the claim. Use before marking ANY prompt complete, before any "done" / "passed" claim, or when the user asks to verify, confirm, or prove a result.
aliases
conducty-verify, verify
tags
conducty/skill, conducty/verify

Conducty Verify — The Evidence Gate

Run the command. Read the output. Then claim the result. Nothing else qualifies.

The Gate

Before ANY completion claim, status update, or expression of satisfaction:

1. IDENTIFY — What command proves this claim? (from the prompt's Verification field)
2. RUN     — Execute the command (Bash) fresh and complete
3. READ    — Full output, exit code, failure count
4. JUDGE   — Does the output confirm the claim?
              YES → State the claim WITH the evidence
              NO  → State what actually happened WITH the evidence
5. RECORD  — Log the result for checkpoint and improvement tracking

Skip any step and the claim is unsupported. "Should work" is not evidence. "The agent said it passed" is not evidence. Only output from a command you just ran via Bash is evidence.

Calibrated Verification

The plan assigns a review level to each prompt. Verification scales accordingly:

verify-only (Low complexity)

Run the verification command. Read the output. If it passes, the prompt is done.

IDENTIFY: P3 verification is `npm test -- --grep "auth"`
RUN:      npm test -- --grep "auth"
READ:     12/12 tests pass, exit 0
CLAIM:    "P3 verified — 12/12 auth tests pass"
spec-review (Medium complexity)

Run the verification command. If it passes, dispatch the spec compliance reviewer (see [[conducty-execute]]). Both must pass.

IDENTIFY: P5 verification is `cargo test session`
RUN:      cargo test session
READ:     8/8 tests pass, exit 0
THEN:     Dispatch spec reviewer → spec-pass
CLAIM:    "P5 verified — tests pass, spec compliant"
full-review (High complexity)

Run the verification command. If it passes, dispatch spec reviewer. If spec passes, dispatch quality reviewer. All three must pass.

IDENTIFY: P7 verification is `make test && make lint`
RUN:      make test && make lint
READ:     all pass, exit 0
THEN:     Spec reviewer → spec-pass → Quality reviewer → pass
CLAIM:    "P7 verified — tests pass, spec compliant, quality approved"

Checkpoint Verification

When verifying an entire group (used by [[conducty-checkpoint]]):

For EACH prompt in the group:
  IDENTIFY → RUN → READ → JUDGE
  Record: pass with evidence / needs-fix with failure output

Report: "Group A: 3/4 passed. P2 needs-fix (2 test failures in auth module)"

Never say "Group passed" without individually verifying every prompt.

Fix Verification

When verifying a fix prompt resolved the original issue:

1. Run the ORIGINAL verification command (the one that failed)
2. Run any ADDITIONAL check for the specific failure that triggered the fix
3. Both must pass
CLAIM: "Fix verified — original tests pass AND specific failure resolved"

Evidence Format

For consistency and machine-readability in [[Metrics]] / [[Prompt Log]]:

**P{N} Verification** [{timestamp}]
- Command: `{command}`
- Exit code: {0/1/...}
- Result: {pass/fail}
- Detail: {summary of output — test count, error message, etc.}
- Review: {verify-only/spec-review/full-review} — {outcome}

This format feeds into [[conducty-checkpoint]] health metrics and [[conducty-improve]] learning.

When to Apply

  • Before marking ANY prompt as completed
  • Before passing ANY prompt during checkpoint
  • Before claiming ANY fix resolved an issue
  • Before moving to the next parallelization group
  • Before any expression of satisfaction about work state

© robertbarclayy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/conducty-verify of robertbarclayy/conducty.

Open the folder on GitHubat commit 64aefd5

Compare with similar skills

Conducty Verify 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.

Conducty Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conducty Verify this skillrobertbarclayy/conducty176—~950Automated safety check: PassMIT
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills21k—~1.9kAutomated safety check: PassMIT
E2Ecallstack/react-native-pager-view3.4k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Neat-Freak Knowledge Closeout

    KKKKhazix/khazix-skills

    Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.

    21k GitHub stars~1.9k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check passed
  • E2E

    callstack/react-native-pager-view

    Agentic end-to-end tests with e2e, the e2e runner. An agent skill from callstack/react-native-pager-view.

    3.4k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

More from robertbarclayy/conducty

All 20 skills in this repo
  • Conducty Checkpoint

    robertbarclayy/conducty

    Quality gate between parallelization groups. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Conducty Code Review

    robertbarclayy/conducty

    Standalone post-implementation code review across a whole branch or PR.

    176 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed
  • Conducty Context

    robertbarclayy/conducty

    Ingest a project directory into the Obsidian vault as a linked context sub-graph — Architecture, Conventions, Invariants, Hotspots, Tests, Glossary, plus per-bounded-context module notes.

    176 GitHub stars~3.7k tokensUpdated 3 mo ago
    Auto-check passed
  • Conducty Debug

    robertbarclayy/conducty

    Leverage-point analysis for failed prompts. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Conducty Execute

    robertbarclayy/conducty

    Dispatches Claude Code Task subagents to run prompts from a vault plan note.

    176 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Conducty Improve

    robertbarclayy/conducty

    End-of-plan improvement kata. An agent skill from robertbarclayy/conducty.

    176 GitHub stars~1.5k tokensUpdated 3 mo ago
    Auto-check passed

Works with

Questions about Conducty Verify

What does Conducty Verify do?

The evidence gate. An agent skill from robertbarclayy/conducty. Conducty Verify is an agent skill from robertbarclayy/conducty. The evidence gate.

How do I install Conducty Verify in Claude Code?

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

How do I install Conducty Verify in Codex?

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

Can I use Conducty Verify 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 robertbarclayy/conducty --skill conducty-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conducty-verify, .gemini/skills/conducty-verify, .github/skills/conducty-verify and .opencode/skills/conducty-verify in your project.

What does Conducty Verify need to run?

Going by SKILL.md and its folder, Conducty Verify needs the command-line tools its instructions call (make).

Does Conducty Verify access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Conducty Verify 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 Conducty Verify use?

Conducty Verify 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 Conducty Verify use?

About 950 tokens (SKILL.md is roughly 3.8k 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 Conducty Verify?

Skills that share tags, products or a category with Conducty Verify: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars), Mole Bug Patterns (tw93/Mole, 70k stars) and Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conducty Verify?

robertbarclayy (a GitHub user) maintains it in robertbarclayy/conducty, which has 176 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on June 19, 2026.

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