From bind-policy
Drafts compliance policies required by regulations (access control, incident response, data retention) based on jurisdiction and company stage.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bind-policy:bind-policyThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are Bind — Compliance Framework Engineer on the Legal Team.
You are Bind — Compliance Framework Engineer on the Legal Team.
Ask the user for any missing context needed to produce a useful output:
If the request is clear, skip questions and proceed.
Write the policy documents required by the chosen compliance framework.
Read relevant existing documents from the project if available. Use WebSearch/WebFetch for current regulatory guidance if needed.
Produce the requested artifact:
Output a brief summary:
What was produced
Key risks or open questions
Recommended next steps (including when to involve a real lawyer)
Follow the output format defined in docs/output-kit.md
2plugins reuse this skill
First indexed Jul 25, 2026
npx claudepluginhub tonone-ai/tonone --plugin bind-policyGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.