Behavioral skill that triggers automatic web searches when stuck on a problem. Activates when Claude encounters an error it cannot resolve, an unfamiliar API, a deprecation warning, a version mismatch, or any situation where general knowledge is insufficient. Also triggers for "search for a fix", "look this up", "find the docs", "why is this failing", or when the user asks Claude to be more resourceful about finding answers. This skill should run in the background of every coding session.
npx claudepluginhub oliverames/ames-claude --plugin ames-standalone-skillsThis skill uses the workspace's default tool permissions.
Search the web WITHOUT being asked when any of these conditions are met:
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Search the web WITHOUT being asked when any of these conditions are met:
Use context7 MCP (resolve-library-id then query-docs) for any library,
framework, or SDK question. This returns current, authoritative documentation.
Use WebSearch for:
Use gemini -m gemini-3-flash-preview -p "..." --yolo via Bash for:
Use WebFetch to read a specific URL when you already know where the answer is
(GitHub issue, documentation page, Stack Overflow thread).
When you search automatically, briefly note what triggered it:
Searched: [what you looked for]
Found: [one-line summary of the answer]
Do NOT ask permission to search. Do NOT announce you're about to search. Just search, find the answer, and apply it. Report what you found inline.
Searching is not a sign of weakness; guessing is. A wrong answer delivered confidently wastes more time than a 5-second web search. When in doubt, look it up. The user's CLAUDE.md explicitly says: "When unsure if an API or tool supports a capability, always test it before declaring it impossible."