# Compliance Docs

> Audit compliance documentation for completeness and freshness.

- **Type:** Skill
- **Install:** `agentstack add skill-cvander-maya-compliance-docs`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [cvander](https://agentstack.voostack.com/s/cvander)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [cvander](https://github.com/cvander)
- **Source:** https://github.com/cvander/Maya/tree/main/skills/compliance_docs

## Install

```sh
agentstack add skill-cvander-maya-compliance-docs
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Compliance Docs

Reads all compliance markdown files and permits/README.md. Reports which expected docs exist, which are missing, which are empty, and which are stale (not updated in >30 days).

Read-only. Does not modify files or reach external services. No PII in output.

## When to Use

- Monthly documentation audit (scheduled: 1st of month)
- Before any scheduled inspection (to verify docs are in order)
- When onboarding a new manager (verify all docs exist)
- After setting up a new bar location

## Procedure

Run the skill from the repo root:

```bash
# Human-readable summary
python -m skills.compliance_docs

# Structured JSON output (for automation)
python -m skills.compliance_docs --format json

# Against a custom compliance directory
python -m skills.compliance_docs --compliance-dir path/to/compliance --format json
```

Parse the JSON result:
- `status`: "ok" (all docs present and current) or "warn" (findings present)
- `findings`: array with codes DOC_MISSING, DOC_EMPTY, DOC_STALE
- `data.docs_checked`: number of docs audited
- `data.docs_present`: number of docs found
- `data.docs_missing`: number of expected docs not found

### Exit Codes

| Code | Meaning |
|------|---------|
| 0 | All expected docs present and current |
| 1 | One or more documentation issues |
| 2 | Config error (bad arguments) |
| 3 | Data error (can't read directory) |
| 10 | Unexpected error |

## Verification

After running, confirm:
- Exit code is 0 or 1 (not 2, 3, or 10)
- stdout is valid JSON (when using --format json)
- `data.docs_checked` > 0 (directory was actually read)
- If exit code is 1, `findings` array is non-empty

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [cvander](https://github.com/cvander)
- **Source:** [cvander/Maya](https://github.com/cvander/Maya)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-cvander-maya-compliance-docs
- Seller: https://agentstack.voostack.com/s/cvander
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.