agentleFS
ARCASSystemsARCASSystems/FounderOS/skills/data-security/SKILL.md

data-security

Skill7 starsChanged 19 days agoMITView on GitHub

Check whether data is safe to share with an external tool. Say "is this safe to paste", "can I send this to <tool>", or "classify this data". Fires before pasting, uploading, forwarding, or sending data to an external tool or AI model. Classifies the data and checks it against the user's data-handling policy.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the first available policy source.

    line 26
  2. Distinctive:

    If none of the above exist or yield a policy, use the default matrix below and tell the user it is a fallback.

    line 33
  3. Distinctive:

    If ambiguous, choose the more restrictive class.

    line 45
  4. Distinctive:

    Do not silently redact and proceed.

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Security

Runs on: reasoning - reads your files and reasons; any capable agent can run this.

Block unsafe data movement before it leaves the user's control.

When To Run

  • The founder is about to paste content into an AI tool.
  • A file is about to be uploaded to an external service.
  • Client, employee, financial, legal, health, or personal data is involved.
  • The tool is new, unlisted, or consumer-grade.
  • The user asks "can I paste this" or "is this safe to upload".

Pre-Read

Read the first available policy source. Skip a source silently if it does not exist; do not error out.

  1. rules/data-handling.md (likely absent on a fresh install - skip if missing)
  2. rules/approval-gates.md (or fall back to templates/rules/approval-gates.md)
  3. stack.json (lists which tools the user has approved)
  4. context/clients.md (per-client restrictions, if any are noted)

If none of the above exist or yield a policy, use the default matrix below and tell the user it is a fallback.

Data Classes

ClassExamplesDefault Tool Access
PublicPublished posts, public pages, public case studiesAny tool
InternalSOPs, internal notes, non-sensitive business plansPaid tools with business terms
Client generalClient name, project scope, public deal existenceTools with no-training terms or business agreement
Client sensitiveStrategy, financials, private messages, personal dataApproved tools only
RegulatedHealth, legal, banking, tax, ID, payroll, protected personal dataSpecific approved systems only

If ambiguous, choose the more restrictive class.

Tool Classes

Tool ClassExamplesAllowed Data
Approved secureEnterprise or API tools listed in the user's policyUp to the policy limit
Business paidPaid tools with no-training or business termsPublic, internal, client general if policy allows
Consumer or freeFree chat tools, unapproved browser toolsPublic only
UnknownAnything not listedPublic only

Procedure

  1. Identify the data involved.
  2. Classify the highest-risk data class.
  3. Identify the destination tool.
  4. Classify the tool class from policy or fallback.
  5. Compare data class to tool class.
  6. Return ALLOW, REDACT FIRST, or BLOCK.
  7. For BLOCK, name a safer tool or a local-only path.

Output Format

Data class: <class>
Tool class: <class>
Call: ALLOW | REDACT FIRST | BLOCK
Reason: <one sentence>
Safe path: <tool or local action>

Redaction Rule

Do not silently redact and proceed. Show what type of information must be removed, then ask the user to confirm the redacted version before using it.

Rules

  • Client-sensitive and regulated data never go to unknown tools.
  • Per-client restrictions override the generic matrix.
  • A one-time exception needs explicit human approval and a log entry.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.