Agent skill

Conducty Bootstrap

by robertbarclayy in robertbarclayy/conducty

First-run walkthrough for Conducty. An agent skill from robertbarclayy/conducty.

MITAuto-check passedTesting & QA

Install Conducty Bootstrap

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

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

GitHub CLI
$ gh skill install robertbarclayy/conducty conducty-bootstrap --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-bootstrap .claude/skills/conducty-bootstrap && 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-bootstrap
GitHub stars
176
Token cost
~1.4k tokens
SKILL.md length
724 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

First-run walkthrough for Conducty. An agent skill from robertbarclayy/conducty.

  • Works in 10 steps: Confirm the Vault → Seed Missing Indexes + Accumulators → First Project — Ingest Context → …
  • The user says set up Conducty
  • SKILL.md covers When to Use, Workflow, What Bootstrap Skips and Failure Modes, plus 1 more section
  • Calls git

What it does

Conducty Bootstrap is an agent skill from robertbarclayy/conducty. First-run walkthrough for Conducty. Confirms vault location, seeds indexes if missing, ingests the user's primary project via [[conducty-context]], and produces a tiny scoped first plan so the user sees the cycle end-to-end. Use when the user says "set up Conducty", "first time", "get started", "bootstrap", "I just installed Conducty", or when no plans yet exist in the vault.

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

It sits in Testing & QA. It works with Obsidian. 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.

When your agent uses it

  • The user says set up Conducty
  • I just installed Conducty
  • No plans yet exist in the vault

Example prompts

  • “set up Conducty”
  • “first time”
  • “get started”
  • “/conducty-bootstrap”

Workflow steps

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

  1. Confirm the Vault
  2. Seed Missing Indexes + Accumulators
  3. First Project — Ingest Context
  4. Pick a Tiny First Goal
  5. Generate the First Plan (Reduced Ceremony)
  6. Execute Manually
  7. Run Checkpoint
  8. Run Review + Improve
  9. Tour the Vault
  10. Hand Off to Plan

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:

    • 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

Conducty Bootstrap loads about 1.4k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 724 words of instructions outside code blocks.

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

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). 724 words, ~1,390 tokens.

Download SKILL.mdSave it as .claude/skills/conducty-bootstrap/SKILL.md (or your agent's skills folder).
name
conducty-bootstrap
description
First-run walkthrough for Conducty. Confirms vault location, seeds indexes if missing, ingests the user's primary project via [[conducty-context]], and produces a tiny scoped first plan so the user sees the cycle end-to-end. Use when the user says "set up Conducty", "first time", "get started", "bootstrap", "I just installed Conducty", or when no plans yet exist in the vault.
aliases
conducty-bootstrap, bootstrap
tags
conducty/skill, conducty/onboarding

Conducty Bootstrap — First-Run Walkthrough

The fastest path from "just installed" to "first finished plan." Bootstrap is opinionated: it picks a small first goal so the user sees the entire cycle (Plan → Execute → Verify → Improve) without committing to anything ambitious.

[!important] One-shot skill Bootstrap is meant to run once per machine. After it completes, the cycle is self-sustaining via [[conducty-plan]].

When to Use

  • The user just ran install-claude-code.sh and is starting their first session
  • The user says "set up Conducty", "first time", "get started", "bootstrap"
  • A Glob Plans/Plan *.md against the vault returns zero results — auto-trigger this skill

Workflow

Step 1: Confirm the Vault

Resolve $CONDUCTY_VAULT (default ~/Obsidian/Conducty/). Confirm with the user:

"Conducty vault is at <resolved path>. Open this directory in Obsidian to navigate the graph as we build it. OK to proceed?"

If the user wants a different path, ask them to set $CONDUCTY_VAULT in their shell profile and re-run. Do not silently move the vault.

Step 2: Seed Missing Indexes + Accumulators

Use [[conducty-obsidian]]'s bootstrap section. Create any missing:

  • Indexes: Conducty Index, Plans Index, Designs Index, Context Index, Improvements Index
  • Accumulators: Failure Patterns, Metrics, Prompt Log

If the installer already seeded them, this is a no-op.

Step 3: First Project — Ingest Context

Ask:

"Which project would you like Conducty to start with? Give me the path."

Run [[conducty-context]] on that path. The output is the project sub-graph: hub, Architecture, Conventions, Invariants, Hotspots, Tests, Glossary.

Briefly summarize for the user: bounded contexts found, test command resolved, any concerns flagged.

Step 4: Pick a Tiny First Goal

Suggest a Low-complexity goal — something the user will see succeed inside 30 minutes. Examples:

  • "Add a small utility function with TDD" (writes one function + tests)
  • "Improve a single error message in module X"
  • "Write a test for a previously-untested branch"

Refuse to bootstrap with a Medium/High goal — the point is to walk the cycle, not ship a feature.

Step 5: Generate the First Plan (Reduced Ceremony)

Run [[conducty-plan]] with the chosen goal and an appetite of 30 minutes. Produce a single-prompt plan in Group A (no parallelization, no tracer needed because there's only one). Review level: verify-only.

Step 6: Execute Manually

Do not auto-dispatch via [[conducty-execute]] on the first plan. Walk the user through manual execution:

  1. Open a fresh Claude Code session in the project directory
  2. Paste the prompt
  3. Watch the implementer work
  4. Run the verification command yourself

The point is for the user to feel the prompt's structure (acceptance criteria, no-go zones, escalation) before delegating it.

Step 7: Run Checkpoint

Use [[conducty-checkpoint]] on the single-prompt group. Verify result via [[conducty-verify]].

Show full SKILL.md (293 more words)Show less
Step 8: Run Review + Improve

Run [[conducty-review]] to update Metrics, Prompt Log. Then run [[conducty-improve]] to write the first Improvement YYYY-MM-DD HHmm.md. Encourage the user to read both — they're the feedback loop.

Step 9: Tour the Vault

Have the user open Obsidian on the vault. Walk them through:

  • Conducty Index (the root hub)
  • The new plan note
  • The context sub-graph for the project
  • The accumulating notes (Failure Patterns, Metrics, Prompt Log)
  • The graph view — show how the plan, design (if any), context, and improvement are linked
Step 10: Hand Off to Plan

Tell the user:

"From here, every working session starts with [[conducty-plan]]. The vault now has a baseline. Future plans will read this graph and get sharper."

Bootstrap is complete. Do not run again on this machine unless the vault is wiped.

What Bootstrap Skips

  • No shaping (conducty-shape) — first goal must be Low complexity, design is overkill
  • No worktrees — single prompt, no parallelism
  • No code review or ship — first plan is intentionally throwaway / educational
  • No conducty-dialectic — we're not making architectural decisions on bootstrap

Failure Modes

  • Vault path inaccessible: report the error, suggest creating the parent directory, and abort.
  • Project has no test command discoverable: ask the user; record in Context {Project} Tests. Do not invent one.
  • Project is not a git repo: warn but proceed. [[conducty-debug]] won't have git diff access; flag for the user.
  • User picks a Medium/High goal: politely refuse and ask for something smaller. "Bootstrap is for cycle-feel. We'll do real work after."

Principles

  • Throwaway first plan — the goal is muscle memory, not feature delivery
  • Manual execution on bootstrap — feel the prompt before delegating
  • Vault tour is part of onboarding — the user must see the graph come alive
  • One-shot skill — bootstrap doesn't run twice; subsequent plans go through [[conducty-plan]]

© 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-bootstrap of robertbarclayy/conducty.

Open the folder on GitHubat commit 64aefd5

Compare with similar skills

Conducty Bootstrap 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 Bootstrap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Conducty Bootstrap this skillrobertbarclayy/conducty176—~1.4kAutomated safety check: PassMIT
Plugin Testingpolyipseity/obsidian-terminal948—~828Automated safety check: PassAGPL-3.0
PlanRafaelGB/Obsidian-ZettelFlow174—~651Automated safety check: PassMIT
Obsidian Debug Bundlejeremylongshore/tons-of-skills-marketplace2.8k—~2.2kAutomated safety check: PassMIT
ReleaseRafaelGB/Obsidian-ZettelFlow174—~1.4kAutomated safety check: PassMIT
Nexus TestingProfSynapse/nexus156—~994Automated safety check: PassMIT

Similar skills

  • Plugin Testing

    polyipseity/obsidian-terminal

    Skill for testing Obsidian plugin features in this repository.

    948 GitHub stars~828 tokensUpdated 5 days ago
    Testing & QAAuto-check passed
  • Plan

    RafaelGB/Obsidian-ZettelFlow

    Stage 2 of the SDD pipeline — turn a ZettelFlow spec (in the GitHub issue body) into a technical plan posted as an issue comment (approach, files by layer, Obsidian score-rule impact, test strategy…

    174 GitHub stars~651 tokensUpdated today
    Testing & QAAuto-check passed
  • Obsidian Debug Bundle

    jeremylongshore/tons-of-skills-marketplace

    Collect Obsidian plugin debug evidence for support and troubleshooting.

    2.8k GitHub stars~2.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Release

    RafaelGB/Obsidian-ZettelFlow

    Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format.

    174 GitHub stars~1.4k tokensUpdated today
    Testing & QAAuto-check passed
  • Nexus Testing

    ProfSynapse/nexus

    Verify a Nexus change — pick a Jest lane, write a test that can actually fail, run the in-app Obsidian CLI loop, drive the eval harness, or fix a shipped-docs drift failure.

    156 GitHub stars~994 tokensUpdated today
    Testing & QAAuto-check passed
  • TDD

    RafaelGB/Obsidian-ZettelFlow

    The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable.

    174 GitHub stars~724 tokensUpdated today
    Testing & QAAuto-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

Categories

Questions about Conducty Bootstrap

What does Conducty Bootstrap do?

First-run walkthrough for Conducty. An agent skill from robertbarclayy/conducty. Conducty Bootstrap is an agent skill from robertbarclayy/conducty. First-run walkthrough for Conducty.

When should I use Conducty Bootstrap?

Conducty Bootstrap fits situations like: the user says set up Conducty; I just installed Conducty; no plans yet exist in the vault.

How do I install Conducty Bootstrap in Claude Code?

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

How do I install Conducty Bootstrap in Codex?

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

Can I use Conducty Bootstrap 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-bootstrap -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-bootstrap, .gemini/skills/conducty-bootstrap, .github/skills/conducty-bootstrap and .opencode/skills/conducty-bootstrap in your project.

What does Conducty Bootstrap need to run?

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

Does Conducty Bootstrap 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 Conducty Bootstrap 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 Bootstrap use?

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

About 1.4k tokens (SKILL.md is roughly 5.6k 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 Bootstrap?

Skills that share tags, products or a category with Conducty Bootstrap: Plugin Testing (polyipseity/obsidian-terminal, 948 stars), Plan (RafaelGB/Obsidian-ZettelFlow, 174 stars), Obsidian Debug Bundle (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Release (RafaelGB/Obsidian-ZettelFlow, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Conducty Bootstrap?

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.