Skip to content
Skills Library
Security · Review & audit

dataset-export-classification

/dataset-export-classification

Classify exported datasets by contents, ownership and destination, because an export is the copy most likely to leave the organization entirely. Use when export files, data dumps or report extracts exist inside the readable boundary

Repository
leaklens ↗
Licence
MIT
Last repository change
28.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Classify exported datasets by contents, ownership and destination, because an export is the copy most likely to leave the organization entirely. Use when export files, data dumps or report extracts exist inside the readable boundary

Original author description

Classify exported datasets by contents, ownership and destination, because an export is the copy most likely to leave the organization entirely. Use when export files, data dumps or report extracts exist inside the readable boundary

How it works

  1. Procedure
  2. Signals
  3. Patterns
  4. Pitfalls
  5. Done when
  6. References
Original SKILL.md headings · 61 lines, 371 words
SKILL.md preview
---
name: dataset-export-classification
description: "Classify exported datasets by contents, ownership and destination, because an export is the copy most likely to leave the organization entirely. Use when export files, data dumps or report extracts exist inside the readable boundary"
pack: leaklens
version: 1.0.0
category: data-tool
tags: [classify, exports, lineage]
---

# Dataset Export Classification

> Classify exported datasets by contents, ownership and destination, because an export is the copy most likely to leave the organization entirely

**Use when:** export files, data dumps or report extracts exist inside the readable boundary

**Avoid when:** no export artifact exists or the boundary excludes them in writing

## Procedure

1. List every export artifact with its format, row count and the date it appears to have been produced.
2. Read the header row only to classify the fields present, without reading data rows.
3. Assign each field a class from the ladder and record the class summary, not the values.
4. Trace where the export came from using naming, dates and any manifest alongside it.
5. Determine, from local evidence only, whether the destination of that copy is inside or outside the organization.
6. Classify by field classes and destination together, with retention and ownership where they are known.

## Signals

- An export contains personal-class fields with no manifest and no owner
- A file's date suggests it predates a retention change and was never refreshed
- The destination of the copy cannot be determined from anything in the tree
- A header row alone was enough to classify but the file was read in full anyway

## Patterns

**1. Export record**

```text
artifact: report-q3.csv | rows: 1580 | fields: id, email, plan | classes: personal | owner: unknown | destination: unknown | retention: none
```

**2. Header-only rule**

```text
read the header row to classify fields and stop; data rows are never opened when the ladder marks the class detect-only
```

**3. Destination rank**

```text
destination outside the organization outranks internal storage for the same fields; rank on destination first
```

## Pitfalls

- Reading data rows to be thorough when the header alone answers the classification question
- Reporting an export without saying where its copy went
- Assuming a recent file date means the content was reviewed

## Done when

- Each export records format, row count, field classes, owner, destination and retention
- Classification comes from the header row, with data rows left unopened

## References

- [NIST SP 800-53 - Information export controls](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final)
- [OWASP - Sensitive data discovery](https://owasp.org/www-project-web-security-testing-guide/)

Versions

The database has no other skills named dataset-export-classification.

Database snapshot: 13.11.2026 · package version 034ddfbe4188 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100export-scope-verification
    Confirm that export, report and download features only ever contain the requesting account's own data. Use when the product offers CSV, JSON or PDF export, scheduled reports or data downloads

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.