claude-opus-4-5-migrat…
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their…
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
Claude Code
$ npx -y skills add LING71671/Open-ClaudeCode --skill gstack-cso --agent claude-code
Codex
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a codex -y
Cursor
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a cursor -y
Gemini CLI
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a gemini-cli -y
GitHub Copilot
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a github-copilot -y
OpenCode
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a opencode -y
Windsurf
$ npx skills add LING71671/Open-ClaudeCode --skill gstack-cso -a windsurf -y
name: gstack-cso description: Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution. allowed-tools: - Read - Grep - Glob - Bash
Use this skill for a security review with OWASP and STRIDE lenses.
Prioritize OPC-specific attack surfaces:
1. Map the trust boundaries and data flows. 2. Identify assets: secrets, filesystem access, provider credentials, session state, command execution, and user prompts. 3. Review entrypoints that cross boundaries. 4. Test high-confidence concerns with direct code evidence. 5. Ignore speculative issues unless there is a concrete exploit path.
For each finding include:
Also include a short "Not Findings" section for checked risks that are already mitigated.
Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their…
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web…
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or…
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior,…
Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify…
Pre-landing code review for the current OPC branch or diff. Use before merging, shipping, or asking whether a change is safe.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.