القائمة
Use when any research, search, or information gathering is needed.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | research |
| description | Use when any research, search, or information gathering is needed. |
Deep/current/external branch of the unified lev find story.
Use lev find first for local repo/operator truth.
Use lev-research when:
Implementation surface: plugins/timetravel with root Poly bindings over core-timetravel.
Use lev research as the northbound runtime surface. lev timetravel remains the
underlying runtime/compat surface.
lev research --help
When published to npm, this becomes:
npx @lev-os/lev research --help
Run that command to see available subcommands, strategies, adapters, and options. The CLI is the documentation. Do not duplicate its interface here.
lev find / agent-native tools, not this skilldeep, max, and academic, first build a short research prompt package:
objective, audience, scope, known context, sub-questions, evidence contract, and output contract.
Use the deep research prompt contract below and the runtime strategy metadata
in plugins/timetravel/src/strategy.ts.
Historical lev research outputs and generated results are AutoWiki intake
material, not canonical guidance. Treat them as raw sources for the wiki
projection unless they have been source-reviewed and promoted.lev research "<query>" -s <strategy> --prompt-plan-onlylev research "<query>" -s <strategy> --flow=deep-research --flow-plan-only
first, then remove --flow-plan-only when a bounded FlowMind run is desired.research-route: <strategy> | lev research -s <strategy>lev research "<query>" -s <strategy> via Bash. Prompt planning is
default-on for deep, max, and academic; completed runs wikify by
default into the project AutoWiki raw layer. Use --no-prompt-plan only
when terse output is required and --no-wikify only when the run must not
touch wiki intake.web_search, WebSearch, browser/search MCP, or equivalent). Do not stop at Sources: 0.research-route: <strategy> | lev research -s <strategy> | fallback: internet-search (<reason>)lev research is the preferred router, not a blocker. The job of this skill is live research. When the router cannot produce URLs, use whatever internet search capability is available in the current agent runtime.
Minimum fallback behavior:
Deep research quality depends on the input contract. Before running deep, max,
or academic, compress the user request into:
Objective: one precise research question.
Audience: who will use the answer and what decision it supports.
Scope: timeframe, geography, domains, source classes, exclusions.
Known context: assumptions, prior decisions, baseline facts, or files.
Sub-questions: 3-7 focused queries that can be searched independently.
Evidence contract: source quality, recency, citation, and contradiction rules.
Output contract: structure, confidence labels, limits, and open questions.
Provider-specific rules belong in the runtime strategy metadata and AutoWiki intake/projection, not in this skill directory. If provider behavior matters, verify against current provider docs and cite the URLs you used.
| Signal Words | Strategy |
|---|---|
| "search", "lookup", "find", "what is" | quick |
| "twitter", "reddit", "trending", "sentiment" | social |
| "paper", "arxiv", "academic", "scholarly" | academic |
| "research", "deep", "comprehensive", "analyze", "compare", "investigate" | deep |
| "complete analysis", "exhaustive", "all angles" | max |
Ambiguous? Default to quick.
| Don't | Why |
|---|---|
| Use this skill for ordinary repo search | lev find is the local retrieval primitive |
Use direct internet search as the first step when lev research is healthy | Keep the router as the primary path so adapter logs and strategy selection remain consistent. |
| Spawn subagents to search | Timetravel handles parallelism internally. |
| Duplicate strategy/adapter definitions | Source of truth is plugins/timetravel/src/strategy.ts. |
Stop after Sources: 0 | No URLs from the router means use internet-search fallback, not no answer. |
| Answer from training data | No URLs = no answer. Call the CLI, then internet-search fallback if needed. |
| Treat synthesis-only output as sourced | Some providers synthesize without URLs; verify with source-bearing adapters or fallback search. |
Routes adaptive multi-agent deliberation with fractal context cycles. Use when using /cdo, think/deep/debug/parliament work, or long runs paired with autoresearch scheduling.
Use when you need an evidence-first provenance report from `cass`, repo docs, `.lev`, `~/.agents/diagrams`, `qmd`, or Grep/Glob tools.
Use the codebase knowledge graph for structural code queries. Triggers on: explore the codebase, understand the architecture, what functions exist, show me the structure, who calls this function, what does X call, trace the call chain, find callers of, show dependencies, impact analysis, dead code, unused functions, high fan-out, refactor candidates, code quality audit, graph query syntax, Cypher query examples, edge types, how to use search_graph.
Handle blocked destructive commands. Use when dcg blocks rm -rf, git reset --hard, DROP DATABASE, kubectl delete, or when configuring agent safety guardrails.
Use when running a visible Lev autopilot that coordinates research, interview, arch, propose, AgentPing, warm-worker intent, realtime dashboard intent, and lev exec updates across the lifecycle.
Heartbeat-driven autonomous development loop using lev loop autodev, with interval, budget, and tick controls for in-process SDLC execution.