distill-shield

Embed identity markers and permissions into data bundles to deter AI distillation.

963|86|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/agenmod/immortal-skill --skill distill-shield
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distill-shield
Source: https://github.com/agenmod/immortal-skill/tree/main/distill-shield-skill
Command: npx skills add https://github.com/agenmod/immortal-skill --skill distill-shield

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill Shield helps individuals and organizations prevent unauthorized AI distillation of personal handover materials by embedding identity markers, licensing, and protective layers into data bundles.

Core Features & Use Cases

  • Identity-based protection: embeds implicit ownership markers to trace the source of a handover.
  • Licensing enforcement: machine-readable permissions to govern how AI can utilize the materials.
  • Protective layering: armor against automated distillation with detectable signals and cost-imposing measures.

Quick Start

Generate a shield bundle by running the shield_gen tool to produce CANARY.txt and SHIELD-MANIFEST.json.

Frequently Asked Questions about distill-shield

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

FAQPage Schema
How do I protect personal handover data from unauthorized AI distillation?

To protect personal handover data from unauthorized AI distillation, you can embed identity markers, machine-readable licensing, and protective layers into data bundles to trace ownership and deter automated leakage.

What is AI distillation and how do identity markers prevent it?

AI distillation is the automated extraction of data patterns. Identity markers prevent unauthorized distillation by embedding traceable source ownership signals directly into data bundles, making automated leakage detectable.

How do I generate a shield bundle with enforceable licensing permissions?

Generate a shield bundle by running the shield generation script to produce a CANARY.txt and SHIELD-MANIFEST.json, which encode identity markers and machine-readable permissions for auditability and enforcement.

Can I apply data protection measures to digital asset handovers across different domains?

Yes, data protection measures apply to personal data handovers, digital assets, and project handovers across domains by embedding identity encoding and enforceable licensing into the bundles.

What is the best way to enforce machine-readable permissions on project handover materials?

The best way to enforce machine-readable permissions on project handover materials is to generate a shield manifest that governs AI utilization and embeds detectable defense signals against unauthorized distillation.

Do I need a defined workflow to ensure traceability when protecting handover data?

Yes, a defined workflow is required to ensure traceability and enforcement, guiding users through identity encoding, licensing, and protective measures to establish detectable defense against unauthorized distillation.