Run any Skill in Manus with one click

upgrade-scope-triage

Stars0

Forks0

UpdatedMarch 1, 2026 at 13:08

Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

tokamak-network

tokamak-network/24-7-playground

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	upgrade-scope-triage
description	Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

Upgrade Scope Triage

Classify the request before writing code.

Classify impact

Identify touched surfaces: apps/sns, apps/runner, DB schema, auth/session, runner launcher, docs.
Assign risk level:
- P0: security boundary, credential flow, auth verification, runner liveness.
- P1: API/schema compatibility, permission transitions, shared component behavior.
- P2: isolated UI copy or styling with no flow impact.

Select companion skills

Always include upgrade-verification-matrix for non-trivial changes.
Add security-boundary-guardrails for any secret/auth/network boundary touch.
Add runner-liveness-guardrails for /runner/*, runner start/stop, or runtime credential changes.
Add auth-and-permission-guardrails for session, nonce, owner/agent actions, or status transitions.
Add schema-migration-guardrails for Prisma model/index/migration edits.
Add api-contract-guardrails for request/response changes.
Add runner-communication-protocol-guardrails for runner<->agent action schema changes or runner<->SNS header/nonce/signature/route changes.
Add docs-and-handover-guardrails when behavior or operator workflow changes.

Produce execution contract

Write a checkable plan with explicit verification commands.
List stop conditions that require redesign instead of patching.
Keep scope minimal; remove unrelated edits.

More from this repository

same repository

auth-and-permission-guardrails

tokamak-network/24-7-playground

Guard authentication, authorization, and action-permission correctness in SNS workflows. Use when changing login/session flows, nonce/signature validation, owner-agent permission boundaries, or thread/request/report state transitions.

2026-03-020

docs-and-handover-guardrails

tokamak-network/24-7-playground

Keep operator and handover documentation aligned with behavior changes. Use when upgrades alter auth flow, runner operations, API behavior, permissions, schema assumptions, or UX workflows documented in project guides.

2026-02-240

runner-communication-protocol-guardrails

tokamak-network/24-7-playground

Define and protect protocol contracts between Runner and the LLM agent, and between Runner and SNS APIs. Use when changing runner prompts, decision/action schema, communication logs, SNS client routes, auth headers, nonce-signature logic, or request-status/tx feedback semantics.

2026-02-240

security-boundary-guardrails

tokamak-network/24-7-playground

Enforce non-negotiable security boundaries for SNS and Runner upgrades. Use when code changes can affect secrets, auth/signing, launcher access, CORS, network flows, logging redaction, or credential storage.

2026-02-240

deploy-build-guardrails

tokamak-network/24-7-playground

Prevent deploy/build failures for SNS and Runner by enforcing guardrails around Next.js render mode, Prisma/DB access timing, environment wiring, and pre-merge verification. Use when changing build scripts, route segment config (`dynamic`/`revalidate`), Prisma usage, or Vercel deployment settings.

2026-02-230

user-error-logging-guardrails

tokamak-network/24-7-playground

Define and govern SNS user-error log collection scope, source types, payload minima, and sync rules for dev-maintenance observability.

2026-02-180

name	upgrade-scope-triage
description	Triage and route any non-trivial upgrade request in this repository by risk, impacted boundaries, and required guardrail skills. Use when a task touches auth, runner runtime, API contracts, schema, permissions, or docs.

Upgrade Scope Triage

Classify the request before writing code.

Classify impact

Identify touched surfaces: apps/sns, apps/runner, DB schema, auth/session, runner launcher, docs.
Assign risk level:
- P0: security boundary, credential flow, auth verification, runner liveness.
- P1: API/schema compatibility, permission transitions, shared component behavior.
- P2: isolated UI copy or styling with no flow impact.

Select companion skills

Always include upgrade-verification-matrix for non-trivial changes.
Add security-boundary-guardrails for any secret/auth/network boundary touch.
Add runner-liveness-guardrails for /runner/*, runner start/stop, or runtime credential changes.
Add auth-and-permission-guardrails for session, nonce, owner/agent actions, or status transitions.
Add schema-migration-guardrails for Prisma model/index/migration edits.
Add api-contract-guardrails for request/response changes.
Add runner-communication-protocol-guardrails for runner<->agent action schema changes or runner<->SNS header/nonce/signature/route changes.
Add docs-and-handover-guardrails when behavior or operator workflow changes.

Produce execution contract

Write a checkable plan with explicit verification commands.
List stop conditions that require redesign instead of patching.
Keep scope minimal; remove unrelated edits.