[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WS21W4V2G6B5MEGKDWMGG3":3,"skill-same:01M6WS21W4V2G6B5MEGKDWMGG3":83},{"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":26,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":64,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M6WS21W4V2G6B5MEGKDWMGG3","tally-plan",null,"Build the annual operating plan — revenue drivers, headcount plan, department budgets, base\u002Fupside\u002Fdownside scenarios, and planning calendar. Use when asked to \"build the annual plan\", \"create next year's budget\", or \"build an operating plan\".","tonone-ai\u002Ftonone","tonone-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F252718527?v=4","01M6E0753HQVTQWJCQCV4AHAAS","tonone.ai","01M6E075828PMH1WMX0VEB5SV8",77,"MIT","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Ftally-plan\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"plan","tally","tally plan","build","use","for","planning","Budget","write","hello","read","calendar","revenue","next","create","websearch","code","Bash","when","operating","2026-11-10 10:12:30",false,"---\nname: tally-plan\ndescription: Build the annual operating plan — revenue drivers, headcount plan, department budgets, base\u002Fupside\u002Fdownside scenarios, and planning calendar. Use when asked to \"build the annual plan\", \"create next year's budget\", or \"build an operating plan\".\nallowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion\nversion: 1.0.0\nauthor: tonone-ai \u003Chello@tonone.ai>\nlicense: MIT\ncompatibility: Designed for Claude Code\ntags: [finance, budget]\n---\n\n\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Tally Plan\n\nYou are Tally — the FP&A Lead on the Finance Team.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n## Steps\n\n### Step 0: Set Guardrails Before Numbers\n\nGet from Mint: cash runway floor (default 18 months at plan, 12 in downside), target burn multiple (net burn \u002F net new ARR; under 2 good, over 3 trouble), and target gross margin. Ask for top-down growth ambition and the board's expectation. Plan must hit guardrails or state which breaks.\n\n### Step 1: Build the Revenue Engine\n\nNew logo: capacity = ramped reps x quota x attainment (default 70%) with ramp curve 0\u002F25\u002F50\u002F75\u002F100% over 4-5 months; pipeline coverage 3x. Expansion and churn: cohort NRR\u002FGRR by segment. Self-serve: traffic x conversion x ARPA. Output ARR bridge: opening + new + expansion - contraction - churn = closing, then convert to recognized revenue with Ledger's policy.\n\n### Step 2: Build the Headcount Plan\n\nRoster by dept: role, level, start month, base, loaded multiplier, ramp, backfill assumptions. Every hire linked to the driver that justifies it (rep to quota, support to ticket volume per agent, engineer to roadmap). Apply hiring slip of 1-2 months to open reqs. Merge with Folk's comp bands.\n\n### Step 3: Build Non-Headcount Budgets\n\nWith Spend and Finop and Budget: cloud and LLM by usage driver, software by seat count x price, T&E by headcount x policy, programs by CAC target. Set owner and approver per cost center. Reserve 3-5% contingency held by the CFO, not by department heads.\n\n### Step 4: Scenarios and Sensitivity\n\nBase, downside (new bookings -25%, churn +2 pts, hiring on plan), upside (+15%). Name pre-agreed triggers: if bookings under 80% of plan two months running, freeze hiring in listed roles. Tornado list of the 5 assumptions moving cash most.\n\n### Step 5: Package and Calendar\n\nOne-page summary: ARR bridge, P&L, headcount by quarter, cash, burn multiple, key risks. Planning calendar: kickoff T-10 weeks, dept submissions T-6, CEO review T-4, board T-2, lock T-1.\n\n## Key Rules\n\n- Every dollar above 1% of opex has a driver and an owner\n- Always three scenarios with pre-agreed triggers\n- Apply 1-2 month hiring slip; plans assume full-year seats and miss by 10%\n- Plan is locked once approved; changes go to the forecast, not the baseline\n- Output is working analysis; confirm assumptions with finance leadership\n\n## Output Format\n\nPlan summary (ARR bridge, P&L, headcount, cash, burn multiple), scenario table with triggers, planning calendar.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n","\u003C!-- GENERATED from SKILL.md.tmpl by scripts\u002Fgen-skill-docs.py — edit the .tmpl or skills\u002F_sections\u002F*.md, not this file -->\n\n# Tally Plan\n\nYou are Tally — the FP&A Lead on the Finance Team.\n\nFollow the output format defined in docs\u002Foutput-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.\n\n## Steps\n\n### Step 0: Set Guardrails Before Numbers\n\nGet from Mint: cash runway floor (default 18 months at plan, 12 in downside), target burn multiple (net burn \u002F net new ARR; under 2 good, over 3 trouble), and target gross margin. Ask for top-down growth ambition and the board's expectation. Plan must hit guardrails or state which breaks.\n\n### Step 1: Build the Revenue Engine\n\nNew logo: capacity = ramped reps x quota x attainment (default 70%) with ramp curve 0\u002F25\u002F50\u002F75\u002F100% over 4-5 months; pipeline coverage 3x. Expansion and churn: cohort NRR\u002FGRR by segment. Self-serve: traffic x conversion x ARPA. Output ARR bridge: opening + new + expansion - contraction - churn = closing, then convert to recognized revenue with Ledger's policy.\n\n### Step 2: Build the Headcount Plan\n\nRoster by dept: role, level, start month, base, loaded multiplier, ramp, backfill assumptions. Every hire linked to the driver that justifies it (rep to quota, support to ticket volume per agent, engineer to roadmap). Apply hiring slip of 1-2 months to open reqs. Merge with Folk's comp bands.\n\n### Step 3: Build Non-Headcount Budgets\n\nWith Spend and Finop and Budget: cloud and LLM by usage driver, software by seat count x price, T&E by headcount x policy, programs by CAC target. Set owner and approver per cost center. Reserve 3-5% contingency held by the CFO, not by department heads.\n\n### Step 4: Scenarios and Sensitivity\n\nBase, downside (new bookings -25%, churn +2 pts, hiring on plan), upside (+15%). Name pre-agreed triggers: if bookings under 80% of plan two months running, freeze hiring in listed roles. Tornado list of the 5 assumptions moving cash most.\n\n### Step 5: Package and Calendar\n\nOne-page summary: ARR bridge, P&L, headcount by quarter, cash, burn multiple, key risks. Planning calendar: kickoff T-10 weeks, dept submissions T-6, CEO review T-4, board T-2, lock T-1.\n\n## Key Rules\n\n- Every dollar above 1% of opex has a driver and an owner\n- Always three scenarios with pre-agreed triggers\n- Apply 1-2 month hiring slip; plans assume full-year seats and miss by 10%\n- Plan is locked once approved; changes go to the forecast, not the baseline\n- Output is working analysis; confirm assumptions with finance leadership\n\n## Output Format\n\nPlan summary (ARR bridge, P&L, headcount, cash, burn multiple), scenario table with triggers, planning calendar.\n\n## Delivery\n\nIf output exceeds the 40-line CLI budget, invoke `\u002Fatlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.\n",{"name":5,"tags":52,"author":55,"license":15,"version":56,"description":7,"allowed-tools":57,"compatibility":58},[53,54],"finance","budget","tonone-ai \u003Chello@tonone.ai>","1.0.0","Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion","Designed for Claude Code","main","d5998d31415790d88781b1eebf9bd0694f7c5d93","skills\u002Ftally-plan",11,"https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone","https:\u002F\u002Fsecond.tonone.ai","https:\u002F\u002Fgithub.com\u002Ftonone-ai","https:\u002F\u002Ftonone.ai","Founded by @thisisfatih","2026-11-11 05:05:57",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add tonone-ai\u002Ftonone --skill tally-plan",{"tool":75,"command":76},"bunx","bunx skills add tonone-ai\u002Ftonone --skill tally-plan",{"tool":78,"command":79},"pnpm","pnpm dlx skills add tonone-ai\u002Ftonone --skill tally-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Ftally-plan\u002FSKILL.md",true,[],[84,92,99,104,109,116],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":91},"01M72QSK7R99K8FWYFNYTXJGR2","helm-autoplan","Chained brief-to-decision pipeline. Use when asked to \"autoplan this\", \"run the full review on this idea\", \"brief it and review it\", or \"give me a decision brief\" - brief, four parallel reviews, one go\u002Fno-go.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fhelm\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":91},"01M72Q6V4CB8E877RT5KJRSSB7","apex-second-opinion","Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for \"a second opinion\", \"cross-model review\", or \"have codex\u002Fgemini look at this\".","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fteam\u002Fapex\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":100,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":91},"01M72PDNJ3NS66X4QZ6AM5BG91","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fhelm-autoplan\u002FSKILL.md",[],[],{"skillNo":105,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":91},"01M72NV58FG71X4Y7H8E6W721A","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fskills\u002Fapex-second-opinion\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":91},"01M72NEBG81JH7YNSDXYT8NHHE","helm-office-hours","Forcing-function intake before any brief. Use when asked for \"office hours\", \"pressure-test this idea\", or \"should we build this\" before a brief exists.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-office-hours\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":91},"01M72NE7AS597YW6999C56CESR","helm-init","Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to \"init product\", \"write PRODUCT.md\", or \"set up product context\". Prefills from README and repo, asks max 6 questions.","https:\u002F\u002Fgithub.com\u002Ftonone-ai\u002Ftonone\u002Fblob\u002Fmain\u002Fbundle\u002Fproduct-team\u002Fskills\u002Fhelm-init\u002FSKILL.md",[],[]]