Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    AI Data Exposure and Vendor Risk Assessor

    1

    AI Data Exposure and Vendor Risk Assessor runs that assessment.

    $14

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    2 installsSecurity scanned
    AI Data Exposure and Vendor Risk Assessor

    AI Data Exposure and Vendor Risk Assessor

    Example session with this skill installed

    We want to use a hosted LLM vendor's enterprise API tier to summarize our internal product roadmap and customer feedback logs. Which parts are safe to send, which need controls, and what should we get in writing from the vendor first?

    • Read your context and instructions
    • Compiled the ai data exposure

    Assessment Summary

    Data Classification:

    • Product Roadmap: Proprietary moat (high sensitivity; value depends on exclusivity).
    • Customer Feedback Logs: Regulated / contractual (likely contains PII).

    Exposure Vectors to Verify for This Tier (do not assume — confirm in writing):

    • Training on inputs: is your data excluded from model training on this tier?
    • Retention: how long are inputs/outputs stored, and is a zero-retention option available?
    • Human review: is there human review for safety/abuse monitoring, and can it be scoped or opted out of?
    • Sub-processors and jurisdiction: who else processes the data, and in which regions?
    • Output memorization: any risk of your content surfacing in other users' outputs?

    Recommendation (per data type):

    • Roadmap: Send with controls — redact unreleased project names/dates; require a written no-training commitment before sending; otherwise keep in-house.
    • Feedback Logs: Send with controls — scrub or pseudonymize PII and minimize fields; confirm the DPA covers this use.

    Questions to Get in Writing from the Vendor:

    • Does our contract/DPA include a no-training and zero- or limited-retention option on this tier?
    • Can we opt out of or scope any human review / safety logging?
    • Who are the sub-processors and what are the data residency options?

    Note: This is decision-support, not legal advice, and it does not assert what any specific vendor does with your data — tier terms vary and change, so confirm the above directly with the vendor and your counsel.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Classify data sensitivity to determine if it belongs in a public or private LLM.Evaluate vendor-specific exposure like model training and human review policies.Generate precise due diligence questions for AI vendor security reviews.Establish technical controls like redaction or pseudonymization for AI workflows.

    About this skill

    Sending data to an AI vendor is now a routine decision made with almost no structure, and the anxiety is real: is the proprietary corpus that is our moat about to train a competitor's model, is customer data leaving our control, what does this vendor actually retain? The honest answer is usually nuanced — some data is completely fine to send to an enterprise zero-retention tier, and some genuinely should never leave your environment — but teams rarely have a way to tell which is which. AI Data Exposure and Vendor Risk Assessor runs that assessment. Describe the data, the use case, and the vendor and tier, and it classifies each data element as moat, regulated, contractual, or low-sensitivity; maps the real exposure vectors for that tier — training on inputs, retention, sub-processors, output memorization, jurisdiction — and distinguishes default consumer behavior from enterprise and self-hosted terms, which are often opposite; lists the exact questions to get in writing from the vendor before anything is sent; and gives a tiered recommendation per data type: send freely, send with specific controls (redaction, minimization, a no-training agreement, region restriction), or keep in-house. It is even-handed, not anti-AI — the right answer is often that the data is fine on an enterprise no-training tier, and it says so — and it reserves the highest bar for the true moat, whose value depends on exclusivity. The download includes three reference files: the data-sensitivity worksheet, an exposure-vectors and vendor-questions guide, and a worked sample assessment. It is decision-support, not legal advice, and it does not assert what any named vendor does with your data — terms vary by tier and change, so it tells you what to verify directly. Works with Claude Code, Cursor, Codex CLI, Gemini CLI, and any SKILL.md agent.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    2 installs

    Downloaded by developers to date

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 3 months ago

    • Passed all security checks, Safe to install

    Listed3 months ago
    Updated2 days ago

    What's inside

    Frequently Asked Questions