Menu
Use when starting any compliance task — establishes skill ordering and MCP grounding requirements before any other complypack skill runs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when user mentions Rego, Conftest, OPA, "generate policy", or "assessment logic" in the context of Gemara catalogs. Generates Rego policies from Gemara Control Catalogs for Kubernetes (Deployments, Pods, DaemonSets, StatefulSets, CronJobs, Jobs, Services, NetworkPolicies, Ingress, RBAC, ConfigMaps, Secrets), CI/CD pipelines (GitHub Actions, GitLab CI, Azure Pipelines), Conftest, or OPA. Accepts mode argument: "single" (default, one requirement at a time) or "batch" (all at once)
Set up complypack for this project — generate complypack.yaml, warm the artifact cache, and optionally configure MCP integration
Use when user wants to build Gemara Policy artifacts for audit preparation or compliance program setup
Use before generating any Rego policy or assessment logic — generates human-reviewable test cases from assessment requirements before any policy is written
Use when user mentions Rego, Conftest, OPA, AMPEL, "generate policy", or "assessment logic" in the context of Gemara catalogs. Generates policies from Gemara Control Catalogs for Kubernetes (Deployments, Pods, DaemonSets, StatefulSets, CronJobs, Jobs, Services, NetworkPolicies, Ingress, RBAC, ConfigMaps, Secrets), CI/CD pipelines (GitHub Actions, GitLab CI, Azure Pipelines), Conftest, OPA, or AMPEL
| name | using-complypack |
| description | Use when starting any compliance task — establishes skill ordering and MCP grounding requirements before any other complypack skill runs |
Check for applicable complypack skills before any compliance action — including answering questions about controls, generating policy, or modifying pipeline artifacts.
| Skill | Type | When |
|---|---|---|
comply:setup | Process | Before any other skill — configures complypack for the project |
comply:build-assessment | Domain | Generating Rego policies from Gemara catalogs (single or batch mode) |
comply:audit-pipeline | Domain | Building Gemara Policy artifacts (scoping, mapping, adherence) |
| Skill | Used By |
|---|---|
comply:test-driven-assessment | comply:build-assessment — test case generation logic |
comply:pack-assessment | comply:build-assessment — policy generation logic |
comply:setup first (required once per project)comply:build-assessment (handles test-then-policy internally)comply:audit-pipeline directly (MCP must already be configured)Every complypack skill reads from MCP. Control IDs, requirement IDs, parameter values, and platform schemas come from MCP resources — never from model memory or training data.
If the MCP server is unreachable, stop and inform the user. Do not proceed with data from general knowledge. The skills will produce incorrect output without MCP grounding.
comply:test-driven-assessment or comply:pack-assessment invoked directly by user → STOP. These are internal skills. Use comply:build-assessment instead.