> ## Documentation Index > Fetch the complete documentation index at: https://docs.decimal.ai/llms.txt > Use this file to discover all available pages before exploring further. # Rename a skill > Rename a skill. The new name must be unique within the requester's org. 2026-06-01 — added to support publish-with-rename in PublishDialog. Other tables reference skills by ID, so this is a single-row update on `skills.name`. No cascading writes; agent bindings, fork lineage, SkillShare grants, and install records continue to point at the same ID. Enforces edit permission: only the creator, owning workspace editors, or org admins can rename. ## OpenAPI ````yaml /openapi.json post /api/v1/skills/{skill_id}/rename openapi: 3.1.0 info: title: DecimalAI Platform description: Agent Dataset Lifecycle Platform — Backend API version: 0.1.0 servers: [] security: - BearerAuth: [] tags: - name: traces description: >- Ingest, search, and inspect agent execution traces. A trace is the atomic unit of the platform — every other feature (evaluation, compatibility scoring, dataset building) operates on traces. Each trace is auto-tagged with the manifest hash of the agent that produced it. - name: eval-scores description: >- Push, fetch, and aggregate per-trace evaluation scores. Scores carry source provenance (built-in, DeepEval, LangSmith, custom) and feed the unified decision engine, which produces a keep / repair / replay / drop verdict per trace. - name: skills description: >- Manage reusable instruction blocks (SKILL.md files) that modify agent behavior. Skills are first-class manifest components — changes to a skill appear in your regression-check impact reports. Use these endpoints to create, version, fork, and sync skills with your local SKILL.md files. - name: manifests description: >- Register and inspect manifest versions. A manifest is a snapshot of your agent's structural identity (tools, prompts, models, skills) at a point in time. The SDK registers manifests automatically; these endpoints expose the underlying records. - name: datasets description: >- Build versioned SFT/DPO training datasets from manifest-classified, eval-scored traces. Datasets are reproducible — each version locks the manifest and filter set used to build it. Export as JSONL, Parquet, or push to HuggingFace Hub. - name: replay description: >- Re-execute historical traces against a new manifest version. Replay is the deferred-future capability for behavioral verification of agent changes. The SDK creates a replay batch, your worker executes each task, then submits results back here for eval scoring. - name: registry description: >- Browse and install community skills from the public skills registry. Each registry skill carries a SkillScore — an evidence-tiered quality composite computed from real-world evals, benchmarks, and ratings across organizations. Installing creates a fork in your org — edits don't affect the public version. - name: agents description: >- List and inspect agents, plus their multi-agent topology (orchestrator → sub-agent edges discovered from traces). Agents are identified by a stable agent_name string set in your SDK init() call. - name: import description: >- Bulk-import historical traces from another observability platform or a JSONL backup. Useful for migrating from LangSmith / Braintrust / Langfuse. Duplicate trace IDs are silently skipped — re-running an import is safe. paths: /api/v1/skills/{skill_id}/rename: post: tags: - skills summary: Rename a skill description: |- Rename a skill. The new name must be unique within the requester's org. 2026-06-01 — added to support publish-with-rename in PublishDialog. Other tables reference skills by ID, so this is a single-row update on `skills.name`. No cascading writes; agent bindings, fork lineage, SkillShare grants, and install records continue to point at the same ID. Enforces edit permission: only the creator, owning workspace editors, or org admins can rename. operationId: rename_skill_route_api_v1_skills__skill_id__rename_post parameters: - name: skill_id in: path required: true schema: type: string description: The skill's stable ID (prefixed 'sk_'). examples: - sk_abc123 title: Skill Id description: The skill's stable ID (prefixed 'sk_'). - name: Authorization in: header required: false schema: type: string title: Authorization - name: decimal_session in: cookie required: false schema: anyOf: - type: string - type: 'null' title: Decimal Session requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/RenameSkillRequest' responses: '200': description: Skill renamed. content: application/json: schema: $ref: '#/components/schemas/RenameSkillResponse' '403': description: Caller is not the owner or a workspace editor. '404': description: Skill not found. '409': description: A skill with the new name already exists in the org. '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' components: schemas: RenameSkillRequest: properties: new_name: type: string maxLength: 200 minLength: 1 title: New Name type: object required: - new_name title: RenameSkillRequest description: |- Validated request for POST /skills/{id}/rename. 2026-06-01 — added to support publish-with-rename in PublishDialog. A user wants to publish a fork under a public name different from their local name; the dialog renames the local skill first, then publishes under the new name. The new name must be a valid slug (same rule as fork); org-uniqueness + the public-slug freeze are checked in the route/service where org_id and visibility are available. RenameSkillResponse: properties: status: type: string const: ok title: Status skill_id: type: string title: Skill Id old_name: type: string title: Old Name new_name: type: string title: New Name type: object required: - status - skill_id - old_name - new_name title: RenameSkillResponse HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type input: title: Input ctx: type: object title: Context type: object required: - loc - msg - type title: ValidationError securitySchemes: BearerAuth: type: http scheme: bearer description: Enter your API key (e.g. dai_sk_test_key_001) ````