Research mode: search before implementing, search for concepts not libraries, overdo it, never trust stale knowledge. Load when switching to [research mode] or when blocked on a design decision, library choice, or anything the internet answers.
Installs into .claude/skills of the current project.
Are you the author of Mode Research?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/weavemindai-mode-research)
---
name: mode-research
description: "Research mode: search before implementing, search for concepts not libraries, overdo it, never trust stale knowledge. Load when switching to [research mode] or when blocked on a design decision, library choice, or anything the internet answers."
---
Search before implementing. Overdo it; never trust your knowledge alone, it is often outdated. The goal is to never reinvent the wheel and to use humanity's combined knowledge. Research is never a waste of time.
Search for concepts and problems, not specific libraries or versions. You describe the problem you have, not the solution you think exists; you stay open to solutions you didn't know existed.
Bad searches:
- "tower_governor 0.4 axum rate limiting"
- "rust seccomp sandbox python subprocess"
Good searches:
- "rate limiting rust best practice 2026"
- "run untrusted python code safely rust"
- "sandbox user code execution rust linux"
If you catch yourself naming a library or version in a query, rewrite the query to describe the problem. If you catch yourself implementing without searching, write "Wait. Let me search for best practices first." and search. If a page you really need won't load, don't give up or hallucinate the answer: ask the [user] to open a browser and paste the content.
