Agent skill

Team Ultra Analyze

by catlog22 in catlog22/Claude-Code-Workflow

Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

MITAuto-check: notesAgent Workflows

Install Team Ultra Analyze

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill team-ultra-analyze -a claude-code

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

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow team-ultra-analyze --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/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/team-ultra-analyze .claude/skills/team-ultra-analyze && 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
team-ultra-analyze
GitHub stars
2.1k
Token cost
~2.4k tokens
SKILL.md length
549 words
Files
11
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

  • Team ultra-analyze
  • SKILL.md covers Architecture, Role Registry, Role Router and Delegation Lock, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Ultra Analyze is an agent skill from catlog22/Claude-Code-Workflow. Deep collaborative analysis team skill. All roles route via this SKILL.md. Beat model is coordinator-only (monitor.md). Structure is roles/ + specs/. Triggers on "team ultra-analyze", "team analyze".

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files (for example `roles/analyst/role.md`, `roles/coordinator/commands/analyze.md` and `roles/coordinator/commands/dispatch.md`).

It sits in Agent Workflows. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Team ultra-analyze

Example prompts

  • “team ultra-analyze”
  • “team analyze”
  • “/team-ultra-analyze”

Requirements

  • Pre-approved tools (allowed-tools): spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ccw-tools__team_msg(*)

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • spawn_agent(*)
    • wait_agent(*)
    • send_message(*)
    • followup_task(*)
    • close_agent(*)
    • list_agents(*)
    • report_agent_job_result(*)
    • request_user_input(*)
    • Read(*)
    • Write(*)

    …and 5 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Team Ultra Analyze loads about 2.4k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 549 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~2.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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), re

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 catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 549 words, ~2,440 tokens.

Download SKILL.mdSave it as .claude/skills/team-ultra-analyze/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
team-ultra-analyze
description
Deep collaborative analysis team skill. All roles route via this SKILL.md. Beat model is coordinator-only (monitor.md). Structure is roles/ + specs/. Triggers on "team ultra-analyze", "team analyze".
allowed-tools
spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ccw-tools__team_msg(*)

Team Ultra Analyze

Deep collaborative analysis: explore -> analyze -> discuss -> synthesize. Supports Quick/Standard/Deep pipeline modes with configurable depth (N parallel agents). Discussion loops enable user-guided progressive understanding.

Architecture

Skill(skill="team-ultra-analyze", args="<topic>")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn workers -> STOP
                                    |
                    +-------+-------+-------+-------+
                    v       v       v       v
                 [team-worker agents, each loads roles/<role>/role.md]

Pipeline (Standard mode):
  [EXPLORE-1..N](parallel) -> [ANALYZE-1..N](parallel) -> DISCUSS-001 -> SYNTH-001

Pipeline (Deep mode):
  [EXPLORE-1..N] -> [ANALYZE-1..N] -> DISCUSS-001 -> ANALYZE-fix -> DISCUSS-002 -> ... -> SYNTH-001

Pipeline (Quick mode):
  EXPLORE-001 -> ANALYZE-001 -> SYNTH-001

Role Registry

RolePathPrefixInner Loop
coordinatorroles/coordinator/role.md——
explorerroles/explorer/role.mdEXPLORE-*false
analystroles/analyst/role.mdANALYZE-*false
discussantroles/discussant/role.mdDISCUSS-*false
synthesizerroles/synthesizer/role.mdSYNTH-*false

Role Router

Parse $ARGUMENTS:

  • Has --role <name> → Read roles/<name>/role.md, execute Phase 2-4
  • No --role → roles/coordinator/role.md, execute entry router

Delegation Lock

Coordinator is a PURE ORCHESTRATOR. It coordinates, it does NOT do.

Before calling ANY tool, apply this check:

Tool CallVerdictReason
spawn_agent, wait_agent, close_agent, send_message, followup_taskALLOWEDOrchestration
list_agentsALLOWEDAgent health check
request_user_inputALLOWEDUser interaction
mcp__ccw-tools__team_msgALLOWEDMessage bus
Read/Write on .workflow/.team/ filesALLOWEDSession state
Read on roles/, commands/, specs/ALLOWEDLoading own instructions
Read/Grep/Glob on project source codeBLOCKEDDelegate to worker
Edit on any file outside .workflow/BLOCKEDDelegate to worker
Bash("ccw cli ...")BLOCKEDOnly workers call CLI
Bash running build/test/lint commandsBLOCKEDDelegate to worker

If a tool call is BLOCKED: STOP. Create a task, spawn a worker.

No exceptions for "simple" tasks. Even a single-file read-and-report MUST go through spawn_agent.


Shared Constants

  • Session prefix: UAN
  • Session path: .workflow/.team/UAN-<date>-<slug>/
  • Team name: ultra-analyze
  • CLI tools: ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
  • Message bus: mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker Spawn Template

Coordinator spawns workers using this template:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  message: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
requirement: <topic-description>
inner_loop: false

Read role_spec file (<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.

## Task Context
task_id: <task-id>
title: <task-title>
description: <task-description>
pipeline_phase: <pipeline-phase>

## Upstream Context
<prev_context>`
})

After spawning, use wait_agent({ timeout_ms: 1800000 }) to collect results. If result.timed_out, send STATUS_CHECK via followup_task (wait 3 min), then FINALIZE with interrupt (wait 3 min), then mark timed_out and close agents. Use close_agent({ target }) each worker.

Model Selection Guide
Rolemodelreasoning_effortRationale
Explorer (EXPLORE-*)(default)mediumFile reading and pattern scanning, less reasoning needed
Analyst (ANALYZE-*)(default)highDeep analysis requires full reasoning
Discussant (DISCUSS-*)(default)highSynthesis of multiple viewpoints, dialectic reasoning
Synthesizer (SYNTH-*)(default)mediumAggregation and summary over generation

Override model/reasoning_effort in spawn_agent when cost optimization is needed:

spawn_agent({
  agent_type: "team_worker",
  task_name: "<task-id>",
  fork_turns: "none",
  model: "<model-override>",
  reasoning_effort: "<effort-level>",
  message: "..."
})

User Commands

CommandAction
check / statusOutput execution status diagram, do not advance pipeline
resume / continueCheck worker status, advance to next pipeline step
Show full SKILL.md (208 more words)Show less

Session Directory

.workflow/.team/UAN-{YYYY-MM-DD}-{slug}/
+-- .msg/messages.jsonl          # Message bus log
+-- .msg/meta.json               # Session metadata + cross-role state
+-- discussion.md                # Understanding evolution and discussion timeline
+-- explorations/                # Explorer output
|   +-- exploration-001.json
|   +-- exploration-002.json
+-- analyses/                    # Analyst output
|   +-- analysis-001.json
|   +-- analysis-002.json
+-- discussions/                 # Discussant output
|   +-- discussion-round-001.json
+-- conclusions.json             # Synthesizer output
+-- wisdom/                      # Cross-task knowledge
|   +-- learnings.md
|   +-- decisions.md
|   +-- conventions.md
|   +-- issues.md

v4 Agent Coordination

Message Semantics
IntentAPIExample
Send exploration findings to running analystssend_messageQueue upstream context without interrupting ANALYZE-* workers
Not used in this skillfollowup_taskNo resident agents -- all workers are one-shot
Check running agentslist_agentsVerify parallel explorer/analyst health during resume
Parallel Phase Coordination

Standard/Deep modes spawn N parallel agents in EXPLORE and ANALYZE phases. Use batch spawn + wait:

// EXPLORE phase: spawn N explorers in parallel
const explorerNames = ["EXPLORE-001", "EXPLORE-002", ..., "EXPLORE-00N"]
for (const name of explorerNames) {
  spawn_agent({ agent_type: "team_worker", task_name: name, ... })
}
wait_agent({ timeout_ms: 1800000 })  // 30 min — apply timeout cascade if timed_out
// Collect all results, then spawn ANALYZE phase

// ANALYZE phase: send exploration context to analysts via items (not send_message)
// since analysts are spawned AFTER explorers complete
Agent Health Check

Use list_agents({}) in handleResume and handleComplete:

// Reconcile session state with actual running agents
const running = list_agents({})
// Compare with tasks.json active_agents
// Reset orphaned tasks (in_progress but agent gone) to pending
// Critical for parallel phases -- multiple agents may crash independently
Named Agent Targeting

Workers are spawned with task_name: "<task-id>" enabling direct addressing:

  • send_message({ target: "ANALYZE-001", message: "..." }) -- queue supplementary exploration findings
  • close_agent({ target: "EXPLORE-001" }) -- cleanup by name after wait_agent returns

Completion Action

When pipeline completes, coordinator presents:

functions.request_user_input({
  questions: [{
    question: "Ultra-Analyze pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up tasks and team resources" },
      { label: "Keep Active", description: "Keep session active for follow-up work or inspection" },
      { label: "Export Results", description: "Export deliverables to a specified location, then clean" }
    ]
  }]
})
ChoiceAction
Archive & CleanUpdate session status="completed" -> output final summary
Keep ActiveUpdate session status="paused" -> output resume instructions
Export Resultsrequest_user_input for target path -> copy deliverables -> Archive & Clean

Specs Reference

Error Handling

ScenarioResolution
Unknown --role valueError with role registry list
Role file not foundError with expected path (roles/{name}/role.md)
Discussion loop stuck >5 roundsForce synthesis, offer continuation
CLI tool unavailableFallback chain: gemini -> codex -> manual analysis
Explorer agent failsContinue with available context, note limitation
Fast-advance conflictCoordinator reconciles on next callback
Completion action failsDefault to Keep Active

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

Files

SKILL.md and 10 other files in .codex/skills/team-ultra-analyze of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • roles/analyst/role.md
  • roles/coordinator/commands/analyze.md
  • roles/coordinator/commands/dispatch.md
  • roles/coordinator/commands/monitor.md
  • roles/coordinator/role.md
  • roles/discussant/role.md
  • roles/explorer/role.md
  • roles/synthesizer/role.md
  • specs/pipelines.md
  • specs/team-config.json

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Team Ultra Analyze 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.

Team Ultra Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Ultra Analyze this skillcatlog22/Claude-Code-Workflow2.1k—~2.4kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79689 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • 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
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    796 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Investigate

    catlog22/Claude-Code-Workflow

    Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Issue Discover

    catlog22/Claude-Code-Workflow

    Unified issue discovery and creation. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~3.3k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Team Ultra Analyze

What does Team Ultra Analyze do?

Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow. Team Ultra Analyze is an agent skill from catlog22/Claude-Code-Workflow. Deep collaborative analysis team skill.

When should I use Team Ultra Analyze?

Team Ultra Analyze fits situations like: team ultra-analyze.

How do I install Team Ultra Analyze in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill team-ultra-analyze -a claude-code`. Or copy the skill folder (.codex/skills/team-ultra-analyze in catlog22/Claude-Code-Workflow) into .claude/skills/team-ultra-analyze in your project. Claude Code loads it when a task matches its description.

How do I install Team Ultra Analyze in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill team-ultra-analyze -a codex`. Or copy the skill folder (.codex/skills/team-ultra-analyze in catlog22/Claude-Code-Workflow) into .agents/skills/team-ultra-analyze in your project. Codex loads it when a task matches its description.

Can I use Team Ultra Analyze 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 catlog22/Claude-Code-Workflow --skill team-ultra-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-ultra-analyze, .gemini/skills/team-ultra-analyze, .github/skills/team-ultra-analyze and .opencode/skills/team-ultra-analyze in your project.

What does Team Ultra Analyze need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Ultra Analyze is instructions for the agent only. Its frontmatter pre-approves these tools: spawn_agent(*), wait_agent(*), send_message(*), followup_task(*), close_agent(*), list_agents(*), report_agent_job_result(*), request_user_input(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__ccw-tools__team_msg(*).

Does Team Ultra Analyze 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 Team Ultra Analyze safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Team Ultra Analyze use?

Team Ultra Analyze 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 Team Ultra Analyze use?

About 2.4k tokens (SKILL.md is roughly 9.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 Team Ultra Analyze?

Skills that share tags, products or a category with Team Ultra Analyze: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Ultra Analyze?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,129 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.