How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

help - Prompt - OpenSmartRoute

Name: help
Author: matryer

Prompt file imported from matryer/context (.cursor/commands/help.md). Copyright stays with the author.

Help Command

Command: `help`

Show an overview of this Context repository and what the user can do.

Steps

Show current directory structure

Run:
```
.context/scripts/print_dir_structure.sh
```
Load the glossary

Read /GLOSSARY.md to understand domain-specific terms.
Present the overview

Display the information below, adapting based on what exists in the repo.
Offer next steps
- If empty (no /projects/ or /people/ folders): suggest setup
- If populated: suggest ingest or ask questions

Context Knowledgebase

A structured repository for tracking projects, people, and progress.

Commands

Command	Description
`setup`	Initialize folder structure, add people/projects, configure glossary
`ingest`	Transform free text (meeting notes, Slack, emails) into structured knowledge
`ask`	Run a predefined question from `/questions/` (e.g., `ask team-overview`)
`report`	Run a predefined report from `/reports/` (e.g., `report weekly-summary`)
`help`	Show this overview

Structure

/projects/:name/README.md                 # Project overview
/projects/:name/work/:item.md             # Task details  
/projects/:name/progress/:year/:month.md  # Monthly updates
/people/:team/:person.md                  # Person profiles
/questions/:name.md                       # Predefined questions
/reports/:name.md                         # Predefined reports
/GLOSSARY.md                              # Domain terms

What You Can Track

Projects: Progress updates · Work items · Ideas and proposals

People: Current focus · Wins and achievements · Ideas · Interests · Team and role

Examples

Ask: "What is Sarah working on?" · "Show progress on API Gateway" · "Who's interested in Rust?"

Do: "Record that Marcus shipped auth" · "Create project Dashboard Redesign" · "Move Sarah to Platform team"

Ingestion

The ingest command transforms unstructured text into knowledge:

Meeting notes → Progress entries with dates and attribution
Slack threads → Updates to relevant projects and people
Status updates → Wins, current focus, and interests

Just paste your content and run ingest — it extracts names, projects, dates, and achievements automatically.

Utility Scripts

Script	Purpose
`print_datetime.sh`	Get current date/time for entries
`print_dir_structure.sh`	Show folder structure
`random_project.sh`	Pick a random project to review
`random_person.sh`	Pick a random person to review

Tips

README.md files — Every folder has one for navigation
Cross-linking — Projects and people reference each other
Attribution — Include @username when recording who did what
Dates — All entries include dates for tracking

Guidelines

Keep output scannable with tables and bullets
Show actual directory structure from script output
Be concise but comprehensive
Tailor suggestions based on what exists in the repo

Install help and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Help Command ## Command: `help` Show an overview of this Context repository and what the user can do. ### Steps 1. **Show current directory structure** Run: ```bash .context/scripts/print_dir_structure.sh ``` 2. **Load the glossary** Read `/GLOSSARY.md` to understand domain-specific terms. 3. **Present the overview** Display the information below, adapting based on what exists in the repo. 4. **Offer next steps** - If empty (no `/projects/` or `/people/` folders): suggest `setup` - If populated: suggest `ingest` or ask questions --- ## Context Knowledgebase A structured repository for tracking projects, people, and progress. ### Commands | Command | Description | |---------|-------------| | `setup` | Initialize folder structure, add people/projects, configure glossary | | `ingest` | Transform free text (meeting notes, Slack, emails) into structured knowledge | | `ask` | Run a predefined question from `/questions/` (e.g., `ask team-overview`) | | `report` | Run a predefined report from `/reports/` (e.g., `report weekly-summary`) | | `help` | Show this overview | ### Structure ``` /projects/:name/README.md # Project overview /projects/:name/work/:item.md # Task details /projects/:name/progress/:year/:month.md # Monthly updates /people/:team/:person.md # Person profiles /questions/:name.md # Predefined questions /reports/:name.md # Predefined reports /GLOSSARY.md # Domain terms ``` ### What You Can Track **Projects:** Progress updates · Work items · Ideas and proposals **People:** Current focus · Wins and achievements · Ideas · Interests · Team and role ### Examples **Ask:** "What is Sarah working on?" · "Show progress on API Gateway" · "Who's interested in Rust?" **Do:** "Record that Marcus shipped auth" · "Create project Dashboard Redesign" · "Move Sarah to Platform team" --- ### Ingestion The `ingest` command transforms unstructured text into knowledge: - **Meeting notes** → Progress entries with dates and attribution - **Slack threads** → Updates to relevant projects and people - **Status updates** → Wins, current focus, and interests Just paste your content and run `ingest` — it extracts names, projects, dates, and achievements automatically. ### Utility Scripts | Script | Purpose | |--------|---------| | `print_datetime.sh` | Get current date/time for entries | | `print_dir_structure.sh` | Show folder structure | | `random_project.sh` | Pick a random project to review | | `random_person.sh` | Pick a random person to review | ### Tips - **README.md files** — Every folder has one for navigation - **Cross-linking** — Projects and people reference each other - **Attribution** — Include `@username` when recording who did what - **Dates** — All entries include dates for tracking ### Guidelines - Keep output scannable with tables and bullets - Show actual directory structure from script output - Be concise but comprehensive - Tailor suggestions based on what exists in the repo

{ "prompt": "# Help Command\n\n## Command: `help`\n\nShow an overview of this Context repository and what the user can do.\n\n### Steps\n\n1. **Show current directory structure**\n \n Run:\n ```bash\n .context/scripts/print_dir_structure.sh\n ```\n\n2. **Load the glossary**\n \n Read `/GLOSSARY.md` to understand domain-specific terms.\n\n3. **Present the overview**\n \n Display the information below, adapting based on what exists in the repo.\n\n4. **Offer next steps**\n \n - If empty (no `/projects/` or `/people/` folders): suggest `setup`\n - If populated: suggest `ingest` or ask questions\n\n---\n\n## Context Knowledgebase\n\nA structured repository for tracking projects, people, and progress.\n\n### Commands\n\n| Command | Description |\n|---------|-------------|\n| `setup` | Initialize folder structure, add people/projects, configure glossary |\n| `ingest` | Transform free text (meeting notes, Slack, emails) into structured knowledge |\n| `ask` | Run a predefined question from `/questions/` (e.g., `ask team-overview`) |\n| `report` | Run a predefined report from `/reports/` (e.g., `report weekly-summary`) |\n| `help` | Show this overview |\n\n### Structure\n\n```\n/projects/:name/README.md # Project overview\n/projects/:name/work/:item.md # Task details \n/projects/:name/progress/:year/:month.md # Monthly updates\n/people/:team/:person.md # Person profiles\n/questions/:name.md # Predefined questions\n/reports/:name.md # Predefined reports\n/GLOSSARY.md # Domain terms\n```\n\n### What You Can Track\n\n**Projects:** Progress updates · Work items · Ideas and proposals\n\n**People:** Current focus · Wins and achievements · Ideas · Interests · Team and role\n\n### Examples\n\n**Ask:** \"What is Sarah working on?\" · \"Show progress on API Gateway\" · \"Who's interested in Rust?\"\n\n**Do:** \"Record that Marcus shipped auth\" · \"Create project Dashboard Redesign\" · \"Move Sarah to Platform team\"\n\n---\n\n### Ingestion\n\nThe `ingest` command transforms unstructured text into knowledge:\n\n- **Meeting notes** → Progress entries with dates and attribution\n- **Slack threads** → Updates to relevant projects and people\n- **Status updates** → Wins, current focus, and interests\n\nJust paste your content and run `ingest` — it extracts names, projects, dates, and achievements automatically.\n\n### Utility Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `print_datetime.sh` | Get current date/time for entries |\n| `print_dir_structure.sh` | Show folder structure |\n| `random_project.sh` | Pick a random project to review |\n| `random_person.sh` | Pick a random person to review |\n\n### Tips\n\n- **README.md files** — Every folder has one for navigation\n- **Cross-linking** — Projects and people reference each other\n- **Attribution** — Include `@username` when recording who did what\n- **Dates** — All entries include dates for tracking\n\n### Guidelines\n\n- Keep output scannable with tables and bullets\n- Show actual directory structure from script output\n- Be concise but comprehensive\n- Tailor suggestions based on what exists in the repo", "variables": [], "notes": "Show an overview of this Context repository and what the user can do.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/matryer/context", "path": ".cursor/commands/help.md", "ref": "ed2f7434508f89842c45d21c2d231653e8fec462", "url": "https://github.com/matryer/context/blob/ed2f7434508f89842c45d21c2d231653e8fec462/.cursor/commands/help.md", "key": "matryer/context/.cursor/commands/help.md" } } }

help

About

Help Command

Command: `help`

Steps

Context Knowledgebase

Commands

Structure

What You Can Track

Examples

Ingestion

Utility Scripts

Tips

Guidelines

Install help and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

Help Command

Command: help

Steps

Context Knowledgebase

Commands

Structure

What You Can Track

Examples

Ingestion

Utility Scripts

Tips

Guidelines

Install help and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

Command: `help`