anonymise

Remove configured PII columns from CSV files and save timestamped anonymised copies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sofer/.agents --skill anonymise
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anonymise
Source: https://github.com/sofer/.agents/tree/main/skills/anonymise
Command: npx skills add https://github.com/sofer/.agents --skill anonymise

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Anonymise CSV data by removing configured personal-identifying information to protect privacy and produce non-identifying outputs, while preserving non-sensitive data for analysis.

Core Features & Use Cases

  • Remove configured columns containing PII from CSV files based on a local config.txt.
  • Generate a timestamped output file and delete the original to prevent leakage.
  • Handles UTF-8 BOM and variable encodings, with graceful error handling.
  • Use Case: Securely prepare customer data extracts for reporting without exposing identifiers.

Quick Start

Run the anonymise script with a CSV file path or let it auto-detect a new CSV file in the current directory.

Frequently Asked Questions about anonymise

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

FAQPage Schema
How do I strip PII columns from CSV data for privacy compliance?

To strip PII from CSV data, configure a local config.txt file specifying which columns to remove, then run the script to produce an anonymised copy. It deletes the original file and saves a timestamped output to prevent data leakage.

Can I auto-detect new CSV files for anonymisation?

Yes, CSV anonymisation can auto-detect unprocessed CSV files in the current directory. If you run the script without a specific file path, it will automatically locate new files, strip configured PII columns, and generate a timestamped output.

Does this CSV anonymisation tool handle UTF-8 BOM encodings?

Yes, this CSV anonymisation tool handles UTF-8 BOM and variable encodings with graceful error handling. This ensures compatibility when stripping PII columns from datasets exported from various systems.

What is the best way to prepare customer data extracts for reporting without exposing identifiers?

The best way to prepare customer data extracts is to anonymise CSV files by removing configured PII columns based on a local config.txt. This preserves non-sensitive data for analysis while producing non-identifying, timestamped outputs.

Why does the original CSV file get deleted during PII removal?

The original CSV file is deleted during PII removal to prevent data leakage. After stripping configured columns, the script saves a timestamped, anonymised copy and removes the source file to ensure sensitive personal-identifying information is not retained.