メニュー
Security sub-skill that routes between Commit Shield (pre-commit/push gate) and CISO workflows. Trigger on git commit, git push, security scan, secret leak, IP check, CVE, security review, PR review, IP audit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Solo Founder Operating System -- the AI-powered team that runs a multi-product SaaS company. This is the master skill that routes to specialized sub-skills. Trigger this skill for ANYTHING related to: setting up company automation, bootstrapping infrastructure, managing personas (CPO, CTO, CFO, SRE, QA, CISO, CMO, Content Writer, DevOps Bot, Support Agent), deploying products, CI/CD pipelines, monitoring, security scanning, IP protection, pre-commit hooks, secret management, collaborator onboarding/offboarding, access control, Obsidian knowledge management, content publishing, email via Resend, auditing, cleanup, or evolving the system. Also trigger for "git commit" and "git push" (routes to Commit Shield). Even casual mentions like "set up my company", "add a new product", "who has access", "rotate secrets", "clean up", "audit my setup", or "publish the blog" should trigger this skill. This is the single entry point for all Solo Founder OS operations.
Set up the Solo Founder OS from scratch or add a new product to an existing deployment
System evolution sub-skill. Handles adding MCP servers, upgrading tools, adding personas, adding products, enhancing persona capabilities, and documenting changes. Every operation writes to the changelog BEFORE executing. Trigger on: add MCP, add tool, upgrade, migrate, enhance persona, integrate, connect new service, scale, changelog, document change.
Collaboration sub-skill for the full collaborator lifecycle: onboard, offboard, change role, manage BYOK keys, and audit access. Trigger on: onboard, offboard, collaborator, invite, revoke, access, permissions, RBAC, who has access, BYOK.
Knowledge and content sub-skill for Obsidian vault management, content workflows (blog, social, newsletter), Resend email integration, and documentation maintenance. Trigger on: Obsidian, vault, blog, content, email, resend, newsletter, docs, publish, social post, documentation, knowledge base.
Maintenance sub-skill for system health, pruning, decommissioning, secret rotation, and drift detection. Trigger on: audit, clean up, prune, rotate secrets, health check, drift, what's unused, decommission persona, decommission product, maintenance schedule.
| name | sfos-security |
| description | Security sub-skill that routes between Commit Shield (pre-commit/push gate) and CISO workflows. Trigger on git commit, git push, security scan, secret leak, IP check, CVE, security review, PR review, IP audit. |
You are the security routing layer for the Solo Founder Operating System. You determine whether the user needs the Commit Shield (real-time commit/push protection) or CISO workflow references (scheduled and on-demand security operations).
Read the user's message and match against the table below. Load the corresponding resource and follow its instructions.
| User intent | Target | Path to load |
|---|---|---|
| git commit, git push, pre-commit, secret scan, secret leak, IP check, ship it, commit shield, security scan on staged files | Commit Shield | <SKILL_DIR>/security/commit-shield/SKILL.md |
| CVE, security review, PR review, IP audit, vulnerability report, dependency scan, weekly digest, monthly audit, CISO | CISO Workflows | Reference <SKILL_DIR>/security/references/ciso-workflows.md and <SKILL_DIR>/security/references/security-tools.md |
If the user says "git commit" or "git push" and Commit Shield is enabled in their
.commit-shield.json (or they want to enable it), load the Commit Shield sub-skill
and execute the full scan pipeline before allowing the commit/push to proceed.
If the user asks about CVEs, security reviews, PR security checks, or IP audits, read the CISO workflow references and present the relevant workflow. These workflows are typically automated via N8N but can also be triggered manually.
The Commit Shield config template lives at <SKILL_DIR>/shared/templates/commit-shield-config.json.
If a project does not have .commit-shield.json in its root, copy this template and
ask the user to customize it.
For questions about what security tools are available or recommended, read
<SKILL_DIR>/security/references/security-tools.md.
