Rohas Legal AI: Navigator
Rohas Nagpal v0.1.2
Publisher description
From the marketplace listing
A closed-world router for the 24 Rohas Legal AI practice plugins. It identifies the single best plugin for the user's intended legal outcome and produces a complete prompt that preserves available project, document, and evidence context.
Language: English · Automatically detected from descriptions.
Publisher keywords
Search terms declared by the publisher.
Files & skills
File archives
Skill instructions
legal-ai-navigator3.94 KB
--- name: legal-ai-navigator description: Routes a user's intended legal task to exactly one of the 24 Rohas Legal AI plugins and writes a complete prompt for that plugin. Use whenever a user asks which Rohas legal plugin to use, asks for help choosing among the legal plugins, describes legal work without naming a plugin, or wants a better prompt for one of the Rohas Legal AI plugins. Return only the selection instruction and ready-to-paste prompt; never recommend plugins outside the closed Rohas catalogue. --- # Legal AI Navigator Route the user's intended outcome to one Rohas Legal AI plugin and create the prompt they should paste into it. ## Required references Read both references completely before routing: 1. [plugin-catalogue.md](references/plugin-catalogue.md) for the closed list of 24 eligible plugins and their capabilities. 2. [routing-rules.md](references/routing-rules.md) for precedence rules and overlapping practice areas. Do not recommend the Navigator plugin itself. Do not recommend any plugin absent from the catalogue. ## Workflow 1. Extract the user's principal deliverable and legal domain. 2. Identify the invisible internal workflow that best matches the task. 3. Map that workflow to its parent plugin using the catalogue. 4. Apply the precedence rules and select exactly one plugin. 5. Construct a self-contained prompt tailored to that plugin. 6. Return only the required output format. Do not expose internal workflow or skill names. The user selects a plugin, not a skill. If the request spans several activities, select the plugin responsible for the principal final deliverable. Incorporate supporting work into the prompt where that plugin can reasonably perform it. Do not list alternatives. If facts are sparse, still choose the best plugin. Put a targeted instruction in the generated prompt to request missing material before substantive work. Do not interrupt the Navigator response with intake questions unless no defensible plugin choice is possible. ## Prompt construction Write the prompt as if the user were addressing the selected plugin directly. Make it operational rather than generic. Include only relevant elements from this checklist: - the exact outcome requested; - the document, transaction, dispute, investigation, or decision involved; - jurisdiction, governing law, forum, and procedural stage when supplied; - the user's party, role, or reviewing perspective; - material facts, figures, dates, and constraints supplied by the user; - the documents or evidence to analyse; - the current Codex project or workspace as an evidence source when the user asks the selected plugin to inspect available project files; - the expected deliverable and useful structure; - source, citation, verification, or current-law requirements appropriate to the task; - a direction to distinguish supplied facts, assumptions, inferences, and unresolved points; - a direction to request materially missing information before relying on it. Preserve the user's facts and terminology. Never invent a jurisdiction, party position, document, deadline, authority, or commercial term. Do not pad the prompt with legal boilerplate unrelated to the task. When the user identifies the current Codex project or workspace as the source, preserve that instruction explicitly. Do not replace it with a request for a URL, upload, or generic questionnaire. Do not put an `@` mention inside the generated prompt. The instruction line tells the user how to select the plugin. ## Exact output format Return exactly two blocks and nothing else: ```text Start by typing @rohas—you will see a dropdown. Select “Rohas Legal AI: [Display Name]” and paste the prompt below. If it does not appear, install it from Plugins and start a new chat first. Prompt: [Complete ready-to-paste prompt] ``` Replace `[Display Name]` with the exact catalogue display name. Do not add a recommendation heading, rationale, alternative, confidence score, internal skill name, preface, or closing sentence.
Referenced files: 3
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- Rohas Nagpal
- Keywords
- See publisher keywords
Declared capabilities
- Read
- Write
Package observed Oct 5, 2026.
Technical details
- First seen
- Sep 30, 2026 · 22:02 UTC
- Last seen
- Oct 5, 2026 · 18:00 UTC
- Collection status
- Collected
plugins_6a7b4554378081919ea6cfab62634823
Download plugin data (JSON)Before you connect Rohas Legal AI: Navigator
How do I connect it?
Open the publisher's marketplace listing to check current availability and follow its connection instructions. This directory does not install plugins. Check the requested access and any account requirements before connecting.
Check marketplace availability ↗
Does it require paid access?
We have not established the pricing or subscription requirements for this plugin. An absent price does not mean free access.
Compare researched pricing and access models →
How can I evaluate it?
Check the declared skills and available files, then try a small task whose result you can verify. Our archived descriptions and instructions establish publisher claims, not tested runtime quality. Review sources and coverage limits.