Skip to content
Skills Library
AI & agents · Automation

start

/start

Start one coding agent from a Trailboss agent definition in a new Herdr or tmux terminal, in a folder as it is, with no worktree or branch. Use when asked to open, launch or spin up another agent for a question, an investigation or a conversation, rather than a task to merge.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Start one coding agent from a Trailboss agent definition in a new Herdr or tmux terminal, in a folder as it is, with no worktree or branch. Use when asked to open, launch or spin up another agent for a question, an investigation or a conversation, rather than a task to merge.

Original author description

Start one coding agent from a Trailboss agent definition in a new Herdr or tmux terminal, in a folder as it is, with no worktree or branch. Use when asked to open, launch or spin up another agent for a question, an investigation or a conversation, rather than a task to merge.

How it works

SKILL.md has no level-two headings · 16 lines, 271 words

SKILL.md preview
---
name: start
description: Start one coding agent from a Trailboss agent definition in a new Herdr or tmux terminal, in a folder as it is, with no worktree or branch. Use when asked to open, launch or spin up another agent for a question, an investigation or a conversation, rather than a task to merge.
requires: trailboss >= 0.5, api 1
---

# Start one agent

First run `trailboss version --json`. If it fails, or `version` is below 0.5 or `api` isn't 1, stop and tell the user to update Trailboss.

**Start or task?** `trailboss start` runs the agent in the folder you name, on whatever branch is checked out there: no worktree, no branch, nothing to accept. Use it when the agent reads, answers or investigates, or when the user will work with it directly. When the agent should change code that gets reviewed and merged, use a task instead (the `dispatch` skill).

1. Pick a definition: `trailboss agents` lists them (a kind such as `claude` or `codex`, yours, or the repository's); `trailboss agents show NAME` shows the command it runs.
2. Write its first prompt to stand alone, at least two words: what to do, where, and when it's done. Or leave it out and the agent starts with only the definition's rules, or waits for the user.
3. Show the plan: `trailboss --json start <definition> [--task "<prompt>" | --task-file F] [--in DIR] [--name LABEL]`. Tell the user the `command` and `folder`.
4. Start it with `--yes` only once the user agrees. A host must be running. It opens in a new terminal, nested under this session (or `--parent`).

The label (`--name`, default the definition's name) names its terminal and shows as `label` in `trailboss --json live` and `resume`. Use it to find the agent again; send it messages with the `follow-up` skill.

A repository's definition needs the user's approval first: if `start` refuses one, show the user `trailboss agents trust <name>` and let them approve it; never approve one yourself.

Versions

RepositoryScoreLicence
This page · trailboss-ai/trailboss-skills86MIT
tilnoteio/tilnote-blog100MIT
dedujeong/gemba100Apache-2.0
nextwork-projects/ai-video-editor-cooked100MIT
wrg32786/aigent-os100MIT
T-X-R/codex-game-studio100MIT
alienfast/claude100MIT
ratomirjovanovic/pandaward100AGPL-3.0
darioabc/massimo100MIT

Database snapshot: 13.11.2026 · package version f817760802ea (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86follow-up
    Send a running coding agent a message through Trailboss, now or once its turn ends. Use when asked to tell, remind or instruct another agent that runs in a Herdr or tmux terminal.
  • 90dispatch
    Hand work to new coding agents with Trailboss tasks, each in its own git worktree and branch, then review and merge what they did. Use when asked to start, check on or accept tasks run by other agents.
  • 100heka
    Drive the Heka macOS app with the `heka` CLI. Use when the HEKA_INSTANCE environment variable is set (you are in a Heka terminal), or when the user asks to use Heka from another terminal. Use it to start another agent in parallel on its own branch (`heka worktree create`), to…
  • 100herdr
    Drives Herdr, the workspace for coding agents, through one script that works in both the Herdr app (hc and herdr-app) and the Herdr TUI (herdr): finds the terminal this agent runs in, identifies and reads other agents' terminals, lists the roster, makes spaces, launches, briefs,…
  • 100worktree-per-agent
    Isolate an agent's work in its own git worktree branched off the default branch, so two agents never land conflicting changes on the shared checkout. Use at the start of any implementation task in a repo where others may also be working, and whenever a repo's instructions say "work in a worktree".
  • 100add-agent
    Use when you need to attach a new Claude Code agent (new tmux window) to an existing running octomux task, sharing the task's worktree and cwd

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.