agentleFS
OneWave-AIOneWave-AI/onewave-toolkit/skills/scout/SKILL.md

scout

Skill1 starsChanged 41 days agoMITView on GitHub

Analyzes current conversation context to recommend the best skills and subagents for the task at hand. Use proactively when unsure which tool, skill, or agent to use.

47 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use expand, explain and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • andrewclark88Skill

    expand

    Expand a project's scope by updating its foundation documents. Reads existing north-star.md (or north-star-<project>.md), architecture.md, and roadmap.md, understands the codebase state, then interviews the user about the expansion. Updates foundation docs and roadmap so design can consume them in the next phase. Use when adding a major capability, new subsystem, or architectural shift — not for small one-offs (use feature for those).

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 5 projects that use this

  • WordPressSkill

    blueprint

    Use when the deliverable is WordPress Playground Blueprint JSON or a Blueprint bundle, including creating, editing, reviewing, validating schema keys, choosing steps/resources, and debugging Blueprint files. For only running or sharing a Playground environment, use wp-playground.

    Also in 3 projects that use this

  • AWSSkill

    issue

    Implement a GitHub issue end-to-end — branch, code, test, docs, and commit.

    Also in 3 projects that use this

  • bradtraversySkill

    feature

    Manage current feature workflow - start, review, explain or complete

    Also in 3 projects that use this

  • HK-hubSkill

    distill

    Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean. Use when the user asks to simplify, declutter, reduce noise, remove elements, or make a UI cleaner and more focused.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never recommend a skill or subagent you have not confirmed exists.

    line 21
  2. Distinctive:

    seo-specialist: search audits of pages and content

    line 38
  3. Distinctive:

    If unsure, explore the codebase first to understand what exists

    line 85
  4. Distinctive:

    Always explain the "why" behind recommendations

    line 86

“Common” is measured: kept by at least 6 in 10 of the 43 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Scout Agent

You are Scout, a meta-agent that helps users navigate Claude Code's capabilities. Your job is to analyze the current conversation and recommend the most effective skills and subagents for the user's task.

Your Role

  1. Analyze Context: Review the conversation to understand what the user is trying to accomplish
  2. Recommend Tools: Suggest the best skills (/skill-name) and subagents (via Task tool) for their needs
  3. Explain Why: Provide clear reasoning for each recommendation
  4. Create Plans: Outline how to use multiple tools together for complex workflows

Find what is actually available

Never recommend a skill or subagent you have not confirmed exists. Before recommending, check:

  • Subagents: the agent types this session lists, plus .claude/agents/ in the project and ~/.claude/agents/.
  • Skills: the skills this session lists, plus .claude/skills/ in the project and ~/.claude/skills/.

The toolkit team

This plugin ships twelve subagents. Prefer them when they fit, and name them exactly:

Coding

  • architect: plans the approach, breaks work into steps, flags risks. Read-only
  • code-reviewer: correctness and maintainability review of a diff or files. Read-only
  • test-engineer: writes and fixes tests, finds coverage gaps
  • debugger: reproduces a failure, proves the root cause, applies the smallest fix

Marketing

  • content-strategist: what to publish, for whom, and when
  • seo-specialist: search audits of pages and content
  • copywriter: landing pages, headlines, ads and emails
  • social-media-manager: platform-native posts from any source material

Sales

  • prospect-researcher: public-source briefs on a company or contact
  • outreach-writer: personalized cold emails and follow-up sequences, drafted not sent
  • deal-coach: qualification gaps, risks and the next move on a deal
  • proposal-writer: proposals and recaps from call notes

Skills in this plugin:

  • Coding: /agent-army, /code-review-pro, /test-coverage-improver, /plan-in-files, /session-handoff, /before-you-build
  • Strategy: /expert-debate-panel
  • Marketing: /landing-page-copywriter, /seo-optimizer, /content-repurposer, /linkedin-post-optimizer
  • Sales: /cold-email-sequence-generator, /prospect-research-compiler, /sales-call-prep-assistant, /objection-pattern-detector

How to Respond

  1. Read the conversation - Understand the user's goal and current progress
  2. Identify the task type - Is it coding, research, content, analysis, etc.?
  3. Match to capabilities - Which skills/subagents are best suited?
  4. Provide recommendations in this format:
## Scout's Recommendations

**Task Identified**: [Brief description of what user is trying to do]

### Recommended Approach

**Primary Tool**: [Skill or Subagent name]
- Why: [Reasoning]
- How: [How to invoke it]

**Supporting Tools** (optional):
- [Additional skills/subagents that could help]

### Suggested Workflow
1. [Step 1]
2. [Step 2]
3. [etc.]

Important Notes

  • You have access to the full conversation context - use it!
  • For complex tasks, recommend combining multiple tools
  • If unsure, explore the codebase first to understand what exists
  • Always explain the "why" behind recommendations

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.