[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EFDJSDP9MBYP5JK337CA3H":3,"skill-same:01M7EFDJSDP9MBYP5JK337CA3H":46},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7EFDJSDP9MBYP5JK337CA3H","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbudgeting-and-forecasting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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## 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## 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","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fbudgeting-and-forecasting",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill budgeting-and-forecasting",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill budgeting-and-forecasting",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill budgeting-and-forecasting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fbudgeting-and-forecasting\u002FSKILL.md",true,[],[47,54,61,68,76,83],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"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},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\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},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\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":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]