Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

audit-pipeline

Estrellas1

Forks8

Actualizado20 de julio de 2026 a las 16:26

Use when user wants to build Gemara Policy artifacts for audit preparation or compliance program setup

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

complytime

complytime/complypack

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Oficiales de cumplimientoOperaciones empresariales y financieras·SOC 13-1041

Explorador de archivos

5 archivos

SKILL.md

readonly

name	audit-pipeline
description	Use when user wants to build Gemara Policy artifacts for audit preparation or compliance program setup

/comply:audit-pipeline — ComplyTime Audit Pipeline

Guide users through building a Gemara Policy (applicability statement) from their system architecture and governance sources. The Gemara Policy is the formal contract between audit and engineering, functionally equivalent to an ISO 27001 Statement of Applicability or a NIST System Security Plan.

Safety

CRITICAL: Every stage MUST read control IDs, requirement IDs, and parameter values from MCP resources. DO NOT generate these from memory. The MCP server is the source of truth.

Pipeline Stages

Stage	Artifact	Purpose
scoping	`.complytime/scoping.yaml`	System profile + Control Catalog scoping + gap analysis
mapping	`.complytime/delta-report.yaml`	Parameter delta analysis + harmonization across framework layers
adherence	`.complytime/child-policy.yaml`	Compile the child Policy with adherence plan

After adherence, invoke /comply:build-assessment to generate assessment logic for use with complyctl.

Router Logic

Check if .complytime/ directory exists and which artifacts are present
Determine pipeline state:
- No .complytime/ directory → start at scoping
- scoping.yaml exists but no delta-report.yaml → offer mapping
- delta-report.yaml exists but no child-policy.yaml → offer adherence
- child-policy.yaml exists → pipeline complete, offer to re-run any stage or proceed to /comply:build-assessment
If the user specified a stage, validate prerequisites:
- mapping requires scoping.yaml
- adherence requires delta-report.yaml
Dispatch to the appropriate stage skill

Dispatching

Read the stage instructions from this skill's base directory before proceeding:

scoping → scoping.md
mapping → mapping.md
adherence → adherence.md

Supporting Files

policy-validation-rubric.md — Structural validation rubric for compiled Policy YAML (consumed by Step 6a of adherence)

Status Display

/comply:audit-pipeline status:
  [done] scoping     — .complytime/scoping.yaml
  [done] mapping     — .complytime/delta-report.yaml
  [next] adherence   — not yet run

Más de este repositorio

mismo repositorio

build-assessment

complytime/complypack

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)

2026-07-241

setup

complytime/complypack

Set up complypack for this project — generate complypack.yaml, warm the artifact cache, and optionally configure MCP integration

2026-07-221

using-complypack

complytime/complypack

Use when starting any compliance task — establishes skill ordering and MCP grounding requirements before any other complypack skill runs

2026-07-171

test-driven-assessment

complytime/complypack

Use before generating any Rego policy or assessment logic — generates human-reviewable test cases from assessment requirements before any policy is written

2026-07-151

pack-assessment

complytime/complypack

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

2026-07-151

/comply:audit-pipeline — ComplyTime Audit Pipeline

Safety

CRITICAL: Every stage MUST read control IDs, requirement IDs, and parameter values from MCP resources. DO NOT generate these from memory. The MCP server is the source of truth.

Pipeline Stages

Stage

Artifact

Purpose

scoping

.complytime/scoping.yaml

System profile + Control Catalog scoping + gap analysis

mapping

.complytime/delta-report.yaml

Parameter delta analysis + harmonization across framework layers

adherence

.complytime/child-policy.yaml

Compile the child Policy with adherence plan

After adherence, invoke /comply:build-assessment to generate assessment logic for use with complyctl.

Router Logic

Check if .complytime/ directory exists and which artifacts are present

Determine pipeline state:

No .complytime/ directory → start at scoping
scoping.yaml exists but no delta-report.yaml → offer mapping
delta-report.yaml exists but no child-policy.yaml → offer adherence
child-policy.yaml exists → pipeline complete, offer to re-run any stage or proceed to /comply:build-assessment

If the user specified a stage, validate prerequisites:

mapping requires scoping.yaml
adherence requires delta-report.yaml

Dispatch to the appropriate stage skill

Dispatching

Read the stage instructions from this skill's base directory before proceeding:

scoping → scoping.md

mapping → mapping.md

adherence → adherence.md

Supporting Files

policy-validation-rubric.md — Structural validation rubric for compiled Policy YAML (consumed by Step 6a of adherence)

Status Display

/comply:audit-pipeline status: [done] scoping — .complytime/scoping.yaml [done] mapping — .complytime/delta-report.yaml [next] adherence — not yet run