Agent skill · marketing growth · sundial-org
save-money
Auto-detect task complexity for Claude models (Haiku + Sonnet). Route simple tasks to Haiku, escalate complex ones to Sonnet. Save 50%+ on API costs. | 適用 Claude 模型（Haiku + Sonnet），自動偵測任務難度，簡單用 Haiku，複雜升級 Sonnet，輕鬆省下 50% 以上的費用。— RULES: Before responding, classify the task. If it matches an escalation trigger, call sessions_spawn with the full task and model anthropic/claude-sonnet-4-20250514 IMMEDIATELY. Do NOT answer complex tasks yourself. ESCALATE: analysis, comparisons, planning, strategy, code >10 lines, reports, proposals, multi-step reasoning, tables, outlines, charts, long writing >3 paragraphs, summarization, long translation. NEVER on Haiku: comparison tables, code >10 lines, multi-step analysis, reports, complex reasoning. STAY on Haiku: factual Q&A, definitions, greetings, reminders, short lookups, casual chat, 1-2 sentence tasks. When in doubt, escalate. Keep Haiku replies concise.
Why this skill is useful
Adds a specific escalation workflow for task complexity management that optimizes API usage and cost savings.
What it needs
About 4k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.
What this skill does
Save Money Run on Haiku by default. Only spawn Sonnet when the task actually needs it. Save 50%+ on API costs. CRITICAL: Classify First, Then Act Before generating ANY response, you MUST: 1. Check: does this task match ANY escalation trigger below? 2. If YES → call sessionsspawn() IMMEDIATELY. Do NOT attempt to answer yourself. 3. If NO → respond directly on the current model. When in doubt, escalate. A wrong escalation only costs a few cents. A bad answer on Haiku wastes the user's time. Rule of Thumb If a human would need more than 30 seconds of focused thinking, escalate. 如果一個人需要超過 30 秒的專注思考才能完成，就升級模型。 When to Escalate → MUST call sessionsspawn If the task matches ANY of the following, do NOT answer yourself. Instead, IMMEDIATELY call: Escalation triggers Analysis & evaluation — compare options, assess trade-offs, review documents Planning & strategy — project plans, roadmaps, business models, architecture Long-form writing — reports, proposals, articles, presentations, emails > 3 paragraphs Code generation — write functions, build features, refactor, debug complex issues Multi-step reasoning — anything with "first... then... finally" or numbered steps Summarize large content — long documents, full articles, meeting transcripts Long translation — paragraphs or full documents (not single sentences) Creative writing — copywriting, ad scripts, naming with brand constraints Structured output — tables, outlines, formatted documents, comparison charts By how people actually ask Language Escalate — real examples ---------- -------------------------- English "Can you analyze this for me?", "Write me a report on...", "Help me plan...", "What are the pros and cons?", "Build a script that...", "Compare A vs B", "Step by step, how do I...", "Draft a proposal for..." 繁體中文 "欸幫我看一下這個報告", "幫我想一下怎麼回客戶", "這兩個方案哪個比較好", "寫一封信給老闆", "幫我整理一下這份資料", "我該怎麼處理這個問題", "可以幫我寫一個程式嗎", "幫我規劃一下行程", "有什麼辦法可以改善", "這個東西要怎麼設計比較好" 日本語 "これを分析してもらえますか", "レポートを書いてください", "計画を立ててほしい", "AとBを比較して", "コードを書いてほし …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sundial-org/save-money