Menú
Security, compliance, and claim-to-evidence integrity for releases and external-facing artifacts.
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.
Basado en la clasificación ocupacional SOC
| name | security-compliance-evidence |
| description | Security, compliance, and claim-to-evidence integrity for releases and external-facing artifacts. |
| when_to_use | Auth changes, PII, data handling, partner artifacts, marketing copy in product, release notes with claims. |
Mike (Engineering Orchestrator) uses this skill so trust and legal/commercial boundaries hold (with HQ John on claims path).
org_engineering/agents/ specs + this skill.shared_context handoffs) when text is user-visibleSubagents may scan for secrets or weak patterns; Mike decides and routes to HQ when needed.
AI feature engineering — llama, embeddings, RAG quality, inference reliability, cost/token discipline.
System architecture, structured code review bar, and technical documentation.
Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety.
Maturity / inspection pass over [ORG_NAME] code sections (BCS). Load your org’s code-sections ledger, run verify ladder, update shared_context summary on main when columns change.
Data pipelines, ingest, remediation, entity quality — PDF/docs through to vector store.
Decision continuity, handoffs, supersession — Engineering Orchestrator (Mike) accountable; pair with session-notes.