ModelScope Skill Contest Workflow

The contest brief is the acceptance contract: 魔搭社区赛题. The 20-point task is to publish one of the participant's own Skills, confirm its contents are viewable on its direct page, then submit that page's complete URL or the full Skill ID to the contest platform.

Choose and prepare a Skill

Inspect Skills the participant authored and choose a complete, useful candidate. Do not assume a bundled, third-party, or AI-generated Skill qualifies as theirs; ask if authorship is unclear. The challenge does not require creating a new Skill when a suitable one already exists.
If a new Skill is needed or requested, present its purpose, name, contents, and validation plan for review before authoring. Give it a clear description and a short usage example.
Validate the complete Skill. Prepare a ZIP whose root contains one SKILL.md and no other files. Keep the archive below 5 MB. For the CLI publish flow, the frontmatter must include name, version, and description.

Publish through the ModelScope API

Use the participant's own token locally; never ask them to paste it into chat or commit it. For the domestic site, set MODELSCOPE_ENDPOINT=https://modelscope.cn; use the endpoint that matches the participant's account and token.

Upload the ZIP. The response's data.id becomes skill_file in the next request:

curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/files/upload" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" \
  -F "file=@skill.zip" \
  -F "type=skill"

Create the Skill using that returned ID:

curl -X POST "$MODELSCOPE_ENDPOINT/openapi/v1/skills" \
  -H "Authorization: Bearer $MODELSCOPE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"owner":"<username>","skill_name":"<lowercase-name>","display_name":"<display name>","description":"<description>","skill_file":"<data.id>","category":"skill-management"}'

Choose owner and skill_name carefully: the name uses lowercase letters, digits, and hyphens, and neither field can be changed after creation. The API returns the Skill record; its full ID is @owner/skill_name.

The official Skills Center publishing reference also shows license, tags, and source_url metadata. Add those fields when they are appropriate and you have accurate values; never invent a license or source URL.

Verify and submit

Open the direct Skill page, typically https://modelscope.cn/skills/@owner/skill_name. Confirm it identifies the intended owner and Skill and that the Skill content is viewable. Record the complete page URL and full ID.
In the contest test platform, open the 魔搭社区赛题 entry and submit either the complete direct Skill page URL or the full Skill ID. Do not submit a profile URL, account ID, or Skill name alone.
Track upload, page visibility, and contest-platform submission as separate states. Report each with evidence; do not infer success from a local file, upload response, or instruction.

When authenticated access is unavailable

Give the participant the packaging and API steps above. Ask them to publish the Skill and return its direct page URL or full ID. Verify the returned page and identifier before helping with any explicitly requested contest-platform submission. Never claim an upload, viewable page, or submission without direct evidence.

Skill routing

| Phase | Apply | | --- | --- | | Inspect candidates or prepare a handoff | This workflow and the contest brief; no extra development skill is needed by default. | | Create or update a Skill in Codex | Read skill-creator and superpowers:writing-skills; for multi-step authoring, read superpowers:writing-plans and get approval before editing. On other agent platforms, follow their equivalent authoring guidance. | | Make a non-obvious authoring choice | Use the platform's design/brainstorming guidance before settling the choice. | | Report final status | Use superpowers:verification-before-completion when available; otherwise verify each stated status from direct evidence. |

Example

Use $modelscope-skill-contest-workflow to check my Skill and prepare it for the ModelScope contest.