src/claude/skills/flag/SKILL.md
Quick-capture observations to a queue for later follow-up or 1B1 discussion
npx skillsauth add the-agency-ai/the-agency src/claude/skills/flagInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Zero-friction capture of observations during work. Flag something now, discuss it later. Flags are stored in the ISCP SQLite DB (outside git) — instant capture from any worktree.
$ARGUMENTS: The message to flag, or a subcommand (list, clear, count, discuss), or --to <agent> <message> to route to a specific agent.If $ARGUMENTS is a message (not a subcommand):
bash $CLAUDE_PROJECT_DIR/agency/tools/flag "$ARGUMENTS"
Confirm: "Flagged: [message summary]"
If $ARGUMENTS starts with --to:
bash $CLAUDE_PROJECT_DIR/agency/tools/flag --to <agent-address> "message"
The agent address must be fully qualified (repo/principal/agent). The flag appears in the target agent's queue on their next flag list or iscp-check.
If $ARGUMENTS is list:
bash $CLAUDE_PROJECT_DIR/agency/tools/flag list
Displays all unread flags and marks them as read (Slack-style seen behavior). Three-state lifecycle: unread → read (on list) → processed (on discuss/clear).
If $ARGUMENTS is count:
bash $CLAUDE_PROJECT_DIR/agency/tools/flag count
Returns unread count only.
If $ARGUMENTS is clear:
bash $CLAUDE_PROJECT_DIR/agency/tools/flag clear
Marks all flags as processed.
If $ARGUMENTS is discuss:
bash $CLAUDE_PROJECT_DIR/agency/tools/flag discuss
Outputs the queue as a numbered 1B1 agenda and marks all as processed. Then invoke /discuss with the agenda items for structured resolution.
capture → unread → read (on list) → processed (on discuss/clear)
Flags are DB-only — no git payload, instant capture. They're designed for quick observations during work, not formal communication (use dispatches for that).
OFFENDERS WILL BE FED TO THE — CUTE — ATTACK KITTENS!
business
Sync worktree with master — merge, copy settings, run sandbox-sync, report changes
tools
List all git worktrees with status info (branch, clean/dirty, deps)
tools
Remove a git worktree and optionally delete its branch
development
Create a new git worktree with dedicated branch and bootstrapped dev environment