kill
# /clickup:kill - Terminate Agent Session
What this skill does
# /clickup:kill - Terminate Agent Session
Kill a ClickUp agent's tmux session, optionally cleaning up the worktree.
## Usage
```
/clickup:kill <task_id> [--cleanup]
```
## Arguments
- `task_id` (required): The ClickUp task ID (e.g., `86ew43633`)
- `--cleanup` (optional): Also remove the worktree after killing the session
## Behavior
When this command is invoked:
1. **Kill tmux Session**: Terminate the agent's tmux session
2. **Optional Cleanup**: If `--cleanup` is specified, remove the worktree
3. **Report Status**: Confirm what was done
## Instructions for Claude
When the user runs `/clickup:kill`, execute the following:
```bash
# Parse arguments
TASK_ID=""
CLEANUP=""
for arg in $ARGUMENTS; do
if [ "$arg" = "--cleanup" ]; then
CLEANUP="--cleanup"
elif [ -z "$TASK_ID" ]; then
TASK_ID="$arg"
fi
done
if [ -z "$TASK_ID" ]; then
echo "Usage: /clickup:kill <task_id> [--cleanup]"
echo ""
echo "Options:"
echo " --cleanup Also remove the worktree"
echo ""
echo "Available ClickUp sessions:"
tmux ls 2>/dev/null | grep "clickup-" || echo " No active sessions"
exit 1
fi
SESSION="clickup-${TASK_ID}"
# Kill session
if tmux has-session -t "$SESSION" 2>/dev/null; then
tmux kill-session -t "$SESSION"
echo "✅ Killed session: $SESSION"
else
echo "⚠️ Session not found: $SESSION (may already be terminated)"
fi
# Optional cleanup
if [ "$CLEANUP" = "--cleanup" ]; then
echo ""
echo "🧹 Cleaning up worktree..."
PROJECT_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
# Find worktree by task ID
WORKTREE=$(find "$PROJECT_ROOT/.worktrees" -maxdepth 3 -type d -name "*${TASK_ID}*" 2>/dev/null | head -1)
if [ -n "$WORKTREE" ] && [ -d "$WORKTREE" ]; then
echo "Found worktree: $WORKTREE"
# Two-phase cleanup
git worktree remove "$WORKTREE" --force 2>/dev/null || true
[ -d "$WORKTREE" ] && rm -rf "$WORKTREE"
git worktree prune
echo "✅ Worktree removed"
else
echo "⚠️ No worktree found for task: $TASK_ID"
fi
fi
```
## Alternative: Use Script
If the project has the scripts/clickup directory:
```bash
cd "$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
./scripts/clickup/tmux-kill.sh "$TASK_ID" "$CLEANUP"
```
## Examples
```bash
# Kill session only (keep worktree for later inspection)
/clickup:kill 86ew43633
# Kill session and cleanup worktree
/clickup:kill 86ew43633 --cleanup
# List sessions before killing
tmux ls | grep clickup-
```
## When to Use --cleanup
Use `--cleanup` when:
- The task is complete and merged
- You want to free up disk space
- The agent crashed and work is unrecoverable
Don't use `--cleanup` when:
- You might want to inspect the work later
- The agent is just paused temporarily
- You want to manually review changes before cleanup
## Related Commands
- `/clickup:attach` - Attach to an agent session
- `/clickup:status` - View all agent sessions
- `/clickup:done` - Complete workflow (includes cleanup)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.