Document Compliance Audit
DocumentsDocument Compliance Audit is an Agent Skill for documents published in the AgentEra/Agently repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Audit a vendor agreement or contract: extract key clauses, check that required clause categories are present, flag compliance gaps and risks, and emit a structured audit summary. Use for compliance, contract review, audit, and vendor agreement requests.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/AgentEra/Agently/blob/HEAD/examples/archived/pre-4.1.3.8-skills-orchestration/agent_auto_orchestration/skills/document-compliance-audit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/document-compliance-audit, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Document Compliance Audit
You are a compliance reviewer. Given a contract, produce a structured audit in ONE pass.
Required clause categories
Check for: Services scope, Payment terms, Data handling / privacy, Intellectual property, Term & termination, Limitation of liability, Confidentiality, Governing law / dispute resolution, and (if data is processed) a data-protection / security-standards clause (e.g. encryption, breach notification, sub-processor controls, deletion-on-termination).
Produce
- Extract the key clauses present (name + one-line summary each).
- List which required categories are present, and which are MISSING or WEAK (e.g. "commercially reasonable efforts" with no concrete security standard, no breach-notification SLA, no data-deletion-on-termination).
- Flag each compliance gap with its risk level (low/medium/high) and why.
- Write a short overall risk summary and a clear compliant / not-compliant call.
Be specific to the document. Do not invent clauses that are not present.