security-bluebook-builder

Featured

Build a minimal but real security policy for sensitive apps. The output is a single, coherent Blue Book document using MUST/SHOULD/CAN language, with explicit assumptions, scope, and security gates.

AI & Automation 49,938 stars 7238 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Security Bluebook Builder ## When to Use - You need a concise but enforceable security policy for an app handling sensitive data. - You want a single Blue Book document with explicit assumptions, controls, and go/no-go gates. - The user needs policy guidance grounded in scope, threat model, and operational security defaults rather than generic advice. ## Overview Build a minimal but real security policy for sensitive apps. The output is a single, coherent Blue Book document using MUST/SHOULD/CAN language, with explicit assumptions, scope, and security gates. ## Workflow ### 1) Gather inputs (ask only if missing) Collect just enough context to fill the template. If the user has not provided details, ask up to 6 short questions: - What data classes are handled (PII, PHI, financial, tokens, content)? - What are the trust boundaries (client/server/third parties)? - How do users authenticate (OAuth, email/password, SSO, device sessions)? - What storage is used (DB, object storage, logs, analytics)? - What connectors or third parties are used? - Retention and deletion expectations (default + user-initiated)? If the user cannot answer, proceed with safe defaults and mark TODOs. ### 2) Draft the Blue Book Load `references/bluebook_template.md` and fill it with the provided details. Keep it concise, deterministic, and enforceable. ### 3) Enforce guardrails - Do not include secrets, tokens, or internal credentials. - If something is unknown, write "TODO" plus a clear assumpti...

Details

Author
sickn33
Repository
sickn33/antigravity-awesome-skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Listed

security-bluebook-builder

Build security Blue Books for sensitive apps

487 Updated today
aiskillstore
DevOps & Infrastructure Listed

app-blueprint

This skill should be used when the user asks to "design a production architecture", "blueprint an app", "scaffold an architecture", "design a complete production-ready application", "architect this app", "give me a full system blueprint", "production architecture for X", or invokes /blueprint. Produces an 11-section senior-architect blueprint (folder tree, layers, data models, API contracts, deps, env, tests, CI/CD, notes, validation) from five required inputs (APP_DESCRIPTION, TECH_STACK, APP_TYPE, LANGUAGE, SCALE). Refuses to proceed if any input is missing. This is a greenfield architecture plan from an idea - it names a deployment target with rationale but does NOT emit infrastructure manifests (use docker-compose-architect or kubernetes-architect for those) and does NOT analyze or diagram an existing codebase (use codebase-to-mermaid / refactoring-analyst). Do NOT use for single-component design, code review, refactor planning, or throwaway prototypes.

5 Updated 3 days ago
chrismccoy
Code & Development Listed

security-page

Build a credible security/trust page for a developer tool before SOC 2 — concrete controls, encryption specifics, subprocessor list, responsible disclosure, data lifecycle, and honest scoping of what you can claim. Use when the user wants a security page, trust page, or trust center, asks "do we need SOC 2", got a vendor security questionnaire, or is losing deals to security review. Also use when they mention a DPA, subprocessors, security.txt, responsible disclosure, or "enterprise readiness", even if they never say "security page".

0 Updated 3 months ago
alexpate