inspire

Researches external sources via WebSearch and WebFetch to inform design and architecture decisions.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill inspire-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inspire
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/lifeline/skills/inspire
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill inspire-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing unfamiliar domains, new frameworks, or design decisions with multiple valid directions, relying on model memory alone risks outdated or incomplete answers. This Skill performs structured online research so decisions are grounded in what actually exists and how others solve the problem. ## Core Features & Use Cases - Adaptive research depth: Quick (1-2 rounds), Normal (2-4), or Deep (4-8) search rounds, with automatic escalation when findings contradict each other. - Dual research tools: WebSearch for broad exploration of unfamiliar territory and WebFetch for targeted reading of documentation, GitHub discussions, blog posts, and forum threads. - Three output modes: Absorb findings silently into the work, Discuss options ranked by end-result quality, or Challenge the current direction when research surfaces risks or anti-patterns. - Use Case: Before choosing a state management approach for a new app, trigger the skill to survey community consensus, compare trade-offs from real-world write-ups, and present the strongest options with sources. ## Quick Start Ask the agent to research how other teams handle a problem you are facing, for example by saying "research what approaches exist for this design decision before we commit".

Frequently Asked Questions about inspire

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research existing solutions before starting a new design?▼

Trigger the skill with a topic or let it detect unfamiliar territory automatically. It runs WebSearch for broad exploration and WebFetch for deep reading of docs, GitHub discussions, and blog posts, then presents options ranked by end-result quality.

When should I use web research versus relying on model knowledge?▼

Use research whenever you face unfamiliar frameworks, evaluative architecture questions, or doubt about a claim. The skill treats uncertainty itself as the signal to search, since model knowledge may miss current libraries, community patterns, and known pitfalls.

How does the skill decide how deep to research a topic?▼

Depth is set by complexity and user signals: Quick uses 1-2 search rounds for factual questions, Normal uses 2-4 for design questions, and Deep uses 4-8 for complex domains. Depth escalates automatically when early results contradict each other.

When should I not trigger external web research?▼

Skip research for routine work in familiar domains, questions purely about your own codebase, or when you explicitly prioritize speed. The skill checks the local codebase first with Grep and Glob before searching externally.

Does the research skill work inside plan mode?▼

Yes. In plan mode, findings are included as a context section within the plan rather than standalone output. Outside plan mode, results are applied directly or presented as a discussion depending on the output mode.