content-desensitization

Redact sensitive patterns from content and output a diff-ready summary.

1|Updated Jun 14, 2021

Search Tags:#guidelines #privacy #redaction #pii #content-editing #desensitization

Ready to run

npx skills add https://github.com/XingMXTeam/maoxunxing.com --skill content-desensitization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-desensitization
Source: https://github.com/XingMXTeam/maoxunxing.com/tree/main/.qoder/skills/content-desensitization
Command: npx skills add https://github.com/XingMXTeam/maoxunxing.com --skill content-desensitization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Redact sensitive information before publishing content publicly. Use when preparing content for public sharing to prevent leakage of PII, internal identifiers, or confidential terms.

Core Features & Use Cases

Identify sensitive patterns (PII, internal names, internal config keys) and replace with generic placeholders
Preserve meaning and readability while removing sensitive details
Ensure consistency across translations and versions
Provide a diff or summary of changes for review

Quick Start

Replace all sensitive identifiers in your draft with neutral terms in one pass.

Frequently Asked Questions about content-desensitization

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

FAQPage Schema

How do I redact PII and sensitive identifiers from content before publishing?▼

Redact PII and sensitive identifiers by replacing internal names, config keys, and personal data with generic placeholders, ensuring the original content meaning is preserved for safe public sharing.

What is the best way to mask sensitive information in code samples and documents?▼

The best way to mask sensitive information in code samples and documents is pattern replacement, swapping internal identifiers with neutral terms while preserving readability and ensuring consistent replacements across versions.

Does content desensitization work across multiple languages and translations?▼

Yes, content desensitization ensures consistent replacements across languages and versions, applying uniform generic placeholders to translated content to prevent leaking confidential terms.

Can I review what sensitive patterns were changed during the redaction process?▼

Yes, you can review changes because the redaction process outputs a diff-ready summary detailing all sensitive patterns identified and replaced, allowing you to verify safety before publishing.

When do I need to redact sensitive content for public sharing?▼

You need to redact sensitive content when preparing blog posts, documents, or code samples for public sharing to prevent the leakage of PII, internal identifiers, or confidential terms.

How do I ensure redacted content remains readable after removing confidential terms?▼

Ensure readability by replacing sensitive patterns with generic terms that fit the context, preserving the original meaning and document flow while removing all confidential details.