security-bluebook-builder
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.
Best for Apps handling sensitive dat…Works with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Builds a single, coherent Blue Book security policy document
- ·Uses MUST/SHOULD/CAN language for enforceability
- ·Includes explicit assumptions, scope, and security gates
- ·Grounds policy in scope, threat model, and operational security defaults
- ·Asks up to 6 short questions to gather necessary context
- ·Proceeds with safe defaults when information is missing
Use Cases
- →Creating an enforceable security policy for an app handling sensitive data
- →Documenting security controls and go/no-go gates for a new application
- →Establishing policy guidance based on specific threat models and operational contexts
Best for
- ✓Apps handling sensitive data (PII, PHI, financial)
- ✓Teams needing concise but enforceable security documentation
Not ideal for
- !Non-sensitive applications
- !Teams needing extensive legal or compliance frameworks
FAQs
name
security-bluebook-builder
description
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.
risk:unknown
source:community
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.
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill security-bluebook-builderSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.