@standardagents/skill 0.32.0 → 0.33.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@standardagents/skill",
-  "version": "0.32.0",
+  "version": "0.33.1",
   "private": false,
   "publishConfig": {
     "access": "public",

package/skills/agentbuilder/SKILL.md

@@ -431,14 +431,31 @@ If you have multiple configured providers, pass `--provider=<name>` explicitly.
 
 ### Fallback strategy
 
-Define more than one model per category, on different providers. The model `name` should describe the *use case*, not the provider, so a fallback can substitute transparently:
+**Every model definition should declare `fallbacks`.** The runtime tries the primary (with retries), then each fallback in order — this is what keeps an agent alive through a provider outage, so a model without fallbacks is a single point of failure.
 
-```
-agents/models/extra_reasoning.ts          → primary (provider A)
-agents/models/extra_reasoning_fallback.ts → secondary (provider B)
+Two rules for choosing the fallback:
+
+1. **Different provider.** The dominant failure mode is a provider-wide outage or rate-limit event, so a fallback at the same provider usually fails with the primary. Route the fallback through a different provider (or a different aggregator path).
+2. **Equal or smarter, never cheaper.** Fallback traffic is rare — it only flows when the primary is already failing — so its cost is negligible. Pick a model at least as capable as the primary whenever one exists at another provider; degrading quality mid-conversation during an outage is far worse than paying a little more for the handful of requests that fall through.
+
+```ts
+// agents/models/extra_reasoning.ts — primary (provider A)
+export default defineModel({
+  name: 'extra_reasoning',
+  provider: providerA,
+  model: '<primary model id>',
+  fallbacks: ['extra_reasoning_fallback'],
+});
+
+// agents/models/extra_reasoning_fallback.ts — equal-or-smarter model (provider B)
+export default defineModel({
+  name: 'extra_reasoning_fallback',
+  provider: providerB,
+  model: '<fallback model id>',
+});
 ```
 
-Prompts and agents reference `extra_reasoning`; if the primary provider is down, the fallback is one rename away.
+The model `name` should describe the *use case*, not the provider (`extra_reasoning`, not `provider_a_thinker`), so prompts and agents never change when the models behind a name are swapped. Confirm both model ids through the Model selection workflow above — the fallback is still a model string, and the no-invented-model-strings rule applies to it too.
 
 For the authoritative list of which models currently fill each category, see `agents/models/AGENTS.md` in your project (created by `agents scaffold`). Do not embed the list here — it drifts.