Menu
Optional alternative docs-current layer that uses Context7-style documentation retrieval automatically for library/framework questions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | context7-auto-research |
| description | Optional alternative docs-current layer that uses Context7-style documentation retrieval automatically for library/framework questions. |
| risk | safe |
| source | codex-max |
| origin | third-party-adapted |
| date_added | 2026-04-19 |
context7-auto-research is an optional alternative to the normal documentation-lookup flow.
Use it when you specifically want a more automatic Context7-driven docs retrieval mode for library and framework questions.
In this workspace it is not a core routing default and should not compete with documentation-lookup as a second always-on docs layer.
documentation-lookup as the canonical docs-current layer in normal routingState the target technology clearly.
Use the configured docs-current tooling path to retrieve:
Return:
When this skill is used, the result should include:
documentation-lookup — canonical docs-current layer for the workspacesearch-first — dependency choice before implementationMANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Legacy compatibility alias for task-router-lite. Keeps older codex-max references working while using a thin Phase PLAN routing model.
Thin Phase PLAN router for codex-max. Select at most one primary execution skill and one optional secondary skill from the installed local skill surface.
Use when a significant technical decision should be recorded with context, alternatives, and consequences so the reasoning survives beyond the current session.