skill.upload
Creates or updates a skill from a zip package uploaded with file.upload. scope and project_id choose whether the skill goes to the user’s personal skills, the user’s team, or a project; see Target scope. The package must not exceed 8 MiB and must contain a SKILL.md file with YAML front matter that sets name.
Upload flow
- Call file.upload with the package’s filename, then
PUTthe zip bytes to the returnedupload_url. - After the
PUTcompletes, callskill.uploadwith the returnedfile.id. Choose where the skill goes withscopeandproject_id; see Target scope. - Use the returned
skill.idinmessage.enable_skillsormessage.force_skillsof task.create or task.sendMessage.
file.upload schedule, and deleting it does not affect the skill.
Target scope
400 invalid_argument. scope values are lowercase and match skill.owner_type in the response. Requests without scope keep working as before.
A team upload always targets the team that the API Key’s or token’s user belongs to; there is no team ID parameter.
Package requirements
Same-name uploads
Thename in SKILL.md identifies the skill within the target scope: the user’s personal skills, the team’s skill library, or the skills of the given project.
After upload
- A created or restored personal skill is enabled for the user. Updating an existing personal skill keeps the user’s current enabled state.
- Every successful project upload adds the skill to the project’s default skills, so it appears in
skill_idsof project.detail. This also re-adds a skill that was removed fromskill_idswith project.update. - A created or restored team skill is not added to team members’ skill lists automatically, including the uploader’s, and is not enabled by default. Members can add it from the team library in Manus, and team admins can change these defaults in Manus. Updating an existing team skill keeps its current team settings.
- Personal skills appear in skill.list. Pass
project_idthere to list project skills, orscope=teamto list the team library.
Errors
Headers
API key for direct authentication. Provide either this or Authorization, not both. See Authentication.
OAuth2 access token in Bearer {token} format. Only Trusted team client and Trusted public client apps can call this endpoint; standard OAuth clients receive 403 permission_denied regardless of scopes. Provide either this or x-manus-api-key, not both. See the Open App guide.
"Bearer {access_token}"
Body
ID of a file uploaded with file.upload. The file must belong to the user, have finished uploading, and be a zip skill package of at most 8 MiB (8,388,608 bytes). The file is not consumed: it still expires on the normal file schedule, and deleting it does not affect the skill.
1 - 64Where to upload the skill. Values match owner_type in the response.
personal— the user's personal skills.project_idmust be omitted.team— the skill library of the user's team. The user must be a Team Owner, Admin, or Super Admin.project_idmust be omitted.project— the project given byproject_id, which is required.
When omitted, the skill goes to the project if project_id is set, and to the user's personal skills otherwise.
personal, team, project Target project. Required when scope is project; when scope is omitted, setting it uploads the skill to this project instead of the user's personal skills. Must be omitted when scope is personal or team. The user must own the project or be a project member with edit permission. Use project.list to get project IDs.
1 - 65Response
Skill uploaded successfully.
The uploaded skill, in the same shape as skill.list. owner_type is personal, team, or project.