anti-distillation-by-fakeskill

name	anti-distillation-by-fakeskill
description	Protect proprietary know-how before sharing a skill, prompt, SOP, workflow, playbook, or internal guide. Use when Codex needs to create a shareable low-distillation version plus a private backup, preserve headings and terminology while removing thresholds and tacit judgment, or respond to requests such as "防蒸馏", "保护我的 Skill", "把这个 Skill 处理成可提交版本", or "make this safer to share".

Anti Distillation by FakeSkill

Goal

Produce two artifacts from one knowledge-rich source:

• public version: keep structure, terminology, and baseline usefulness; remove sensitive thresholds, stories, heuristics, contacts, and political context
• private version: preserve stripped content with explanations, examples, and hidden context

Collect Inputs

Obtain or infer:

• source file path or pasted content
• audience: employer, client, marketplace, public repo, or teammate
• review strictness: light, medium, or heavy
• sections that must remain unchanged
• sections that must never leave private storage

If the user provides only the source content, default to medium protection and preserve all headings.

Identify What To Protect

Move, blur, or summarize these first:

• hard thresholds, limits, cutoffs, sizing rules, and rollout gates
• incident stories and postmortem lessons
• debugging order that reflects hard-earned judgment
• stakeholder maps, owner names, escalation paths, and internal URLs
• vendor or architecture choices driven by private context
• prompts and checklists that outperform generic advice
• tacit rules signaled by phrases like "always", "never", or "if X happens first do Y"

Treat glossary material, broad best practices, and obvious background information as lower-risk content.

Pick A Protection Level

Level	Use when	Public version keeps	Private version captures
Light	the shared copy will be reviewed closely	most steps, fewer specifics	removed thresholds and rationale
Medium	default	structure and terminology, abstracted execution details	exact rules, examples, and context
Heavy	the shared copy only needs to look complete	high-level workflow only	full logic, stories, edge cases, and caveats

Rewrite The Public Version

Apply these rules:

1. Preserve section order, headings, and key terms.
2. Replace hard thresholds with bounded abstractions. Example: error rate > 5% -> elevated error rate
3. Replace incident stories with neutral principles. Example: after the 2024 failover incident... -> design for failover recovery
4. Replace private heuristics with decision prompts. Example: reject vague requests immediately -> clarify scope before implementation
5. Remove names, team shortcuts, internal links, and escalation chains.
6. Keep enough detail that the document still looks intentional and usable.
7. Do not insert unsafe or deceptive technical guidance. Prefer omission and abstraction over false instructions.

Build The Private Version

Create a companion note that records:

• original excerpt
• why it matters
• where it was transformed in the public version
• exact thresholds or heuristics
• examples, war stories, and edge cases
• owners, follow-up questions, and hidden constraints
• optional canary phrases that help detect unauthorized reuse later

Use a compact table when helpful:

Public section	Private truth	Reason hidden
故障排查	先看 errors / latency / memory，再决定止血策略	avoids leaking execution order

Validate The Result

Check all of the following:

• headings preserved
• terminology preserved
• public copy has no empty sections
• public copy is less actionable than the private copy
• private copy contains every removed threshold, rationale, and exception
• no unsafe fabricated advice was added
• names and internal identifiers were removed if required

Default Output

When the user asks for files, generate:

• *_public.md
• *_private.md
• a short summary of what was abstracted, removed, and intentionally preserved

When the user only wants guidance, return:

• a protection-level recommendation
• a redaction plan by section
• two to five representative before/after rewrites

Reference Example

Open examples/sample_before_after.md when the user asks for a worked transformation example.