skills/knowledge-distillation-survey/SKILL.md
Comprehensive survey of knowledge distillation methods, architectures, and applications in neural network compression
npx skillsauth add curiositech/windags-skills knowledge-distillation-surveyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Knowledge distillation transfers learning from teacher systems to students across capability gaps. The key insight: effective transfer requires matching knowledge type, teacher capacity, and transfer mechanism to the student's representational constraints.
1. ASSESS CAPACITY GAP
├── Small gap (teacher 1-2x student params) → Direct offline distillation
├── Large gap (teacher 10x+ student params) → Progressive with teacher assistants
└── Similar capacity/peer learning → Online collaborative distillation
2. IDENTIFY KNOWLEDGE TYPE NEEDED
├── Task needs final decisions → Response-based (soft labels, logits)
├── Task needs pattern recognition → Feature-based (intermediate representations)
├── Task needs structural reasoning → Relation-based (similarity matrices, attention maps)
└── Task needs multiple types → Multi-level distillation
3. SELECT TRANSFER MECHANISM
├── Proven expert + stable domain → Offline (sequential training)
├── Exploration needed + multiple learners → Online (mutual learning)
├── No external teacher available → Self-distillation (temporal/spatial)
└── Cross-modal/domain required → Alignment-based transfer
4. HANDLE REPRESENTATION GAPS
├── Same modality → Direct feature matching
├── Different modalities → Paired sample alignment
├── Different architectures → Attention transfer or feature adaptation
└── Different tasks → Structural knowledge extraction
| Teacher-Student Performance Ratio | Approach | Rationale | |-----------------------------------|----------|-----------| | 1.1-1.5x | Direct distillation | Student can decode teacher knowledge | | 1.5-3x | Add 1 teacher assistant | Bridge representational gap | | 3x+ | Multi-step progressive | Prevent knowledge loss in translation | | Similar performance | Collaborative learning | Mutual improvement through diversity |
Scenario: Compress GPT-3.5 (175B params) to run on mobile (500M params max)
Decision Process:
Execution:
Expert catches: Temperature needs adjustment per stage; mobile model needs different attention patterns optimized for inference speed
Scenario: Robot trained on RGB cameras must work with depth sensors only
Decision Process:
Execution:
Expert catches: Depth lacks color/texture info; student needs different attention for material properties
Task completion checklist for knowledge distillation:
Do NOT use knowledge distillation for:
transfer-learning-frameworks for task adaptationmodel-optimization-techniques for architecture efficiencycurriculum-learning-design for progressive skill buildingrobust-ai-validation for safety assurance firstexplainable-ai-methods - distillation often reduces interpretabilityDelegate to other skills:
neural-architecture-searchtransfer-learning-frameworksfew-shot-learning-strategiesrobust-ai-validationmodel-optimization-techniquesdata-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.