SCC CLI 1.0.3

Command-line submission workflow for Student Creator Camp events.

Requirements

• Node.js 22 or newer
• An SCC account assigned to a team and event
• A completed .scc/submission.yaml
• Traditional Chinese (zh-TW) and English (en) names and introductions
• One app icon and 1 to 5 screenshots; each local media file must be 10MB or smaller
• A valid HTTP/HTTPS poster-site URL
• Submission before the assigned event deadline

The demo-video URL is optional.

Workflow

scc auth login
scc auth doctor
scc init --event "Your assigned event"
scc pull
scc validate
scc preview
scc submit --dry-run --event "Your assigned event"
scc submit --confirm --event "Your assigned event"
scc status

Always run scc pull before editing an existing submission so local changes start from the latest server version.

Login duration and security

Supabase access tokens still expire after one hour. SCC CLI 1.0.3 securely stores the rotating refresh token alongside the access token in ~/.scc/config.json, restricts the file to the current user (0600), and refreshes the session automatically. The login therefore continues beyond one hour until the user signs out, changes security-sensitive account details, or the Supabase session is otherwise revoked.

scc auth doctor verifies the user with Supabase Auth, checks the API connection, confirms refresh support, and checks the local credential-file permissions. scc auth logout signs out the current Supabase session and removes local credentials.

Event selection

event in submission.yaml and scc submit --event <name|slug|id> select and verify the target event. For safety, the value must match the event assigned to the signed-in account; the flag cannot submit to an unrelated event.

Media lifecycle

Submission uploads use a unique batch path. If an upload or database save fails, the CLI removes files from that failed batch. After a successful replacement, it removes media from the prior submission that is no longer referenced. The server independently enforces the 1-to-5 screenshot limit.

Run scc --help for the complete workflow or scc <command> --help for command-specific options.