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.
setup - Skill - OpenSmartRoute
Skillv1.0.0
setup
Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says "set up", "configure", "connect", or when MCP tools are missing.
Imported from aws/agent-toolkit-for-aws (plugins/aws-agents-for-devsecops/skills/setup/SKILL.md) via skills.sh. Install upstream with npx skills add aws/agent-toolkit-for-aws --skill setup. Copyright stays with the author.
Setup
Run these skills in order:
Invoke the setup-devops-agent skill to configure the DevOps Agent MCP connection.
Invoke the setup-security-agent skill to configure the Security Agent workspace (agent space, IAM role, S3 bucket).
If the user only needs one agent, run only the relevant skill.
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://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/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 setup 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.
aws-agent-toolkit-for-aws-setup.ocm.jsonjson
{
"ocm": "1",
"id": "aws-agent-toolkit-for-aws-setup",
"kind": "skill",
"name": "setup",
"description": "Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says \"set up\", \"configure\", \"connect\", or when MCP tools are missing.",
"publisher": "aws",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Set up the AWS DevOps Agent and AWS Security Agent connections. Use when the user says \"set up\", \"configure\", \"connect\", or when MCP tools are missing."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/aws/agent-toolkit-for-aws",
"path": "plugins/aws-agents-for-devsecops/skills/setup/SKILL.md",
"ref": "HEAD",
"url": "https://www.skills.sh/aws/agent-toolkit-for-aws/setup",
"key": "aws/agent-toolkit-for-aws/plugins/aws-agents-for-devsecops/skills/setup/SKILL.md"
}
},
"instructions": "# Setup\n\nRun these skills in order:\n\n1. Invoke the `setup-devops-agent` skill to configure the DevOps Agent MCP connection.\n2. Invoke the `setup-security-agent` skill to configure the Security Agent workspace (agent space, IAM role, S3 bucket).\n\nIf the user only needs one agent, run only the relevant skill.",
"cost": {
"context_tokens": 77
}
}
Fetch it by URL: GET /api/v1/registry/aws-agent-toolkit-for-aws-setup/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.
