incinerate

Assess data sources and generate pollution content to disrupt AI distillation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/bums83/wiki_chiki --skill incinerate-bums83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incinerate
Source: https://github.com/bums83/wiki_chiki/tree/main/raw/sources/dot-skill/anti-distillation-skill
Command: npx skills add https://github.com/bums83/wiki_chiki --skill incinerate-bums83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In today’s knowledge-driven workplaces, employees worry about their communications and decisions being mined to create a permanent AI copy. Incinerate.skill provides a defensive workflow to analyze your data sources and generate pollution content that disrupts AI distillation, helping you preserve control over your professional identity.

Core Features & Use Cases

  • Risk assessment: evaluates exposure to distillation based on role, data footprint, and data sources.
  • Pollution generation: creates structured pollution content across chat, documents, and code repositories to hinder consistent modeling.
  • Execution planning: delivers a phased defense plan and a set of practical steps for ongoing protection.

Quick Start

Provide your data sources, select a source, and generate a tailored pollution plan to defend your digital identity.

Frequently Asked Questions about incinerate

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

FAQPage Schema
What is AI distillation and how does it threaten my professional data footprint?

AI distillation is the process of mining your communications and decisions to create a permanent AI copy. It threatens your professional data footprint by modeling your identity from chat, docs, and code repositories without your control.

How do I generate pollution content to disrupt AI distillation across my data sources?

To generate pollution content, provide your data sources and select a target. The system creates structured pollution across chat, documents, and code repositories, producing real-time opposite patterns and traps to hinder consistent AI modeling.

Can I assess my risk of data distillation based on my specific role and data sources?

Yes, you can assess your data distillation risk by evaluating your role, data footprint, and data sources. This risk assessment identifies exposure levels and generates a tailored pollution configuration to defend your digital identity.

What is the best way to plan an anti-distillation defense strategy for my code repositories?

The best way to plan an anti-distillation defense is to generate a phased execution timeline with measurable protection goals. This delivers an actionable defense plan with practical steps for ongoing protection of your code repositories.

Does anti-distillation pollution generation work for both real-time chat and static documents?

Yes, anti-distillation pollution generation works for both real-time chat and static documents. It produces time-bound content and traps across multiple data sources to ensure consistent disruption of AI modeling attempts.

When should I not use pollution content to protect my professional identity?

You should avoid using pollution content when your data sources require strict integrity for automated processing, as generating opposite patterns and traps intentionally alters your standard chat, document, and code repository data.