Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
research-tasks - Skill - OpenSmartRoute
Skillv1.0.0
research-tasks
Process for answering research questions using the web and saving findings into the workspace.
Imported from mastra-ai/mastra (templates/template-claw-assistant/workspace/skills/research-tasks/SKILL.md). Install upstream with npx skills add mastra-ai/mastra --skill research-tasks. Copyright stays with the author.
Research task process
Use web_search first for broad queries; use the browser tools when you need to read a specific page.
Capture useful URLs and short quotes into a markdown file under notes/ in the workspace.
Never invent sources. If a claim isn't supported by something you actually fetched, drop it.
Final answer format:
Answer: one paragraph.
Sources: bulleted list of URLs.
Notes file: path to the saved markdown notes.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install research-tasks 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.
When a provider is down or over quota the request moves on; the trace says it did.
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
mastra-ai-mastra-research-tasks.ocm.jsonjson
{
"ocm": "1",
"id": "mastra-ai-mastra-research-tasks",
"kind": "skill",
"name": "research-tasks",
"description": "Process for answering research questions using the web and saving findings into the workspace.",
"publisher": "mastra-ai",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"research",
"web",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Process for answering research questions using the web and saving findings into the workspace."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/mastra-ai/mastra",
"path": "templates/template-claw-assistant/workspace/skills/research-tasks/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/mastra-ai/mastra/blob/HEAD/templates/template-claw-assistant/workspace/skills/research-tasks/SKILL.md",
"key": "mastra-ai/mastra/templates/template-claw-assistant/workspace/skills/research-tasks/SKILL.md"
}
},
"instructions": "# Research task process\n\n1. Use `web_search` first for broad queries; use the browser tools when you need to read a specific page.\n2. Capture useful URLs and short quotes into a markdown file under `notes/` in the workspace.\n3. Never invent sources. If a claim isn't supported by something you actually fetched, drop it.\n4. Final answer format:\n - **Answer:** one paragraph.\n - **Sources:** bulleted list of URLs.\n - **Notes file:** path to the saved markdown notes.",
"cost": {
"context_tokens": 118
}
}
Fetch it by URL: GET /api/v1/registry/mastra-ai-mastra-research-tasks/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
