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 codebase, prompts, or API calls…
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
$ npx -y skills add LING71671/Open-ClaudeCode --skill gstack-cso --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/gstack-csoContext preview
The summary Claude sees to decide when to auto-load this skill.
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
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.
完整开源的 Claude Code 项目 - 基于 Anthropic 官方源码重建 🌐 Languages: 中文 | English
Repo: LING71671/Open-ClaudeCode
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 codebase, prompts, or API calls…
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or…
Update or audit OPC documentation after code changes. Use when behavior, setup, CLI flags, desktop workflow, provider support, or plugin surfaces changed.
Systematic root-cause debugging for OPC work. Use when there is a bug, crash, regression, failing command, flaky behavior, provider issue, or unexplained…
Read-only QA report for an OPC desktop flow, CLI command, local URL, staging URL, or documented user journey. Does not modify code.
Pre-landing code review for the current OPC branch or diff. Use before merging, shipping, or asking whether a change is safe.