audit-intake-and-evidence-map

Plans privacy, zero-knowledge, and E2EE audits by scoping claims and mapping evidence into a manifest.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill audit-intake-and-evidence-map-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-intake-and-evidence-map
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-privacy-audit/skills/audit-intake-and-evidence-map
Command: npx skills add https://github.com/bpcakes/jig-skills --skill audit-intake-and-evidence-map-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Privacy, zero-knowledge, and E2EE audits often start without clear scope, authorization boundaries, or an inventory of available evidence, leading to unfocused testing and unsupported conclusions. This Skill structures the intake phase so every claim, data class, flow, and artifact is captured before analysis begins. ## Core Features & Use Cases - Scoped Audit Planning: Converts privacy claims from policies, app store disclosures, and whitepapers into testable audit questions with explicit in-scope and out-of-scope boundaries. - Machine-Readable Manifest: Produces an audit-manifest.json validated against a JSON Schema, with stable IDs linking claims, data classes, flows, evidence requests, limitations, and failure signals. - Refusal and Limitation Handling: Records authorization gaps, partial evidence, and unsafe request conditions early, and recommends the next privacy-audit skills based on risk. - Use Case: A team claims their app is end-to-end encrypted. Use this Skill to inventory the claims, map available network captures and source code to those claims, and generate a manifest that hands off to crypto and network analysis skills. ## Quick Start Ask the agent to plan a privacy audit for your app by scoping the E2EE claims and producing an audit-manifest.json from the evidence you have available.

Frequently Asked Questions about audit-intake-and-evidence-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a privacy or E2EE audit before testing?

Start with an intake phase that inventories claims, data classes, user flows, and available evidence, then record them in a structured manifest. This Skill converts each claim into testable audit questions and classifies evidence as available, requested, blocked, or out of scope.

What is an audit manifest for zero-knowledge verification?

An audit manifest is a machine-readable JSON file linking claims, data classes, flows, and evidence with stable IDs. It uses a JSON Schema for validation so later findings can cite the same claims and artifacts throughout the audit.

Does this audit intake require access to production systems?

No. Authorization boundaries are confirmed first, and the intake explicitly supports test accounts, staging, synthetic data, and redacted artifacts. Requests requiring unauthorized access, credential bypass, or live customer data are refused with safer alternatives offered.

When should I skip the audit intake and evidence mapping phase?

Skip intake when you have a focused question with supplied code, captures, or an already established scope. Narrow privacy, encryption, telemetry, or remediation analysis can go directly to the relevant analysis skill without a manifest.

What frameworks does the privacy audit intake reference?

It uses OWASP ASVS and MASVS for web, API, and mobile verification surfaces, plus the NIST Privacy Framework for privacy risk framing. These are used only for scope orientation, not as compliance certifications.