메뉴
Internal guidance for presenting redteam panel JSON back to the user
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when a request needs product/design exploration, unclear requirements, multiple viable approaches, UI/UX choices, or new behavior whose intent is not yet bounded.
Use when 2+ independent tasks, failures, research lanes, exploration lanes, or path-scoped investigations can run without shared state, shared files, or sequential dependency.
Use when executing a written implementation plan inline in the current session with checkpoints and verification.
Use when adding or changing a capability surface such as a public function, API, command, prompt, workflow, schema/helper, policy, or reusable instruction.
Use when implementation is complete, verification passes, and the remaining decision is how to integrate, merge, PR, clean up, or finish the branch.
Use when creating or revising docs, plans, records, PR text, handoffs, or other prose that should be sparse, direct, and low-context.
| name | redteam-result-handling |
| description | Internal guidance for presenting redteam panel JSON back to the user |
| user-invocable | false |
When presenting review/decision/hack/ultrareview output:
summary first, then findings ordered by severity (critical → high → medium → low).approve with no material findings, say so briefly.needs-attention, treat findings as blocking until addressed or explicitly accepted./redteam:status to check progress — never poll results dirs or loop on BashOutput./redteam:result <job-id> or the notification payload, then apply this skill./redteam:setup.