Source profileQuality 76/100

griffinwork40/agent-afk/src/bundled-plugins/awa-bundled/skills/gather/SKILL.md

gather

Parallel context-gathering for a code area. Use when you need to understand a module, feature, or subsystem and would otherwise read 3+ files sequentially — dispatches two agents in parallel to map structure and test coverage in one wave.

Source repository stars: 45
Declared platforms: 0
Static risk flags: 2
Last source update: 2026-07-28
Source checked: 2026-07-28

Decision Compatibility Install Workflow Permissions Evidence Source

Decision brief

What it does—and where it fits

You MUST emit exactly two agent tooluse blocks in a single response turn — both calls in the same assistant message, before either result arrives. Do not dispatch the second agent in a later turn after seeing the first agent's reply. Do not dispatch three agents. Do not dispatch…

Best for

Use when you need to understand a module, feature, or subsystem and would otherwise read 3+ files sequentially — dispatches two agents in parallel to map structure and test coverage in one wave.

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/griffinwork40/agent-afk --skill "src/bundled-plugins/awa-bundled/skills/gather"

Safe inspection promptEditorial

Inspect the Agent Skill "gather" from https://github.com/griffinwork40/agent-afk/blob/803066d4f1e0cd57e983658dc670d647fcd893c9/src/bundled-plugins/awa-bundled/skills/gather/SKILL.md at commit 803066d4f1e0cd57e983658dc670d647fcd893c9. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
Dispatch protocol
You MUST emit exactly two agent tooluse blocks in a single response turn — both calls in the same assistant message, before either result arrives. Do not dispatch the second agent in a later turn after seeing the first agent's reply. Do not dispatch three agents. Do not dispatch…
You MUST emit exactly two agent tooluse blocks in a single response turn — both calls in the same assistant message, before either result arrives. Do not dispatch the second agent in a later turn after seeing the first…Correct shape of your next response:If you find yourself about to send a single agent call and wait, stop — that is the failure mode this skill exists to prevent.
02
The two agents
When understanding a task requires reading multiple related files (imports, callers, tests, configs, types), dispatch these two — concurrently, per the protocol above:
Structure Agent (Explore, thoroughness matched to scope) — Find and read the target file(s), all direct imports, callers, and config references. Return:filesread: absolute paths examinedcallgraph: how components connect (one paragraph)
03
When NOT to use
You already know exactly which 1–2 files to read — just read them directly.
You already know exactly which 1–2 files to read — just read them directly.The task is a simple grep or symbol lookup — use Grep or Glob.You're mid-edit and need to check one adjacent file — a single Read is fine.

Permission review

Static risk signals and limitations

Reads files

low · line 20

The documentation asks the agent to read local files, directories, or repositories.

**Structure Agent** (Explore, thoroughness matched to scope) — Find and read the target file(s), all direct imports, callers, and config references. Return:

Writes files

medium · line 37

The documentation asks the agent to create, modify, or delete local files.

You're mid-edit and need to check one adjacent file — a single Read is fine.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	76/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	45	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: griffinwork40/agent-afk
Skill path: src/bundled-plugins/awa-bundled/skills/gather/SKILL.md
Commit: 803066d4f1e0cd57e983658dc670d647fcd893c9
License: Apache-2.0
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

Dispatch protocol

You MUST emit exactly two agent tool_use blocks in a single response turn — both calls in the same assistant message, before either result arrives. Do not dispatch the second agent in a later turn after seeing the first agent's reply. Do not dispatch three agents. Do not dispatch one.

Correct shape of your next response:

<assistant turn>
  <tool_use name="agent" id="…"> Structure Agent prompt </tool_use>
  <tool_use name="agent" id="…"> Test Agent prompt </tool_use>
</assistant turn>

If you find yourself about to send a single agent call and wait, stop — that is the failure mode this skill exists to prevent.

The two agents

When understanding a task requires reading multiple related files (imports, callers, tests, configs, types), dispatch these two — concurrently, per the protocol above:

Structure Agent (Explore, thoroughness matched to scope) — Find and read the target file(s), all direct imports, callers, and config references. Return:
- files_read: absolute paths examined
- call_graph: how components connect (one paragraph)
- public_interfaces: function signatures, types, or contracts that govern the area
- entry_points: where control flow enters
Test Agent (Explore, "medium") — Find test files that exercise the target area, read them, identify what paths are covered and what's missing. Return:
- test_files: absolute paths of relevant tests
- coverage_summary: what behaviors/branches tests exercise
- untested_paths: code paths with no test coverage

When both return, merge into a unified context map. If either agent's output has gaps (e.g., Structure Agent missed config, Test Agent found no tests), issue one targeted follow-up Read — do not re-dispatch.

When NOT to use

You already know exactly which 1–2 files to read — just read them directly.
The task is a simple grep or symbol lookup — use Grep or Glob.
You're mid-edit and need to check one adjacent file — a single Read is fine.

Alternatives

Compare before choosing

Computed 10042,015

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 1007

event4u-app/agent-config

testing-anti-patterns

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

Computed 997

event4u-app/agent-config

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

Computed 987

event4u-app/agent-config

pest-testing

Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.