down-skilling

Solid

Distill Opus-level reasoning into optimized instructions for Haiku 4.5 (and Sonnet). Generates explicit, procedural prompts with n-shot examples that maximize smaller model performance on a given task. Use when user says "down-skill", "distill for Haiku", "optimize for Haiku", "make this work on Haiku", "generate Haiku instructions", or needs to delegate a task to a smaller model with high reliability.

AI & Automation 134 stars 7 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Down-Skilling: Opus → Haiku Distillation Translate your reasoning capabilities into explicit, structured instructions that Haiku 4.5 can execute reliably. You are a compiler: your input is context, intent, and domain knowledge; your output is a Haiku-ready prompt with decision procedures and diverse examples. ## Core Principle Opus infers from WHY. Haiku executes from WHAT and HOW. Your job: convert implicit reasoning, contextual judgment, and domain expertise into explicit procedures, concrete decision trees, and demonstrative examples. Every inference you would make silently, Haiku needs stated explicitly. ## Economics: Why Examples Are Free Opus 4.8 costs 5× Haiku 4.5 on both sides ($5/$25 vs $1/$5 per MTok; 2026-07 pricing). A task that costs $1.00 on Opus costs ~$0.20 on Haiku — but only if Haiku gets it right on the first try. One retry halves the savings; a few retries makes Haiku more expensive. **The math that matters:** - Input tokens are cheap (Haiku 4.5: $1.00/MTok input vs $5.00/MTok output) - Adding 2,000 tokens of examples costs ~$0.002 per call - A single failed-then-retried call costs ~$0.008+ in wasted output - **Examples pay for themselves if they prevent even 1-in-5 retries** **What this means for prompt design:** - If you're sending an 8K token document, you can afford 3-4K tokens of examples — the examples cost less than the document itself - Lengthy input prompts don't inflate output costs — output pricing is independent of input length - ...

Details

Author
oaustegard
Repository
oaustegard/claude-skills
Created
9 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

cost-lean-orchestration

Token-efficient model routing for complex engineering sessions. The main model (Opus / Fable, high reasoning) never bulk-reads or explores — it delegates all exploration, bulk file reading, codebase search, log scanning, dependency tracing, and documentation reading to Sonnet subagents that return compact structured findings, and it spends its own tokens only on synthesis, architecture, judgment, and final code. Use this skill in EVERY session that involves reading more than a couple of files, exploring or mapping a codebase, investigating a bug, auditing call sites, reviewing a large diff, digesting logs or docs, or any multi-step engineering task — even if the user never mentions cost, tokens, subagents, or delegation. This is a standing operating discipline, not an on-request feature.

0 Updated 2 weeks ago
itzTiru
AI & Automation Listed

token-efficient-skill-optimizer

Audit and optimize an existing AI skill, system prompt, agent instruction set, or workflow for token/cost efficiency WITHOUT degrading quality or safety — evidence-backed rules, honest measurement (measured/estimated/projected labels enforced by a validator), reviewable diffs, before/after benchmarks. Use when the user wants to cut a skill's or prompt's token cost, context footprint, or API spend; audit why an agent is expensive; validate someone's claimed token savings; or batch-audit a skills directory. Triggers: "optimize this skill/prompt", "cut token costs", "why is this agent so expensive", "audit my skill", "is this optimization real", "לייעל את הסקיל", "לחסוך טוקנים", "כמה עולה הסקיל הזה", "בדוק את החיסכון". Do NOT use for one-off prompt-wording help that won't be saved as a reusable artifact (answer directly), for authoring a brand-new skill from scratch (use skill-creator / token-efficient-skill-builder), or for optimizing a skill whose purpose is harmful — refuse those.

1 Updated 2 days ago
yosishe
AI & Automation Listed

token-efficiency

Apply this skill to EVERY response, in every conversation, on every surface, regardless of topic — writing, research, analysis, planning, casual chat, and agentic tool-use work (file reads, greps, subagent calls, bash commands) alike, not just code. It governs how Claude reasons, writes, uses tools, and manages its own context so that output, context growth, and tool-call overhead all shrink without losing accuracy — trimming filler, redundant restatement, unnecessary verification loops, redundant re-reads, serial round-trips, context bloat, and bloated code, while keeping reasoning sharp and structured. Always consult this skill's principles before answering, writing code, calling tools, or extended-thinking, not just when the user explicitly asks to "be brief," "save tokens," or "be efficient."

0 Updated 6 days ago
denfry