- Home
- Skills
- Legal & Compliance
- Compliance Evidence Vault — Organize Proof for Audits
Works with the AI Agents you already use
Compliance Evidence Vault — Organize Proof for Audits
Organize audit evidence with control mappings, provenance, period coverage, gap tracking and review-ready indexes.
$9.99
Compliance Evidence Vault — Organize Proof for Audits
Example session with this skill installed
Illustrative scenario: Prepare an internal evidence pack for access-review control AC-01 for 1 January–31 December 2025. Our supplied control requires quarterly reviews. I provide a policy approved on 10 January, signed Q1–Q3 review records and a current MFA screenshot dated 5 January 2026. No Q4 review or historical MFA logs are supplied. Use only these facts. Build the evidence matrix, gaps, collection requests and delivery checklist; do not claim a framework version or compliance.
- Read your context and instructions
- Compiled the compliance evidence vault
Readiness brief
The supplied evidence is incomplete for the full 2025 period. Three quarterly access reviews are represented; Q4 is an evidence gap. The current MFA screenshot supports only the visible January 2026 state, not historical enforcement. No certification or audit conclusion is made.
Scope
Control: AC-01, user-supplied quarterly access review. Period: 1 January–31 December 2025. Framework/version: not supplied. Systems, control owner, user population and sampling plan: unverified. Assessment is based on the scenario descriptions, not independently inspected files.
Evidence matrix
| ID | Supplied artifact | Evidence class | Coverage | Limitation |
|---|---|---|---|---|
| E-01 | Policy approved 10 January 2025 | Design | Document approval date known | Effective date, prior version and first nine days unverified; policy does not prove reviews occurred |
| E-02 | Signed Q1 review | Operating | Q1, as described | Population completeness, decisions and removal follow-through need inspection |
| E-03 | Signed Q2 review | Operating | Q2, as described | Same validation needed |
| E-04 | Signed Q3 review | Operating | Q3, as described | Same validation needed |
| E-05 | MFA screenshot, 5 January 2026 | Current implementation | Point in time only | Does not prove 2025 enforcement; relevance to AC-01 must be justified |
Gaps and collection requests
- G-01 / insufficient period: Q4 review evidence absent. Owner: to confirm. Search legitimate review systems or backups with authorization. Request the actual Q4 record, review population, reviewer decisions and follow-through records. If unavailable, disclose the gap; never create a retroactive record. Internal triage: high, subject to owner review.
- G-02 / unverified population: Request the complete in-scope user population and reproducible export parameters for each quarter. Do not claim representative sampling until completeness is validated.
- G-03 / provenance: For each original, record source system, collector, collection date, represented period, version and access restrictions. Hash only if file execution is available; no hash has been computed here.
- G-04 / historical MFA: If MFA is a separate requested control objective, collect genuine historical configuration/change/log records. Otherwise keep E-05 as context rather than force-fitting it to AC-01.
Pack and delivery checklist
Include index, control register, E-01–E-05 manifest, period map, request tracker and gap register. Preserve restricted originals; redact approved derivative copies and record transformations. Confirm entity, system and environment; inspect readability and contradictions; obtain authorized review before external delivery. No evidence has been collected, approved or sent by this response.
Next steps
Confirm owner, system, deadline and repository; inspect supplied files; assign the open requests; record verified provenance and populations; update the pack with actual results. Set future quarterly evidence collection and freshness reminders in an authorized system.
Connects securely to your tools. The creator never sees your data.
About this skill
Turn scattered evidence into a traceable audit pack
Compliance Evidence Vault helps compliance, GRC, internal audit and control owners organize supplied policies, exports, logs, screenshots, tickets and approvals against an explicit control catalog and review period.
What it helps you produce
- Scope and control registers with evidence objectives and owners.
- Control-to-artifact matrices, manifests and provenance records.
- Evidence quality, freshness and historical period checks.
- Population and sample tracking using approved plans.
- Contradiction, gap and remediation registers with actionable collection requests.
- Navigable auditor packs and minimized customer assurance packs for authorized human review.
- Recurring collection and refresh plans when supported tools and permissions exist.
The workflow separates policy/design evidence from control operation and effectiveness. It preserves originals, records derivative redactions and refuses fabricated or backdated proof. Hashing and structured exports depend on file/code tools; connectors are optional and require authorized access. Without them, it prepares request lists and templates.
This is an instruction-based audit preparation skill, not a hosted evidence repository or certification service. Framework requirements must be supplied or verified; final audit conclusions belong to authorized assessors.
Organizing evidence does not prove compliance or operating effectiveness. Auditors may require additional testing or different evidence. Framework versions and requirements must be supplied or verified. Missing metadata, unreadable artifacts, incomplete populations and historical gaps reduce confidence. Current screenshots do not establish prior-period coverage. Collection, hashing, image inspection, exports and persistence depend on host tools; no built-in hosted vault or guaranteed certification.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
File Scopes
Read only the evidence and control catalog the user authorizes. Write manifests, trackers and approved redacted derivatives only in agreed output locations. Browsing/network and GRC, cloud, HR or ticketing connectors are optional and permission-dependent. Shell/code access is optional for hashes and structured exports. Preserve originals; never expose secrets. External delivery, production changes, access changes, approval or deletion requires explicit authorization. No accounts must be connected for manual planning.