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.
recipe-find-large-files - Skill - OpenSmartRoute
Skillv1.0.0
recipe-find-large-files
Identify large Google Drive files consuming storage quota.
Imported from googleworkspace/cli (skills/recipe-find-large-files/SKILL.md) via skills.sh. Install upstream with npx skills add googleworkspace/cli --skill recipe-find-large-files. Copyright stays with the author.
Find Largest Files in Drive
PREREQUISITE: Load the following skills to execute this recipe: gws-drive
Identify large Google Drive files consuming storage quota.
Steps
List files sorted by size: gws drive files list --params '{"orderBy": "quotaBytesUsed desc", "pageSize": 20, "fields": "files(id,name,size,mimeType,owners)"}' --format table
Review the output and identify files to archive or move
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 recipe-find-large-files 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.
