Prompt & skills, versions and roll back

​

What the page shows

• The system prompt DecimalAI serves the agent, with its version and whether the agent follows the latest version or a pinned one.
• The skill list the model sees: the same skills, in the same order, that the agent’s next run receives. Each row says why the skill is on the list:
  • Added to this agent: you added it to this agent.
  • Offered to all agents: an organization skill offered to every agent.
  • Linked from the registry for this agent: a registry skill you installed for it.
• How each skill is used here: how often runs loaded it in the last 30 days, and its benchmark lift (the skill’s own eval suite, run with and without it). Runs that loaded a skill aren’t compared with runs that didn’t: the model loads a skill when the request fits it, so the load count is a count, not lift.
• What doesn’t fit: the list holds at most 30 skills and about 1,500 tokens of descriptions. Skills past that are listed under Not sent: over the limit, so the model never sees them.

​

Changing what an agent gets: Review & apply

​

Removing a skill that every agent gets

​

Versions

• you apply a change (or an API key does): your version, with your note;
• something outside the agent changes what it gets: a skill it uses gets a new version, a skill is made opt-in, a registry skill it follows is updated, or a safety check blocks a skill. These are automatic versions, and each says why (“Removed refund-policy (made opt-in)”);
• you roll back: a new version, marked Roll back to v3.

​

The Versions page

• filters for All, Prompt, Skills and Code changes;
• under each version, the runs routed under it and, from 5 graded runs, their eval pass rate, beside the version before. These are different days and different traffic, so the page calls them a comparison, not a measured effect;
• Compare shows two versions side by side: the prompt text, the skill list and both versions’ runs;
• Roll back on any version that isn’t current.

​

Roll back

• a skill v3 had, and has since moved to a newer version, is pinned back to the version v3 served: the review says “pinned to v3 (latest is now v5)”;
• a skill v3 didn’t have comes off the agent;
• anything that can no longer be restored (a skill since deleted or blocked) is listed, and the rest still rolls back.

​

Which agents get a new skill

from decimalai import SkillRouter

router = SkillRouter()  # key from decimalai.init() or DECIMAL_API_KEY
skill = router.create_skill(name="refund-policy", description="Refund policy",
                            body_markdown="...", offer_scope="restricted")
router.assign_skill("support-agent", skill["skill_id"])

​

Make it opt-in

​

From the API

curl -X POST "https://api.decimal.ai/api/v1/agents/support-agent/setup/apply" \
  -H "Authorization: Bearer $DECIMAL_API_KEY" -H "Content-Type: application/json" \
  -d '{
        "changes": [
          {"op": "add_skill", "skill_id": "skill_abc"},
          {"op": "remove_skill", "skill_id": "skill_def"},
          {"op": "set_skill_version", "skill_id": "skill_ghi", "version_number": 2},
          {"op": "set_prompt_version", "version_number": null}
        ],
        "note": "Swap the refund skills",
        "base_version": 14
      }'

• POST /api/v1/agents/{agent_name}/setup/preview takes the same body and returns the review (the list text before and after, the token change, any problems) without changing anything.
• "rollback_to": 3 instead of changes rolls back to version 3.
• With base_version, a change made against a version that is no longer current gets 409 and the current state, so two people can’t overwrite each other.
• set_prompt_version with null serves the latest prompt version; a number pins it.
• GET /api/v1/agents/{agent_name}/versions lists versions (?show=prompt|skills|code), …/versions/{number} reads one, and …/versions/compare?from=3&to=14 compares two.
• POST /api/v1/skills/{skill_id}/make-opt-in?dry_run=true previews Make it opt-in; without dry_run it applies it.

​

Related