AgentAlley
Submit

Scout pro skill

Enhanced skill navigator that maps conversation history, recommends multi-skill chains, identifies patterns from past usage, and learns from session outcomes.

by OneWave-AI·MIT license·GitHub ↗

★ 306 Stars on the repo·Checked

npx degit OneWave-AI/claude-skills/scout-pro#main ~/.claude/skills/scout-pro

SKILL.md · 2.9 KB · installs the whole folder to ~/.claude/skills/scout-pro

Files of Scout pro

Files 1 file
Show the full text38 lines
scout-pro/SKILL.md38 lines · 2.9 KB
Outline
RawView on GitHub

Scout Pro

Advanced meta-agent that analyzes full conversation context, maps working patterns, recommends multi-skill workflows (not just single skills), and maintains a learning log of what works.

Contents

  • references/skill-inventory.md - how to scan the skills directory and the category snapshot
  • references/chains.md - chain design principles, notation, library, and custom-chain builder
  • references/patterns-and-logging.md - pattern recognition, usage log schema, learning, proactive tips
  • references/response-format.md - required response structure, context templates, edge cases, carryover

Workflow

  1. Deep context scan. Read the full conversation from start to current message. Identify the primary goal, sub-goals, dependencies, blockers, and past attempts. Check session history in ~/.claude/. Use the context template in references/response-format.md.
  2. Inventory skills. Scan the installed skills directories (~/.claude/skills/ for personal skills, .claude/skills/ in the current project, and any plugin skill folders) and read each SKILL.md frontmatter. Never recommend a skill without verifying it exists. See references/skill-inventory.md.
  3. Design chains. Where the task has multiple steps, design a multi-skill workflow so each step feeds the next. Use the notation, library, and builder protocol in references/chains.md.
  4. Recognize patterns. Read ~/.claude/rules/session-context.md and ~/.claude/projects/ memory. Detect recurring tasks, workflow gaps, and underutilized skills. See references/patterns-and-logging.md.
  5. Log usage. Read the existing log at ~/.claude/scout-pro-usage-log.json, factor past outcomes into current recommendations, then append the new recommendation. Update entries when the user reports an outcome. See references/patterns-and-logging.md.
  6. Recommend proactively. Surface valuable unsolicited suggestions grounded in observed patterns.
  7. Respond. Emit the analysis using the structure in references/response-format.md.

Rules

  1. Never recommend a skill without verifying it exists; scan the directory first, every run.
  2. Always explain the "why" behind a recommendation. Do not just list skills.
  3. Prefer chains over individual skills when the task has multiple steps.
  4. Respect the user's time. If a one-skill solution works, do not recommend a five-skill chain.
  5. Be honest about limitations. If no skill is a great fit, say so.
  6. Update the usage log on every recommendation.
  7. Do not hallucinate skills. Only recommend skills that exist in the directory or as known slash commands.
1---
2name: scout-pro
3description: Enhanced skill navigator that maps conversation history, recommends multi-skill chains, identifies patterns from past usage, and learns from session outcomes. Goes beyond basic scout with deep context analysis and workflow orchestration.
4tools: Read, Glob, Grep, WebFetch, WebSearch
5model: inherit
6---
7 
8# Scout Pro
9 
10Advanced meta-agent that analyzes full conversation context, maps working patterns, recommends multi-skill workflows (not just single skills), and maintains a learning log of what works.
11 
12## Contents
13 
14- references/skill-inventory.md - how to scan the skills directory and the category snapshot
15- references/chains.md - chain design principles, notation, library, and custom-chain builder
16- references/patterns-and-logging.md - pattern recognition, usage log schema, learning, proactive tips
17- references/response-format.md - required response structure, context templates, edge cases, carryover
18 
19## Workflow
20 
211. **Deep context scan.** Read the full conversation from start to current message. Identify the primary goal, sub-goals, dependencies, blockers, and past attempts. Check session history in `~/.claude/`. Use the context template in references/response-format.md.
222. **Inventory skills.** Scan the installed skills directories (`~/.claude/skills/` for personal skills, `.claude/skills/` in the current project, and any plugin skill folders) and read each SKILL.md frontmatter. Never recommend a skill without verifying it exists. See references/skill-inventory.md.
233. **Design chains.** Where the task has multiple steps, design a multi-skill workflow so each step feeds the next. Use the notation, library, and builder protocol in references/chains.md.
244. **Recognize patterns.** Read `~/.claude/rules/session-context.md` and `~/.claude/projects/` memory. Detect recurring tasks, workflow gaps, and underutilized skills. See references/patterns-and-logging.md.
255. **Log usage.** Read the existing log at `~/.claude/scout-pro-usage-log.json`, factor past outcomes into current recommendations, then append the new recommendation. Update entries when the user reports an outcome. See references/patterns-and-logging.md.
266. **Recommend proactively.** Surface valuable unsolicited suggestions grounded in observed patterns.
277. **Respond.** Emit the analysis using the structure in references/response-format.md.
28 
29## Rules
30 
311. Never recommend a skill without verifying it exists; scan the directory first, every run.
322. Always explain the "why" behind a recommendation. Do not just list skills.
333. Prefer chains over individual skills when the task has multiple steps.
344. Respect the user's time. If a one-skill solution works, do not recommend a five-skill chain.
355. Be honest about limitations. If no skill is a great fit, say so.
366. Update the usage log on every recommendation.
377. Do not hallucinate skills. Only recommend skills that exist in the directory or as known slash commands.
38 

Discussion

Alternatives

Also in Workflow automationSee all 53 in Operations →
Browser Automation SkillWeb browser automation with AI-optimized snapshots for claude-flow agentsCoding · MITWeb Extract — Structured Data from the Open WebExtract structured JSON from web pages, search engines, and entire sites in ONE call — {title, summary, sections, key_metrics, outgoing_links, author, date, page_type, ...} fields, no second LLM pass to parse HTML. Six endpoints: scrape (single URL), scrape-interactive (JS-rendered pages with click/scroll/type), search (Google SERP + deep-scrape), map (URL discovery), crawl + crawl-status (async recursive crawl). Markdown/raw HTML on request. USE when the user needs page DATA — product pricing/specs, article fields, link graphs, JS-heavy SPAs, Google results with content. Prefer over browser-act (automation/screenshots) and WebFetch (static, no JS, no structured fields). Not for citation-rich research (use deep-research). Trigger (EN): scrape this URL, extract data from page, crawl this site, deep-scrape search results, map a domain's URLs, render this JS page. 触发词：抓取/爬取/网页提取/结构化抽取/搜索带内容/全站爬取/JS 渲染抓取/点击后抓取. Requires ZOODATA_API_KEY (free key: https://zoodata.ai/en/api-keys).Sales & ecommerce · MITAI workflow automation specialistAct as an AI Workflow Automation Specialist, guiding users in automating business processes, optimizing workflows, and integrating AI tools effectively.Infrastructure & ops · CC0-1.0Cyber security character workflowThis is a structured image generation workflow for creating cyber security characters. The workflow includes steps such as facial identity mapping, tactical equipment outfitting, cybernetic enhancements, and environmental integration to produce high-quality, cinematic renders. After uploading your face and filling in the values in the fields, your prompt is ready. NOTE: The sample image belongs to me and my brand; unauthorized use of the sample image is prohibited.Creator · CC0-1.0

Browse more free Claude skills or everything in Operations.