From anycap
Guide for conducting thorough, multi-source research and producing comprehensive, well-sourced reports. Powered by AnyCap -- the capability runtime that equips AI agents with web search (including AI Grounded citations), web crawl, image generation, cloud storage, and one-click web publishing through a single CLI. Use when the user asks for deep research, competitive analysis, market research, technical deep dive, literature review, technology comparison, or any task requiring multi-source information gathering and synthesis. Also use when users say "investigate", "survey the landscape", "compare X vs Y", "state of the art", "write a report on", "look into", "find out about", "analyze the market", or any inquiry that needs more than a single search. Trigger on mentions of research, analysis, investigation, comparison, report, survey, or deep dive.
How this skill is triggered — by the user, by Claude, or both
Slash command
/anycap:anycap-deepresearchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Read this entire file before starting.** It defines the multi-source research workflow from planning through synthesis.
Read this entire file before starting. It defines the multi-source research workflow from planning through synthesis.
Conduct thorough, multi-source research on any topic. Gather information broadly, verify claims rigorously, and synthesize findings into a polished, well-sourced report.
Think deeply. Search broadly. Verify everything. Deliver clearly.
Read all five reference files before taking any action. Understanding the full process prevents wasted effort and ensures thorough research.
For detailed CLI command usage (flags, output formats, jq patterns), refer to the anycap-cli skill and its references.
anycap CLI installed and authenticated (anycap status to verify)Follow the research process below. User clarification is mandatory -- do not skip it.
graph LR
A["Preliminary Search<br/>(optional)"] --> B[Clarify with User]
B --> C[Plan]
C --> D[Gather]
D --> E[Analyze]
E --> F[Synthesize]
F --> G[Deliver]
E -->|gaps found| D
The process starts with an optional preliminary search to build context, followed by a mandatory clarification with the user, then autonomous execution.
Each phase has detailed guidance in the references:
This skill involves the user at key decision points:
anycap actions image-read) before including them in the report. See 04-synthesize.md.Do not skip the initial clarification. A 2-minute conversation with the user can save an hour of misguided research.
Once research begins (Phase 2 onward), work autonomously. Do not interrupt the user with questions during gathering, analysis, or synthesis. Make your best judgment based on the preferences established in Phase 1. If you encounter ambiguity, note it in your research journal and resolve it with the best available evidence.
Be thorough, not frugal. Use as many searches and crawls as needed to produce a comprehensive report. Breadth and depth of research determine report quality.
Save everything. Write intermediate results (search outputs, crawled pages, grounding responses, notes) to local files. These are your evidence base for cross-verification and sourcing.
Verify, do not assume. Cross-check important claims across multiple independent sources. When sources conflict, investigate further rather than picking one.
Search in parallel. When sub-questions are independent, run multiple searches concurrently rather than sequentially. This produces results faster and gives you more material to cross-reference.
Prefer AI Grounded search for complex questions. Grounding search (--prompt) synthesizes across multiple sources and provides citations. Use it generously for questions that benefit from multi-source synthesis. Use general search (--query) for finding specific pages and data points.
Use mermaid for diagrams. When the report needs architecture diagrams, flow charts, timelines, or comparisons, use mermaid syntax in markdown. Both Drive and Page render mermaid natively. Always verify mermaid diagrams render correctly before including them in the final report (see 04-synthesize.md).
Prefer original images. When a source provides relevant images, diagrams, or screenshots, download and use the originals. Only generate images when you need to explain a concept, aggregate data into a visualization, or express information more clearly than the source material. Generated images must not misrepresent or deviate from the source material.
| Tool | Purpose |
|---|---|
anycap search --query "..." | Find pages on a topic |
anycap search --query "..." --no-crawl | Fast scan: titles and URLs only |
anycap search --prompt "..." | AI Grounded answer with citations |
anycap crawl <url> | Read a web page as Markdown |
anycap image generate ... | Create explanatory illustrations |
anycap drive upload ... | Store files in the cloud |
anycap drive share ... | Generate a shareable link |
anycap page deploy ... | Publish as a web page |
npx claudepluginhub anycap-ai/anycap --plugin anycapGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.