[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AYAHTNT9Q4GQS8AT39CC7":3,"skill-same:01M69AYAHTNT9Q4GQS8AT39CC7":62},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M69AYAHTNT9Q4GQS8AT39CC7","spend-analysis",null,"Use when a finance director asks which synthetic category is over budget or approaching a limit.","microsoft\u002Faibast-agents-library","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69ACKE6NWSADP5WEMFXBPPJ",8,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Fprocurement-agent\u002Fmanual\u002Fskills\u002Faibast_spend-analysis_04\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000040","财务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33],"spend analysis","analysis","finance","Budget","use","director","synthetic","limit","which","when","2026-11-10 10:12:30",false,"---\nname: spend-analysis\ndescription: Use when a finance director asks which synthetic category is over budget or approaching a limit.\n---\n\u003C!-- bic:source=blank -->\n# Spend and budget review\n\nUse when a finance director asks which synthetic category is over budget or approaching a limit.\n\n## Procedure\n\n1. Use this uploaded `spend-analysis` skill with\n   `aibast_procurement-agent-synthetic-records.md` and\n   `aibast_procurement-agent-rules-and-guardrails.md`. Retrieve and cite both.\n2. Use `available = budget - spent YTD - committed`. Sum all category balances\n   once, including negative values. Never subtract a category deficit again.\n   Reconcile this with total budget minus total spent YTD minus total committed.\n   Category balances are not freely transferable.\n3. Use `(spent YTD + committed) \u002F budget` for utilization and the rules'\n   status thresholds. Preserve existing budget exceptions. Technology is already\n   `At Risk`; Software is `Over Budget`. Keep the snapshot unchanged.\n4. The snapshot has no request-to-commitment mapping. Finance reconciliation\n   must establish whether a request is already included in commitments.\n   Do not infer inclusion from matching amounts or request status.\n   Do not calculate hypothetical revised balances or utilization, or assert\n   incremental budget effects without that mapping. Do not introduce\n   request-specific projections or attribute a category deficit to a request.\n5. Do not invent periods, causal mappings or executed\u002Freversible statuses.\n   Report recorded trends only; do not extrapolate a quarter or forecast.\n6. For amount-based human review of a source-backed request amount, use the rule:\n   Choose the first threshold whose inclusive upper bound covers the request\n   amount. Retain its cap and the `Unlimited` \u002F `CEO + Board` tier.\n   Do not invent dollar-only lower bounds or serial approval chains.\n   The selected approver must review and decide; do not promise approval.\n   Do not invent an approver for unspecified spend.\n   The SLA is a source label, not evidence that a review clock or approval started.\n   It is not a promise of approval.\n\n## Required response contract\n\nUse these headings in order, with exact wording and capitalization. Populate\neach section from the retrieved source; do not replace the tables with prose.\n\n```text\n# Spend Analysis\n## By Category\n## Alerts\n```\n\n- Under `Spend Analysis`, include a portfolio totals table with Total budget,\n  Spent YTD, Committed and Available, preserving the source amounts and labels.\n- Under `By Category`, include all five source category rows in source order:\n  Technology, Software, Office Supplies, Professional Services and Travel.\n  Keep all columns: Category, Budget, Spent YTD, Committed, Available,\n  Utilization, Status and Trend.\n- Under `Alerts`, retain the existing exceptions and their source-backed\n  amounts, including exactly `Software category over budget by $60,000` for\n  this snapshot. Explain the inclusion and transfer limits. For a specified\n  request amount, identify its source-threshold reviewer here; otherwise do not\n  name one. Use the mandatory paragraph below for the complete unresolved\n  human-review set.\n- Before the final footer, include exactly `No purchase order is created.`\n\n## Deterministic pilot evidence\n\n- `Software`\n- `$60,000`\n- `No purchase order is created`\n\n## Safety gate\n\nDo not claim to have changed a system, contacted a person or supplier, made a decision, or completed a transaction. Stop at a reviewable brief or draft.\nRetain the global policy's exact terminal safety footer verbatim.\n\n## Mandatory human-review paragraph\n\nCopy this paragraph verbatim once in every final answer, after all case-specific\ncontent and citations, immediately before the final safety footer. Never shorten,\nsplit, paraphrase or duplicate it. These controls are unresolved in this review,\nnot a serial chain or a denial of recorded historical statuses.\n\nRequired human reviews remain unresolved: Finance for budget validation and reconciliation; procurement for request and supplier review; legal, security, competition, supplier diversity, conflicts of interest, business-owner, delegated-authority and explicit publication review by the corresponding authorized owners.\n\n## Shared final footer\n\nEnd every response with this exact final standalone paragraph, once.\nPut case-specific boundaries and citations before this footer; append nothing\nafter it.\n\nSynthetic procurement evidence; decision support only. No approval, supplier action, purchase order, or spend commitment occurred.\n","\u003C!-- bic:source=blank -->\n# Spend and budget review\n\nUse when a finance director asks which synthetic category is over budget or approaching a limit.\n\n## Procedure\n\n1. Use this uploaded `spend-analysis` skill with\n   `aibast_procurement-agent-synthetic-records.md` and\n   `aibast_procurement-agent-rules-and-guardrails.md`. Retrieve and cite both.\n2. Use `available = budget - spent YTD - committed`. Sum all category balances\n   once, including negative values. Never subtract a category deficit again.\n   Reconcile this with total budget minus total spent YTD minus total committed.\n   Category balances are not freely transferable.\n3. Use `(spent YTD + committed) \u002F budget` for utilization and the rules'\n   status thresholds. Preserve existing budget exceptions. Technology is already\n   `At Risk`; Software is `Over Budget`. Keep the snapshot unchanged.\n4. The snapshot has no request-to-commitment mapping. Finance reconciliation\n   must establish whether a request is already included in commitments.\n   Do not infer inclusion from matching amounts or request status.\n   Do not calculate hypothetical revised balances or utilization, or assert\n   incremental budget effects without that mapping. Do not introduce\n   request-specific projections or attribute a category deficit to a request.\n5. Do not invent periods, causal mappings or executed\u002Freversible statuses.\n   Report recorded trends only; do not extrapolate a quarter or forecast.\n6. For amount-based human review of a source-backed request amount, use the rule:\n   Choose the first threshold whose inclusive upper bound covers the request\n   amount. Retain its cap and the `Unlimited` \u002F `CEO + Board` tier.\n   Do not invent dollar-only lower bounds or serial approval chains.\n   The selected approver must review and decide; do not promise approval.\n   Do not invent an approver for unspecified spend.\n   The SLA is a source label, not evidence that a review clock or approval started.\n   It is not a promise of approval.\n\n## Required response contract\n\nUse these headings in order, with exact wording and capitalization. Populate\neach section from the retrieved source; do not replace the tables with prose.\n\n```text\n# Spend Analysis\n## By Category\n## Alerts\n```\n\n- Under `Spend Analysis`, include a portfolio totals table with Total budget,\n  Spent YTD, Committed and Available, preserving the source amounts and labels.\n- Under `By Category`, include all five source category rows in source order:\n  Technology, Software, Office Supplies, Professional Services and Travel.\n  Keep all columns: Category, Budget, Spent YTD, Committed, Available,\n  Utilization, Status and Trend.\n- Under `Alerts`, retain the existing exceptions and their source-backed\n  amounts, including exactly `Software category over budget by $60,000` for\n  this snapshot. Explain the inclusion and transfer limits. For a specified\n  request amount, identify its source-threshold reviewer here; otherwise do not\n  name one. Use the mandatory paragraph below for the complete unresolved\n  human-review set.\n- Before the final footer, include exactly `No purchase order is created.`\n\n## Deterministic pilot evidence\n\n- `Software`\n- `$60,000`\n- `No purchase order is created`\n\n## Safety gate\n\nDo not claim to have changed a system, contacted a person or supplier, made a decision, or completed a transaction. Stop at a reviewable brief or draft.\nRetain the global policy's exact terminal safety footer verbatim.\n\n## Mandatory human-review paragraph\n\nCopy this paragraph verbatim once in every final answer, after all case-specific\ncontent and citations, immediately before the final safety footer. Never shorten,\nsplit, paraphrase or duplicate it. These controls are unresolved in this review,\nnot a serial chain or a denial of recorded historical statuses.\n\nRequired human reviews remain unresolved: Finance for budget validation and reconciliation; procurement for request and supplier review; legal, security, competition, supplier diversity, conflicts of interest, business-owner, delegated-authority and explicit publication review by the corresponding authorized owners.\n\n## Shared final footer\n\nEnd every response with this exact final standalone paragraph, once.\nPut case-specific boundaries and citations before this footer; append nothing\nafter it.\n\nSynthetic procurement evidence; decision support only. No approval, supplier action, purchase order, or spend commitment occurred.\n",{"name":5,"description":7},"main","d665f66f72c112f5d2956b180f9b534dcb1d94f8","solutions\u002Fprocurement-agent\u002Fmanual\u002Fskills\u002Faibast_spend-analysis_04",9,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-12 14:55:52",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add microsoft\u002Faibast-agents-library --skill spend-analysis",{"tool":54,"command":55},"bunx","bunx skills add microsoft\u002Faibast-agents-library --skill spend-analysis",{"tool":57,"command":58},"pnpm","pnpm dlx skills add microsoft\u002Faibast-agents-library --skill spend-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Fprocurement-agent\u002Fmanual\u002Fskills\u002Faibast_spend-analysis_04\u002FSKILL.md",true,[],[63,84,95,105,116,128],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":34},"01M70JM1PSN44H3XTBBV1P5H2V","get-win-loss-analysis","Add Win\u002FLoss Analysis Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Win\u002FLoss Analysis Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Fwin-loss-analysis\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[25,75,76,77,33,78,79,80,81,82,83,28],"get win loss analysis","win loss analysis","get","studio","copilot studio","copilot","add","deploy","user",{"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":91,"publishedAt":34},"01M70JKGB2V8QZTQ2VZD4CSMJP","get-wealth-insights-generator","Add Wealth Insights Generator Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Wealth Insights Generator Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Fwealth-insights-generator\u002FSKILL.md",[90],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[77,92,93,94,80,82,79,83,28,81,33,78],"insights","generator","get wealth insights generator",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":102,"publishedAt":34},"01M70JK4RG6907D1JA6QAFJNRA","get-warranty-registration","Add Warranty and Registration Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Warranty and Registration Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Fwarranty-registration\u002FSKILL.md",[101],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[103,77,104,81,78,33,28,82,80,79,83],"registration","get warranty registration",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":34},"01M70JJJY46SWJG5J05CVMJ9GV","get-utility-billing-assistance","Add Utility Billing and Assistance Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Utility Billing and Assistance Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Futility-billing-assistance\u002FSKILL.md",[111],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[113,114,115,77,78,82,80,79,83,28,81,33],"get utility billing assistance","billing","utility",{"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":123,"publishedAt":34},"01M70JHVE1PCHBR0A08V8H6ZEE","get-underwriting-support","Add Underwriting Support Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Underwriting Support Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Funderwriting-support\u002FSKILL.md",[122],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[124,125,77,126,81,82,80,79,127,83,28,78,33],"underwriting","get underwriting support","support","support agent",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":34},"01M70JH5PBZQD2RVJ3BPPKS9CQ","get-time-entry-billing","Add Time Entry and Billing Agent to the user's own Copilot Studio. Use when asked to get, add or deploy Time Entry and Billing Agent.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Faibast-agents-library\u002Fblob\u002Fmain\u002Fsolutions\u002Ftime-entry-billing\u002FSKILL.md",[134],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},[136,137,138,77,114,139,80,79,140,83,28,81,78,33,82],"get time entry billing","get time","time","entry","billing agent"]