[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HA3BPVP0KCEEDZ152EHVN":3,"skill-same:01M70HA3BPVP0KCEEDZ152EHVN":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M70HA3BPVP0KCEEDZ152EHVN","token-budget-advisor",null,"Offer a choice of response depth (25%\u002F50%\u002F75%\u002F100%) with token estimates before answering, then answer at that level. Use when the user asks to control response length or token budget, such as 'token budget', 'short version', 'brief answer', 'respuesta corta vs larga', 'cuántos tokens', 'ahorrar tokens', 'responde al 50%', 'dame la versión corta', 'quiero controlar cuánto usas'. Skip if depth is already set this session or 'token' means an auth\u002Fpayment token.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-budget-advisor\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"Budget","token","token budget","token budget advisor","advisor","version","use","depth","session","tokens","answer","as","at","when","choice","short","auth","brief","community","SET","2026-11-10 10:12:30",false,"---\nname: token-budget-advisor\ndescription: Offer a choice of response depth (25%\u002F50%\u002F75%\u002F100%) with token estimates before answering, then answer at that level. Use when the user asks to control response length or token budget, such as 'token budget', 'short version', 'brief answer', 'respuesta corta vs larga', 'cuántos tokens', 'ahorrar tokens', 'responde al 50%', 'dame la versión corta', 'quiero controlar cuánto usas'. Skip if depth is already set this session or 'token' means an auth\u002Fpayment token.\nmetadata:\n  origin: community\n---\n\n# Token Budget Advisor (TBA)\n\nIntercept the response flow to offer the user a choice about response depth **before** Claude answers.\n\n## When to Use\n\n- User wants to control how long or detailed a response is\n- User mentions tokens, budget, depth, or response length\n- User says \"short version\", \"tldr\", \"brief\", \"al 25%\", \"exhaustive\", etc.\n- Any time the user wants to choose depth\u002Fdetail level upfront\n\n**Do not trigger** when: user already set a level this session (maintain it silently), or the answer is trivially one line.\n\n## How It Works\n\n### Step 1 — Estimate input tokens\n\nUse the repository's canonical context-budget heuristics to estimate the prompt's token count mentally.\n\nUse the same calibration guidance as [context-budget](..\u002Fcontext-budget\u002FSKILL.md):\n\n- prose: `words × 1.3`\n- code-heavy or mixed\u002Fcode blocks: `chars \u002F 4`\n\nFor mixed content, use the dominant content type and keep the estimate heuristic.\n\n### Step 2 — Estimate response size by complexity\n\nClassify the prompt, then apply the multiplier range to get the full response window:\n\n| Complexity   | Multiplier range | Example prompts                                      |\n|--------------|------------------|------------------------------------------------------|\n| Simple       | 3× – 8×          | \"What is X?\", yes\u002Fno, single fact                   |\n| Medium       | 8× – 20×         | \"How does X work?\"                                  |\n| Medium-High  | 10× – 25×        | Code request with context                           |\n| Complex      | 15× – 40×        | Multi-part analysis, comparisons, architecture      |\n| Creative     | 10× – 30×        | Stories, essays, narrative writing                  |\n\nResponse window = `input_tokens × mult_min` to `input_tokens × mult_max` (but don’t exceed your model’s configured output-token limit).\n\n### Step 3 — Present depth options\n\nPresent this block **before** answering, using the actual estimated numbers:\n\n```\nAnalyzing your prompt...\n\nInput: ~[N] tokens  |  Type: [type]  |  Complexity: [level]  |  Language: [lang]\n\nChoose your depth level:\n\n[1] Essential   (25%)  ->  ~[tokens]   Direct answer only, no preamble\n[2] Moderate    (50%)  ->  ~[tokens]   Answer + context + 1 example\n[3] Detailed    (75%)  ->  ~[tokens]   Full answer with alternatives\n[4] Exhaustive (100%)  ->  ~[tokens]   Everything, no limits\n\nWhich level? (1-4 or say \"25% depth\", \"50% depth\", \"75% depth\", \"100% depth\")\n\nPrecision: heuristic estimate ~85-90% accuracy (±15%).\n```\n\nLevel token estimates (within the response window):\n- 25%  → `min + (max - min) × 0.25`\n- 50%  → `min + (max - min) × 0.50`\n- 75%  → `min + (max - min) × 0.75`\n- 100% → `max`\n\n### Step 4 — Respond at the chosen level\n\n| Level            | Target length       | Include                                             | Omit                                              |\n|------------------|---------------------|-----------------------------------------------------|---------------------------------------------------|\n| 25% Essential    | 2-4 sentences max   | Direct answer, key conclusion                       | Context, examples, nuance, alternatives           |\n| 50% Moderate     | 1-3 paragraphs      | Answer + necessary context + 1 example              | Deep analysis, edge cases, references             |\n| 75% Detailed     | Structured response | Multiple examples, pros\u002Fcons, alternatives          | Extreme edge cases, exhaustive references         |\n| 100% Exhaustive  | No restriction      | Everything — full analysis, all code, all perspectives | Nothing                                        |\n\n## Shortcuts — skip the question\n\nIf the user already signals a level, respond at that level immediately without asking:\n\n| What they say                                      | Level |\n|----------------------------------------------------|-------|\n| \"1\" \u002F \"25% depth\" \u002F \"short version\" \u002F \"brief answer\" \u002F \"tldr\"  | 25%   |\n| \"2\" \u002F \"50% depth\" \u002F \"moderate depth\" \u002F \"balanced answer\"        | 50%   |\n| \"3\" \u002F \"75% depth\" \u002F \"detailed answer\" \u002F \"thorough answer\"       | 75%   |\n| \"4\" \u002F \"100% depth\" \u002F \"exhaustive answer\" \u002F \"full deep dive\"     | 100%  |\n\nIf the user set a level earlier in the session, **maintain it silently** for subsequent responses unless they change it.\n\n## Precision note\n\nThis skill uses heuristic estimation — no real tokenizer. Accuracy ~85-90%, variance ±15%. Always show the disclaimer.\n\n## Examples\n\n### Triggers\n\n- \"Give me the short version first.\"\n- \"How many tokens will your answer use?\"\n- \"Respond at 50% depth.\"\n- \"I want the exhaustive answer, not the summary.\"\n- \"Dame la version corta y luego la detallada.\"\n\n### Does Not Trigger\n\n- \"What is a JWT token?\"\n- \"The checkout flow uses a payment token.\"\n- \"Is this normal?\"\n- \"Complete the refactor.\"\n- Follow-up questions after the user already chose a depth for the session\n\n## Source\n\nStandalone skill from [TBA — Token Budget Advisor for Claude Code](https:\u002F\u002Fgithub.com\u002FXabilimon1\u002FToken-Budget-Advisor-Claude-Code-).\nOriginal project also ships a Python estimator script, but this repository keeps the skill self-contained and heuristic-only.\n","# Token Budget Advisor (TBA)\n\nIntercept the response flow to offer the user a choice about response depth **before** Claude answers.\n\n## When to Use\n\n- User wants to control how long or detailed a response is\n- User mentions tokens, budget, depth, or response length\n- User says \"short version\", \"tldr\", \"brief\", \"al 25%\", \"exhaustive\", etc.\n- Any time the user wants to choose depth\u002Fdetail level upfront\n\n**Do not trigger** when: user already set a level this session (maintain it silently), or the answer is trivially one line.\n\n## How It Works\n\n### Step 1 — Estimate input tokens\n\nUse the repository's canonical context-budget heuristics to estimate the prompt's token count mentally.\n\nUse the same calibration guidance as [context-budget](..\u002Fcontext-budget\u002FSKILL.md):\n\n- prose: `words × 1.3`\n- code-heavy or mixed\u002Fcode blocks: `chars \u002F 4`\n\nFor mixed content, use the dominant content type and keep the estimate heuristic.\n\n### Step 2 — Estimate response size by complexity\n\nClassify the prompt, then apply the multiplier range to get the full response window:\n\n| Complexity   | Multiplier range | Example prompts                                      |\n|--------------|------------------|------------------------------------------------------|\n| Simple       | 3× – 8×          | \"What is X?\", yes\u002Fno, single fact                   |\n| Medium       | 8× – 20×         | \"How does X work?\"                                  |\n| Medium-High  | 10× – 25×        | Code request with context                           |\n| Complex      | 15× – 40×        | Multi-part analysis, comparisons, architecture      |\n| Creative     | 10× – 30×        | Stories, essays, narrative writing                  |\n\nResponse window = `input_tokens × mult_min` to `input_tokens × mult_max` (but don’t exceed your model’s configured output-token limit).\n\n### Step 3 — Present depth options\n\nPresent this block **before** answering, using the actual estimated numbers:\n\n```\nAnalyzing your prompt...\n\nInput: ~[N] tokens  |  Type: [type]  |  Complexity: [level]  |  Language: [lang]\n\nChoose your depth level:\n\n[1] Essential   (25%)  ->  ~[tokens]   Direct answer only, no preamble\n[2] Moderate    (50%)  ->  ~[tokens]   Answer + context + 1 example\n[3] Detailed    (75%)  ->  ~[tokens]   Full answer with alternatives\n[4] Exhaustive (100%)  ->  ~[tokens]   Everything, no limits\n\nWhich level? (1-4 or say \"25% depth\", \"50% depth\", \"75% depth\", \"100% depth\")\n\nPrecision: heuristic estimate ~85-90% accuracy (±15%).\n```\n\nLevel token estimates (within the response window):\n- 25%  → `min + (max - min) × 0.25`\n- 50%  → `min + (max - min) × 0.50`\n- 75%  → `min + (max - min) × 0.75`\n- 100% → `max`\n\n### Step 4 — Respond at the chosen level\n\n| Level            | Target length       | Include                                             | Omit                                              |\n|------------------|---------------------|-----------------------------------------------------|---------------------------------------------------|\n| 25% Essential    | 2-4 sentences max   | Direct answer, key conclusion                       | Context, examples, nuance, alternatives           |\n| 50% Moderate     | 1-3 paragraphs      | Answer + necessary context + 1 example              | Deep analysis, edge cases, references             |\n| 75% Detailed     | Structured response | Multiple examples, pros\u002Fcons, alternatives          | Extreme edge cases, exhaustive references         |\n| 100% Exhaustive  | No restriction      | Everything — full analysis, all code, all perspectives | Nothing                                        |\n\n## Shortcuts — skip the question\n\nIf the user already signals a level, respond at that level immediately without asking:\n\n| What they say                                      | Level |\n|----------------------------------------------------|-------|\n| \"1\" \u002F \"25% depth\" \u002F \"short version\" \u002F \"brief answer\" \u002F \"tldr\"  | 25%   |\n| \"2\" \u002F \"50% depth\" \u002F \"moderate depth\" \u002F \"balanced answer\"        | 50%   |\n| \"3\" \u002F \"75% depth\" \u002F \"detailed answer\" \u002F \"thorough answer\"       | 75%   |\n| \"4\" \u002F \"100% depth\" \u002F \"exhaustive answer\" \u002F \"full deep dive\"     | 100%  |\n\nIf the user set a level earlier in the session, **maintain it silently** for subsequent responses unless they change it.\n\n## Precision note\n\nThis skill uses heuristic estimation — no real tokenizer. Accuracy ~85-90%, variance ±15%. Always show the disclaimer.\n\n## Examples\n\n### Triggers\n\n- \"Give me the short version first.\"\n- \"How many tokens will your answer use?\"\n- \"Respond at 50% depth.\"\n- \"I want the exhaustive answer, not the summary.\"\n- \"Dame la version corta y luego la detallada.\"\n\n### Does Not Trigger\n\n- \"What is a JWT token?\"\n- \"The checkout flow uses a payment token.\"\n- \"Is this normal?\"\n- \"Complete the refactor.\"\n- Follow-up questions after the user already chose a depth for the session\n\n## Source\n\nStandalone skill from [TBA — Token Budget Advisor for Claude Code](https:\u002F\u002Fgithub.com\u002FXabilimon1\u002FToken-Budget-Advisor-Claude-Code-).\nOriginal project also ships a Python estimator script, but this repository keeps the skill self-contained and heuristic-only.\n",{"name":5,"metadata":49,"description":7},{"origin":42},"main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-budget-advisor",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill token-budget-advisor",{"tool":64,"command":65},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill token-budget-advisor",{"tool":67,"command":68},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill token-budget-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftoken-budget-advisor\u002FSKILL.md",true,[],[73,81,89,96,103,110],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":80},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":88},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":88},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":88},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":88},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]