[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAPTVXGD9C7NF03RWWWBVK":3,"skill-same:01M7FAPTVXGD9C7NF03RWWWBVK":53},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FAPTVXGD9C7NF03RWWWBVK","budgeting-and-forecasting",null,"Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fbudgeting-and-forecasting\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: budgeting-and-forecasting\ndescription: Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.\n---\n\n# Budgeting and forecasting\n\n## The budget is a commitment, the forecast is a belief\n\nKeep them separate. A budget re-cut every month is not a commitment; a forecast held to the original\nbudget is not a belief. Both failures make the numbers useless for different reasons.\n\n## Running the cycle\n\n1. **Set the frame first** — targets, headcount envelope, and the assumptions everyone builds on\n   (pricing, attrition, timing). Distributed teams building on different assumptions produces a\n   consolidation that cannot be reconciled.\n2. **Collect in a fixed template.** Free-form submissions cost more to normalize than to build.\n3. **Challenge the inputs**, specifically: what is the volume driver, what is this per unit, what\n   happens if it comes in at half. Budget submissions are negotiating positions and should be\n   treated as such without hostility.\n4. **Consolidate and find the gap** between bottom-up and top-down. There always is one. Close it\n   explicitly by cutting something named, not by proportional trimming — proportional cuts damage\n   the highest-return line as much as the lowest.\n5. **Publish what was not funded** and why. This prevents the same request arriving three times.\n\n## Rolling forecast\n\nRe-forecast on a fixed cadence over a constant horizon. Update only what has changed and say what\nchanged and why. A re-forecast with no narrative is a new set of numbers with no information in it.\n\n## Variance analysis\n\nVariance is only useful decomposed. For each material variance, separate:\n\n- **Volume** — did we do more or less of it?\n- **Rate** — did each unit cost or earn a different amount?\n- **Timing** — did it move between periods, or is it gone?\n- **Mix** — did the composition shift?\n\nTiming variances need no action and are constantly mistaken for performance. Rate variances on\nrecurring costs compound and are constantly under-reacted to.\n\nExplain the top few by value, not every line. A variance report covering everything gets read as\nnothing.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nPlanning: Anaplan, Pigment, Workday Adaptive Planning, Vena, Cube, and similar. A\nwell-built spreadsheet on a clean chart of accounts beats a planning tool nobody has been\nstaffed to maintain; move when budget owners outnumber the people who can hold the model\nin their head.\n\nDriver data comes from the ledger, the CRM, and the HRIS. The planning tool is only ever\nas current as those connections.\n\n## Never\n\n- Present a forecast without saying what changed since the last one.\n- Let a department own an assumption that drives another department's numbers.\n- Report accuracy without measuring it. Track forecast error over time — it improves quickly once\n  visible and never improves while unmeasured.\n","# Budgeting and forecasting\n\n## The budget is a commitment, the forecast is a belief\n\nKeep them separate. A budget re-cut every month is not a commitment; a forecast held to the original\nbudget is not a belief. Both failures make the numbers useless for different reasons.\n\n## Running the cycle\n\n1. **Set the frame first** — targets, headcount envelope, and the assumptions everyone builds on\n   (pricing, attrition, timing). Distributed teams building on different assumptions produces a\n   consolidation that cannot be reconciled.\n2. **Collect in a fixed template.** Free-form submissions cost more to normalize than to build.\n3. **Challenge the inputs**, specifically: what is the volume driver, what is this per unit, what\n   happens if it comes in at half. Budget submissions are negotiating positions and should be\n   treated as such without hostility.\n4. **Consolidate and find the gap** between bottom-up and top-down. There always is one. Close it\n   explicitly by cutting something named, not by proportional trimming — proportional cuts damage\n   the highest-return line as much as the lowest.\n5. **Publish what was not funded** and why. This prevents the same request arriving three times.\n\n## Rolling forecast\n\nRe-forecast on a fixed cadence over a constant horizon. Update only what has changed and say what\nchanged and why. A re-forecast with no narrative is a new set of numbers with no information in it.\n\n## Variance analysis\n\nVariance is only useful decomposed. For each material variance, separate:\n\n- **Volume** — did we do more or less of it?\n- **Rate** — did each unit cost or earn a different amount?\n- **Timing** — did it move between periods, or is it gone?\n- **Mix** — did the composition shift?\n\nTiming variances need no action and are constantly mistaken for performance. Rate variances on\nrecurring costs compound and are constantly under-reacted to.\n\nExplain the top few by value, not every line. A variance report covering everything gets read as\nnothing.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Tooling\n\nPlanning: Anaplan, Pigment, Workday Adaptive Planning, Vena, Cube, and similar. A\nwell-built spreadsheet on a clean chart of accounts beats a planning tool nobody has been\nstaffed to maintain; move when budget owners outnumber the people who can hold the model\nin their head.\n\nDriver data comes from the ledger, the CRM, and the HRIS. The planning tool is only ever\nas current as those connections.\n\n## Never\n\n- Present a forecast without saying what changed since the last one.\n- Let a department own an assumption that drives another department's numbers.\n- Report accuracy without measuring it. Track forecast error over time — it improves quickly once\n  visible and never improves while unmeasured.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fbudgeting-and-forecasting",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill budgeting-and-forecasting",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill budgeting-and-forecasting",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill budgeting-and-forecasting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fbudgeting-and-forecasting\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",937,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fbudgeting-and-forecasting\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"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":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]