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.
bumping-biome - Skill - OpenSmartRoute
Skillv1.0.0
bumping-biome
Bumps biome package versions (e.g. @biomejs/biome) using pnpm, aligns biome.jsonc files with the new version/s across the repository and runs biome-related checks.
Imported from prisma/prisma-next (skills-contrib/bumping-biome/SKILL.md). Install upstream with npx skills add prisma/prisma-next --skill bumping-biome. Copyright stays with the author.
Bumping Biome Skill
Instructions
Run pnpm up -D -w -r @biomejs/biome@<version> - replace <version> with a specific package version provided in the session, otherwise fallback to latest.
Rename all biome.json files to biome.jsonc and replace the old package version number in $schema with the newly installed package version number from the previous step.
Run pnpm -w lint:fix. Report any issues/regressions briefly.
If there are remaining unsafe fixes following the previous step, offer to run pnpm -w lint:fix:unsafe to attempt to fix some of the issues/regressions.
If the offer in the previous step is agreed, run the appropriate command, and report any remaining issues/regressions briefly.
If there are remaining issues/regressions after the previous step, try and come up with your own suggestions for fixing them and present the plan.
Don't Do
Don't scan for biome versions. If the session doesn't include a specific package version number, use latest.
Don't read the root package.json or lockfiles looking for the current biome version/s. We'll see the change in version numbers in Git anyway.
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 bumping-biome 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.
prisma-prisma-next-bumping-biome.ocm.jsonjson
{
"ocm": "1",
"id": "prisma-prisma-next-bumping-biome",
"kind": "skill",
"name": "bumping-biome",
"description": "Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names).",
"publisher": "prisma",
"version": "1.0.0",
"capabilities": {
"domains": [
"coding"
],
"tags": [
"skill-md",
"skills-sh"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Bumps `biome` package versions (e.g. `@biomejs/biome`) using `pnpm`, aligns `biome.jsonc` files with the new version/s across the repository and runs biome-related checks. Use when required to update `biome` to a newer version - explicitly or implicitly (e.g. after running `pnpm up`, `pnpm update`, `pnpm upgrade` without specific package names)."
],
"primary": false,
"metadata": {
"source": {
"provider": "skills.sh",
"repository": "https://github.com/prisma/prisma-next",
"path": "skills-contrib/bumping-biome/SKILL.md",
"ref": "HEAD",
"url": "https://github.com/prisma/prisma-next/blob/HEAD/skills-contrib/bumping-biome/SKILL.md",
"key": "prisma/prisma-next/skills-contrib/bumping-biome/SKILL.md"
}
},
"instructions": "# Bumping Biome Skill\n\n## Instructions\n\n1. Run `pnpm up -D -w -r @biomejs/biome@<version>` - replace `<version>` with a specific package version provided in the session, otherwise fallback to `latest`.\n\n2. Rename all `biome.json` files to `biome.jsonc` and replace the old package version number in `$schema` with the newly installed package version number from the previous step.\n\n3. Run `pnpm -w lint:fix`. Report any issues/regressions briefly.\n\n4. If there are remaining unsafe fixes following the previous step, offer to run `pnpm -w lint:fix:unsafe` to attempt to fix some of the issues/regressions.\n\n5. If the offer in the previous step is agreed, run the appropriate command, and report any remaining issues/regressions briefly.\n\n6. If there are remaining issues/regressions after the previous step, try and come up with your own suggestions for fixing them and present the plan.\n\n## Don't Do\n\n1. Don't scan for `biome` versions. If the session doesn't include a specific package version number, use `latest`.\n\n2. Don't read the root `package.json` or lockfiles looking for the current `biome` version/s. We'll see the change in version numbers in Git anyway.",
"cost": {
"context_tokens": 291
}
}
Fetch it by URL: GET /api/v1/registry/prisma-prisma-next-bumping-biome/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.