From sco-control
Controls SenseCore SCO CLI resources and jobs: CCI containers, ACP training jobs, AEC2 clusters, AFS storage, AOSS/CCR images, and shell-template job submission. Optimized for query, submit, inspect, log, exec, and storage workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sco-control:sco-controlThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to operate `sco` pragmatically from shell templates and known command patterns. Prefer the embedded patterns below before reading references. Load reference files only when the user asks for a less common flag, a YAML example, or a precise command variant.
Use this skill to operate sco pragmatically from shell templates and known command patterns. Prefer the embedded patterns below before reading references. Load reference files only when the user asks for a less common flag, a YAML example, or a precise command variant.
delete, quota/ACL updates, stop running jobs/apps), show the exact command and ask unless the user already explicitly requested execution.-o json or -o yaml when a command supports it and the next step needs parsing.jobs list can return other users' jobs; filter client-side by the runtime user id or by job display-name patterns.sco tests unless the user asks.sco config profiles list
sco config list
sco aec2 clusters list
sco afs volume list
sco ccr images list
sco aec2 clusters list-workerspec --workspace-name "$WORKSPACE" --aec2-name "$AEC2"
sco aec2 clusters describe --name "$AEC2"
sco acp jobs create, or the shell-template pattern in run_sco_pattern.md.sco cci apps create.sco acp jobs list --workspace-name "$WORKSPACE" --page-size 10
sco acp jobs describe --workspace-name "$WORKSPACE" -o json "$JOB_ID"
sco acp jobs get-workers --workspace-name "$WORKSPACE" "$JOB_ID"
sco acp jobs stream-logs --workspace-name "$WORKSPACE" "$JOB_ID"
sco cci apps list --workspace-name "$WORKSPACE"
sco cci apps describe "$APP" --workspace-name "$WORKSPACE" -o yaml
ACP jobs, highest priority:
sco acp jobs create --workspace-name "$WORKSPACE" --aec2-name "$AEC2" --job-name "$JOB" \
--container-image-url "$IMAGE" --training-framework pytorch --worker-nodes "$NODES" \
--worker-spec "$SPEC" --priority normal --quota-type reserved --storage-mount "$VOL:/data" \
--command "$COMMAND"
sco acp jobs list --workspace-name "$WORKSPACE" --page-size 20 -o table
sco acp jobs list --workspace-name "$WORKSPACE" --page-size 100 -o json
sco acp jobs describe --workspace-name "$WORKSPACE" -o json "$JOB_ID"
sco acp jobs get-workers --workspace-name "$WORKSPACE" "$JOB_ID"
sco acp jobs stream-logs --workspace-name "$WORKSPACE" "$JOB_ID" --follow
sco acp jobs exec --workspace-name "$WORKSPACE" --worker-name "$WORKER" "$JOB_ID"
sco acp jobs stop --workspace-name "$WORKSPACE" "$JOB_ID"
sco acp jobs start --workspace-name "$WORKSPACE" "$JOB_ID"
If the user gives a user id, use it only as a runtime filter, for example:
sco acp jobs list --workspace-name "$WORKSPACE" --page-size 100 -o table | awk 'NR<=4 || /'"$USER_ID"'/'
CCI apps, highest priority:
sco cci apps create "$APP" --workspace-name "$WORKSPACE" --config ./cci-app.yaml --ports 1002,1003
sco cci apps list --workspace-name "$WORKSPACE" --keyword "$USER_ID" --page-size 20
sco cci apps list --workspace-name "$WORKSPACE" --aec2-name "$AEC2" --state RUNNING
sco cci apps describe "$APP" --workspace-name "$WORKSPACE" -o yaml
sco cci apps update "$APP" --workspace-name "$WORKSPACE" --replicas 1
sco cci apps stop "$APP" --workspace-name "$WORKSPACE"
sco cci apps start "$APP" --workspace-name "$WORKSPACE"
sco cci apps delete "$APP" --workspace-name "$WORKSPACE"
CCI --keyword fuzzy-matches user_name, display_name, or name, so use the runtime user id only as a query value, not as a skill default.
AEC2 queries:
sco aec2 clusters list
sco aec2 clusters describe --name "$AEC2"
sco aec2 clusters list-workerspec --workspace-name "$WORKSPACE" --aec2-name "$AEC2"
If AEC2 reports SUBSCRIPTION_NAME_REQUIRED, rerun with a configured profile or explicit global --subscription/--resource-group values from the user's environment.
AFS storage:
sco afs volume list
sco afs volume list -i "$VOLUME_ID"
sco afs volume ls -i "$VOLUME_ID" -d /
sco afs dir-quota list -i "$VOLUME_ID"
sco afs dir-quota create -i "$VOLUME_ID" -d /path --files 100000 --capacity 1024
sco afs dir-quota update -i "$VOLUME_ID" -d /path --files 100000 --capacity 2048
sco afs dir-acl list -i "$VOLUME_ID" -d /path
sco afs dir-acl create -i "$VOLUME_ID" -d /path -p rw -u all
AOSS/CCR images:
sco ccr images list
sco ccr images list -p
sco ccr namespaces list
sco ccr namespaces get "$NAMESPACE"
sco ccr builds create -n "$NAMESPACE" -f ./Dockerfile -t "$TAG" -c ./context
sco ccr builds list -n "$NAMESPACE"
sco ccr builds log -n "$NAMESPACE" "$BUILD_ID"
sco ccr labels list
sco ccr labels update "$IMAGE_NAME" -n "$NAMESPACE" -c gpu,cpu -p acp,ams
When the user asks to create or adapt a submission template, preserve this shape unless they override it:
SPEC1CONTAINER_IMAGE_URLvolume_id:/datacd "$REMOTE_PROJECT_DIR", export env vars, echo task metadata, then bash "$TARGET_SCRIPT" "$ENTRY_ARG"sco acp jobs create --training-framework=pytorch --priority=normal --quota-type=reserved --storage-mount=... --command=...For task-switching guidance, read run_sco_pattern.md. For a shell skeleton, use acp_submit_template.sh.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub binarycheater/sco-skill --plugin sco-control