ck-scout

Estrelas4

Forks1

Atualizado18 de maio de 2026 às 05:57

Fast codebase scouting using parallel agents. Use for file discovery, task context gathering, quick searches across directories. Supports internal (Explore) and external (Gemini/OpenCode) agents.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

bestagentkits

bestagentkits/ck-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	ck:scout
description	Fast codebase scouting using parallel agents. Use for file discovery, task context gathering, quick searches across directories. Supports internal (Explore) and external (Gemini/OpenCode) agents.
argument-hint	[search-target] [ext]
metadata	{"author":"claudekit","version":"1.0.0"}

Scout

Fast, token-efficient codebase scouting using parallel agents to find files needed for tasks.

Arguments

Default: Scout using built-in Explore subagents in parallel (./references/internal-scouting.md)
ext: Scout using external Gemini/OpenCode CLI tools in parallel (./references/external-scouting.md)

When to Use

Beginning work on feature spanning multiple directories
User mentions needing to "find", "locate", or "search for" files
Starting debugging session requiring file relationships understanding
User asks about project structure or where functionality lives
Before changes that might affect multiple codebase parts

Quick Start

Analyze user prompt to identify search targets
Use a wide range of Grep and Glob patterns to find relevant files and estimate scale of the codebase
Spawn parallel agents with divided directories
Collect results into concise report

Configuration

Read from .claude/.ck.json:

gemini.model - Gemini model (default: gemini-3-flash-preview)

Workflow

1. Analyze Task

Parse user prompt for search targets
Identify key directories, patterns, file types, lines of code
Determine optimal SCALE value of subagents to spawn

2. Divide and Conquer

Split codebase into logical segments per agent
Assign each agent specific directories or patterns
Ensure no overlap, maximize coverage

3. Register Scout Tasks

Skip if: Agent count ≤ 2 (overhead exceeds benefit)
Skip if: Task tools unavailable (VSCode extension) — use TodoWrite instead
TaskList first — check for existing scout tasks in session
If not found, TaskCreate per agent with scope metadata
See references/task-management-scouting.md for patterns and examples

4. Spawn Parallel Agents

Load appropriate reference based on decision tree:

Internal (Default): references/internal-scouting.md (Explore subagents)
External: references/external-scouting.md (Gemini/OpenCode)

Notes:

TaskUpdate each task to in_progress before spawning its agent (skip if Task tools unavailable)
Prompt detailed instructions for each subagent with exact directories or files it should read
Remember that each subagent has less than 200K tokens of context window
Amount of subagents to-be-spawned depends on the current system resources available and amount of files to be scanned
Each subagent must return a detailed summary report to a main agent

5. Collect Results

IMPORTANT: Invoke "/ck:project-organization" skill to organize the outputs.

Timeout: 3 minutes per agent (skip non-responders)
TaskUpdate completed tasks; log timed-out agents in report (skip if Task tools unavailable)
Aggregate findings into single report
List unresolved questions at end

Report Format

# Scout Report

## Relevant Files
- `path/to/file.ts` - Brief description
- ...

## Unresolved Questions
- Any gaps in findings

References

references/internal-scouting.md - Using Explore subagents
references/external-scouting.md - Using Gemini/OpenCode CLI
references/task-management-scouting.md - Claude Task patterns for scout coordination

Mais deste repositório

mesmo repositório

ck-ai-artist

bestagentkits/ck-skills

Generate images via Nano Banana with 129 curated prompts. Mandatory validation interview refines style/mood/colors (use --skip to bypass). 3 modes: search, creative, wild. Styles: Ukiyo-e, Bento grid, cyberpunk, cinematic, vintage patent.

2026-05-184

ck-plan

bestagentkits/ck-skills

Plan implementations, design architectures, create technical roadmaps with detailed phases. Use for feature planning, system design, solution architecture, implementation strategy, phase documentation.

2026-05-184

ck-codex

bestagentkits/ck-skills

Use OpenAI Codex CLI (GPT-5.5 + gpt-image-2) programmatically: second-opinion code review, GitHub PR audit, plan/spec auditing, edge-case discovery, style/persona prompting, and subscription-billed image generation for visual assets, decorations, infographics, banners. Activate whenever the user says 'codex', 'second opinion', 'audit plan', 'review PR with codex', 'generate image', 'create banner/illustration/visual asset', or wants a careful adversarial reader to catch what Claude (especially Opus) might skim past.

2026-05-184

ck-cook

bestagentkits/ck-skills

ALWAYS activate this skill before implementing EVERY feature, plan, or fix.

2026-05-184

ck-copywriting

bestagentkits/ck-skills

Conversion copywriting formulas, headline templates, email copy patterns, landing page structures, CTA optimization, and writing style extraction. Activate for writing high-converting copy, crafting headlines, email campaigns, landing pages, or applying custom writing styles from assets/writing-styles/ directory.

2026-05-184

ck-databases

bestagentkits/ck-skills

Design schemas, write queries for MongoDB and PostgreSQL. Use for database design, SQL/NoSQL queries, aggregation pipelines, indexes, migrations, replication, performance optimization, psql CLI.

2026-05-184

name	ck:scout
description	Fast codebase scouting using parallel agents. Use for file discovery, task context gathering, quick searches across directories. Supports internal (Explore) and external (Gemini/OpenCode) agents.
argument-hint	[search-target] [ext]
metadata	{"author":"claudekit","version":"1.0.0"}

Scout

Fast, token-efficient codebase scouting using parallel agents to find files needed for tasks.

Arguments

Default: Scout using built-in Explore subagents in parallel (./references/internal-scouting.md)
ext: Scout using external Gemini/OpenCode CLI tools in parallel (./references/external-scouting.md)

When to Use

Beginning work on feature spanning multiple directories
User mentions needing to "find", "locate", or "search for" files
Starting debugging session requiring file relationships understanding
User asks about project structure or where functionality lives
Before changes that might affect multiple codebase parts

Quick Start

Analyze user prompt to identify search targets
Use a wide range of Grep and Glob patterns to find relevant files and estimate scale of the codebase
Spawn parallel agents with divided directories
Collect results into concise report

Configuration

Read from .claude/.ck.json:

gemini.model - Gemini model (default: gemini-3-flash-preview)

Workflow

1. Analyze Task

Parse user prompt for search targets
Identify key directories, patterns, file types, lines of code
Determine optimal SCALE value of subagents to spawn

2. Divide and Conquer

Split codebase into logical segments per agent
Assign each agent specific directories or patterns
Ensure no overlap, maximize coverage

3. Register Scout Tasks

Skip if: Agent count ≤ 2 (overhead exceeds benefit)
Skip if: Task tools unavailable (VSCode extension) — use TodoWrite instead
TaskList first — check for existing scout tasks in session
If not found, TaskCreate per agent with scope metadata
See references/task-management-scouting.md for patterns and examples

4. Spawn Parallel Agents

Load appropriate reference based on decision tree:

Internal (Default): references/internal-scouting.md (Explore subagents)
External: references/external-scouting.md (Gemini/OpenCode)

Notes:

TaskUpdate each task to in_progress before spawning its agent (skip if Task tools unavailable)
Prompt detailed instructions for each subagent with exact directories or files it should read
Remember that each subagent has less than 200K tokens of context window
Amount of subagents to-be-spawned depends on the current system resources available and amount of files to be scanned
Each subagent must return a detailed summary report to a main agent

5. Collect Results

IMPORTANT: Invoke "/ck:project-organization" skill to organize the outputs.

Timeout: 3 minutes per agent (skip non-responders)
TaskUpdate completed tasks; log timed-out agents in report (skip if Task tools unavailable)
Aggregate findings into single report
List unresolved questions at end

Report Format

# Scout Report

## Relevant Files
- `path/to/file.ts` - Brief description
- ...

## Unresolved Questions
- Any gaps in findings

References

references/internal-scouting.md - Using Explore subagents
references/external-scouting.md - Using Gemini/OpenCode CLI
references/task-management-scouting.md - Claude Task patterns for scout coordination