[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PMQ94EYXMEMBSWSMM59KJN":3,"skill-same:01M6PMQ94EYXMEMBSWSMM59KJN":74},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":67},"01M6PMQ94EYXMEMBSWSMM59KJN","azure-app-rebuild",null,"Implement an explicitly scoped complete application, migration wave, or vertical slice from a reviewed existing-application modernization package. Use for a separately requested rearchitecture or rebuild after functional discovery and target selection, preserving requirements, external contracts, data ownership, and incumbent UI authority. Implement incrementally and verify the full requested scope before reporting completion. Not for initial assessment, isolated runtime upgrades, greenfield design, automatic deployment, or production data migration.","microsoft\u002Ffrontier-agentic-modernization-rvas","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M6PMNDQAJ94CAQWGYJS1FC4S",9,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-modernization\u002Fskills\u002Fazure-app-rebuild\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"azure","azure app rebuild","app","rebuild","ui","reporting","data","assessment","contracts","selection","full","modernization","scope","vertical slice","data migration","functional","for","authority","automatic","design","2026-11-10 10:12:30",false,"---\nname: azure-app-rebuild\ndescription: \"Implement an explicitly scoped complete application, migration wave, or vertical slice from a reviewed existing-application modernization package. Use for a separately requested rearchitecture or rebuild after functional discovery and target selection, preserving requirements, external contracts, data ownership, and incumbent UI authority. Implement incrementally and verify the full requested scope before reporting completion. Not for initial assessment, isolated runtime upgrades, greenfield design, automatic deployment, or production data migration.\"\ndisable-model-invocation: true\n---\n\n# Azure App Rebuild\n\nImplement the customer's explicitly requested application, wave, or slice in\ntheir application repository. A complete-app rebuild is a supported delivery\nscope, not a requirement to rewrite everything in one pass. This is a separate\ndelivery workflow, never an automatic continuation of `azure-app-modernization`.\n\n## 1. Reconcile the delivery contract\n\nRead the current repository instructions and the complete package under\n`docs\u002Fmodernization\u002F`: `assessment.md`, `specification.md`, `strategy-matrix.md`,\n`target-architecture.md`, `infrastructure-plan.md`, `cost-estimate.md`,\n`current-state.drawio`, `target-architecture.drawio`, and `migration-plan.md`.\nInspect the source, tests,\nmanifests, data contracts, deployment configuration, domain records, and relevant\nUI authority. Discover available supporting skills instead of assuming installation.\n\nRequire an explicit delivery scope: **complete application**, **migration wave**,\nor **vertical slice**, with its boundary, acceptance IDs, preserve\u002Fchange\u002Fretire\ndecisions, prerequisites, and expected validation evidence. Use the reviewed\npackage and explicit delivery request directly; do not require another summary\nor handoff document. If scope is missing or ambiguous, obtain a decision before editing;\ndo not assume either an unrestricted rewrite or a single-slice outcome.\nA reviewed package need not carry formal approval unless the customer's\ngovernance requires it. Check any required acceptance record.\n\nFor complete-app scope, account for every required workflow, integration, and\napplicable UI surface in the reviewed specification. Track coverage in existing\ntask\u002Ftest records or the response, linking workflows to acceptance IDs,\nimplementation work, tests\u002Fchecks, and pass\u002Ffail\u002Fblocked evidence.\nResolve gaps in required behavior or acceptance\ncriteria with the decision owner rather than inventing criteria or silently\ndropping workflows. An intentional retirement needs a recorded package decision.\n\nCompare current source with the confirmed baseline and selected target. Identify\nstale evidence, missing artifacts, contradictions, and unresolved feasibility\nblockers. Stop affected implementation and return material architecture changes\nto planning; do not invent a target, acceptance criteria, or approval.\n\nReadiness for static planning is not readiness to execute: establish a repeatable\nbuild\u002Ftest approach, safe fixtures, and required local access for the requested\nscope.\nRecord pre-existing failures separately. Do not execute unknown scripts, restore\ndatabase backups, or use production credentials simply to establish a baseline.\n\n## 2. Implement incrementally within the agreed scope\n\nBreak the agreed scope into testable end-to-end increments and follow the\nreviewed dependency order. For complete-app delivery, continue through the\nincrements inside that scope while prerequisites hold; a working first journey\nis a checkpoint, not completion. Do not require a new scope decision for each\nalready-agreed increment, or stop after one merely because it works.\nFor a wave or slice request, keep later waves and unrelated workflows out of scope.\nMaterial blockers or architecture changes still require the affected work to stop.\n\nUse existing patterns and preserve all behavior and contracts not explicitly\nchanged by the specification. Keep unrelated\ncomponents untouched. Use `codebase-design`, `tdd`, or `diagnosing-bugs` for bounded\nsupport when installed, without granting those skills broader scope.\n\nFor UI work, load `impeccable` when available and use `PRODUCT.md`, `DESIGN.md`,\n`.impeccable\u002Fdesign.json`, and confirmed `SURF-` dispositions as authority. New\nfrontend technology does not authorize redesign. Report missing design evidence\nbefore changing affected surfaces.\n\nFor data\u002Fintegration changes, preserve write ownership, ordering, idempotency,\ncompatibility, coexistence, and rollback\u002Freconciliation boundaries from the plan.\nUse synthetic or sanitized data. Author migration\u002FIaC\u002FCI files only when in the\nagreed scope; generating them does not authorize running them. Use\n`infrastructure-plan.md` to reconcile the app's configuration, identity, and\ndependency needs with the provided infrastructure contract.\n\nDo not use the upstream `implement` skill as an unattended wrapper: its contract\nincludes committing work. Do not commit, publish issues, provision resources,\ndeploy, migrate production data, or change repository\u002Fcloud settings without\nexplicit authorization for that action in this delivery session. Tool permission\nprompts and repository controls remain in force.\n\n## 3. Validate and review\n\nAdd focused tests for changed behavior, including important failure and\ncompatibility paths. Run the smallest relevant existing checks, expanding to\nintegration\u002Fbuild checks as needed. Verify every in-scope acceptance criterion\nwith actual output; a generated test or workflow file is not a passed check.\n\nFor complete-app scope, reconcile workflow coverage against the full reviewed\nspecification, including workflows absent from the implementation diff. Exercise\nthe app's required workflows and integrations with safe fixtures; record\nunavailable checks as blocked. Passing one journey, a build, or an increment's\ntests does not establish whole-app completion.\n\nReview implementation completeness against requirements, wave dependencies, data\nand UI commitments, and directly related documentation. Use the host's code-review\nworkflow or installed `code-review` skill, then resolve findings and rerun affected\nchecks. Run a separate security review after completeness findings are resolved\nor explicitly accepted. If independent review or runtime tooling is unavailable,\nname the missing review\u002Fcheck and its owner; do not claim it passed.\n\n## 4. Report results and stop\n\nReport the package revision, requested delivery scope, completed increments,\nchanged files, acceptance IDs with pass\u002Ffail\u002Fblocked evidence, review findings\nand disposition, pre-existing\nfailures, remaining prerequisites, and rollback\u002Freconciliation readiness.\nDistinguish local validation from deployment or production readiness.\n\nA failed, blocked, or uncovered required criterion means the requested scope is\nincomplete or explicitly partial, not done. For a complete-app request, report\nremaining workflows and blockers even when several increments are finished.\nDo not silently relabel partial delivery as a smaller successful scope.\nStop at the agreed app\u002Fwave\u002Fslice boundary; do not advance to an unrequested wave\nor expand the application. Leave commits and operational execution to\nseparately authorized actions.\n","# Azure App Rebuild\n\nImplement the customer's explicitly requested application, wave, or slice in\ntheir application repository. A complete-app rebuild is a supported delivery\nscope, not a requirement to rewrite everything in one pass. This is a separate\ndelivery workflow, never an automatic continuation of `azure-app-modernization`.\n\n## 1. Reconcile the delivery contract\n\nRead the current repository instructions and the complete package under\n`docs\u002Fmodernization\u002F`: `assessment.md`, `specification.md`, `strategy-matrix.md`,\n`target-architecture.md`, `infrastructure-plan.md`, `cost-estimate.md`,\n`current-state.drawio`, `target-architecture.drawio`, and `migration-plan.md`.\nInspect the source, tests,\nmanifests, data contracts, deployment configuration, domain records, and relevant\nUI authority. Discover available supporting skills instead of assuming installation.\n\nRequire an explicit delivery scope: **complete application**, **migration wave**,\nor **vertical slice**, with its boundary, acceptance IDs, preserve\u002Fchange\u002Fretire\ndecisions, prerequisites, and expected validation evidence. Use the reviewed\npackage and explicit delivery request directly; do not require another summary\nor handoff document. If scope is missing or ambiguous, obtain a decision before editing;\ndo not assume either an unrestricted rewrite or a single-slice outcome.\nA reviewed package need not carry formal approval unless the customer's\ngovernance requires it. Check any required acceptance record.\n\nFor complete-app scope, account for every required workflow, integration, and\napplicable UI surface in the reviewed specification. Track coverage in existing\ntask\u002Ftest records or the response, linking workflows to acceptance IDs,\nimplementation work, tests\u002Fchecks, and pass\u002Ffail\u002Fblocked evidence.\nResolve gaps in required behavior or acceptance\ncriteria with the decision owner rather than inventing criteria or silently\ndropping workflows. An intentional retirement needs a recorded package decision.\n\nCompare current source with the confirmed baseline and selected target. Identify\nstale evidence, missing artifacts, contradictions, and unresolved feasibility\nblockers. Stop affected implementation and return material architecture changes\nto planning; do not invent a target, acceptance criteria, or approval.\n\nReadiness for static planning is not readiness to execute: establish a repeatable\nbuild\u002Ftest approach, safe fixtures, and required local access for the requested\nscope.\nRecord pre-existing failures separately. Do not execute unknown scripts, restore\ndatabase backups, or use production credentials simply to establish a baseline.\n\n## 2. Implement incrementally within the agreed scope\n\nBreak the agreed scope into testable end-to-end increments and follow the\nreviewed dependency order. For complete-app delivery, continue through the\nincrements inside that scope while prerequisites hold; a working first journey\nis a checkpoint, not completion. Do not require a new scope decision for each\nalready-agreed increment, or stop after one merely because it works.\nFor a wave or slice request, keep later waves and unrelated workflows out of scope.\nMaterial blockers or architecture changes still require the affected work to stop.\n\nUse existing patterns and preserve all behavior and contracts not explicitly\nchanged by the specification. Keep unrelated\ncomponents untouched. Use `codebase-design`, `tdd`, or `diagnosing-bugs` for bounded\nsupport when installed, without granting those skills broader scope.\n\nFor UI work, load `impeccable` when available and use `PRODUCT.md`, `DESIGN.md`,\n`.impeccable\u002Fdesign.json`, and confirmed `SURF-` dispositions as authority. New\nfrontend technology does not authorize redesign. Report missing design evidence\nbefore changing affected surfaces.\n\nFor data\u002Fintegration changes, preserve write ownership, ordering, idempotency,\ncompatibility, coexistence, and rollback\u002Freconciliation boundaries from the plan.\nUse synthetic or sanitized data. Author migration\u002FIaC\u002FCI files only when in the\nagreed scope; generating them does not authorize running them. Use\n`infrastructure-plan.md` to reconcile the app's configuration, identity, and\ndependency needs with the provided infrastructure contract.\n\nDo not use the upstream `implement` skill as an unattended wrapper: its contract\nincludes committing work. Do not commit, publish issues, provision resources,\ndeploy, migrate production data, or change repository\u002Fcloud settings without\nexplicit authorization for that action in this delivery session. Tool permission\nprompts and repository controls remain in force.\n\n## 3. Validate and review\n\nAdd focused tests for changed behavior, including important failure and\ncompatibility paths. Run the smallest relevant existing checks, expanding to\nintegration\u002Fbuild checks as needed. Verify every in-scope acceptance criterion\nwith actual output; a generated test or workflow file is not a passed check.\n\nFor complete-app scope, reconcile workflow coverage against the full reviewed\nspecification, including workflows absent from the implementation diff. Exercise\nthe app's required workflows and integrations with safe fixtures; record\nunavailable checks as blocked. Passing one journey, a build, or an increment's\ntests does not establish whole-app completion.\n\nReview implementation completeness against requirements, wave dependencies, data\nand UI commitments, and directly related documentation. Use the host's code-review\nworkflow or installed `code-review` skill, then resolve findings and rerun affected\nchecks. Run a separate security review after completeness findings are resolved\nor explicitly accepted. If independent review or runtime tooling is unavailable,\nname the missing review\u002Fcheck and its owner; do not claim it passed.\n\n## 4. Report results and stop\n\nReport the package revision, requested delivery scope, completed increments,\nchanged files, acceptance IDs with pass\u002Ffail\u002Fblocked evidence, review findings\nand disposition, pre-existing\nfailures, remaining prerequisites, and rollback\u002Freconciliation readiness.\nDistinguish local validation from deployment or production readiness.\n\nA failed, blocked, or uncovered required criterion means the requested scope is\nincomplete or explicitly partial, not done. For a complete-app request, report\nremaining workflows and blockers even when several increments are finished.\nDo not silently relabel partial delivery as a smaller successful scope.\nStop at the agreed app\u002Fwave\u002Fslice boundary; do not advance to an unrequested wave\nor expand the application. Leave commits and operational execution to\nseparately authorized actions.\n",{"name":5,"description":7,"disable-model-invocation":44},true,"main","b16645dc5c0b91a24d3a7667b877c3ec9939a261","plugins\u002Fagentic-modernization\u002Fskills\u002Fazure-app-rebuild",5,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas","https:\u002F\u002Fmicrosoft.github.io\u002Ffrontier-agentic-modernization-rvas\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-05 22:04:00",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":44},[57,60,63],{"tool":58,"command":59},"npx","npx skills add microsoft\u002Ffrontier-agentic-modernization-rvas --skill azure-app-rebuild",{"tool":61,"command":62},"bunx","bunx skills add microsoft\u002Ffrontier-agentic-modernization-rvas --skill azure-app-rebuild",{"tool":64,"command":65},"pnpm","pnpm dlx skills add microsoft\u002Ffrontier-agentic-modernization-rvas --skill azure-app-rebuild","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-modernization\u002Fskills\u002Fazure-app-rebuild\u002FSKILL.md",[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fevals.json","REFERENCE","参考文档",8445,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-modernization\u002Fskills\u002Fazure-app-rebuild\u002Fevals\u002Fevals.json",[75,110,135,167,185,209],{"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":89,"publishedAt":39},"01M6PMQDZ5ZEGBYHNYSPWJSQCA","cloud-architecture-diagram","Create, edit, or troubleshoot Azure-first architecture diagrams as editable draw.io files, with AWS and multicloud topology support and identity, API, and CI\u002FCD flow diagrams. Use for architecture visualization, network boundaries, interaction flows, or missing diagram icons. Not for deploying infrastructure, live cloud discovery, security certification, or unrelated charts.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-modernization\u002Fskills\u002Fcloud-architecture-diagram\u002FSKILL.md",[81,86],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000023","Skill与智能体开发",[90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109],"architecture","cloud architecture diagram","diagram","architecture diagram","cloud","cloud architecture","MCP","create","visualization","ci","api","Charts","access","work","diagrams","files","local","io","interaction","flows",{"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":122,"publishedAt":39},"01M6PMQ0P1G7DXJF0S3WR30PTM","azure-app-modernization","Architecture-first Azure modernization for existing applications supplied as source code, documentation, UI assets, or database artifacts. Use for recovering functional requirements, incumbent product and visual-design authority, user-interface surfaces, current architecture and integrations, interviewing stakeholders, suggesting proven Azure reference architectures for the user to choose, blueprinting infrastructure-as-code in the user's choice of Terraform or Bicep, estimating target and migration costs, and planning a migration before implementation, including on-premises, cross-cloud, and already-Azure estates. Produces an assessment, specification, editable diagrams, target architecture, infrastructure plan, cost estimate, migration plan, and conditional product\u002Fdesign context for existing UIs. Ends with a reconciled planning-package handoff; isolated SDK\u002FSKU upgrades, deployment, troubleshooting, greenfield design, and standalone AI-feature design use other workflows.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002Fplugins\u002Fagentic-modernization\u002Fskills\u002Fazure-app-modernization\u002FSKILL.md",[116,117],{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[19,30,123,21,124,38,125,90,26,126,127,128,129,104,130,131,132,133,134,36],"app modernization","azure app modernization","workflows","code","database","choose","choice","specification","user-interface","interface","infrastructure-as","standalone",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":139,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":149,"publishedAt":39},"01M6PMPQN41C48HBWRCBM20BXZ","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fimpeccable\u002FSKILL.md",[142,145,148],{"categoryNo":143,"categoryName":144,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":146,"categoryName":147,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[137,150,38,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,132,166],"frontend","review","components","init","tasks","design systems","simplify","improve","clarify","distill","only","overdrive","quieter","typeset","ux copy","states","effects",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":179,"publishedAt":39},"01M6PMPMGNHNAEQE7XA853Z2QP","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[173,176],{"categoryNo":174,"categoryName":175,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":177,"categoryName":178,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000036","内容创作者",[180,181,35,182,183,184],"writing","writing for agents","documents","editing","use",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":192,"publishedAt":39},"01M6PMPE5KY9T25DR0N778V9S6","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[191],{"categoryNo":87,"categoryName":88,"taxonomyType":84,"taxonomyTypeDesc":85},[193,194,195,196,197,97,198,199,200,157,201,184,202,203,204,205,35,206,207,208],"skill creator","creator","performance","run evals","variance analysis","run","benchmark","analysis","edit","evals","optimize","existing skill","From Scratch","accuracy","Existing","scratch",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":218,"publishedAt":39},"01M6PMP855VGYPT5ZKRF1TRGST","rvap-brand","Applies the RVAP (Real Value Acceleration Program) brand identity — colors, fonts, logo, and layout patterns — consistently to any GitHub Pages website. Use this skill whenever someone asks to brand, rebrand, apply RVAP\u002FRVAS visual identity, make a site look RVAP, match the brand kit, or transform a GitHub Pages site's look and feel to match RVAP. Also trigger when the user shares an HTML\u002FCSS\u002FMkDocs site and says it should look consistent with other RVAP\u002FRVAS materials, even if they don't explicitly say \"brand\".","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ffrontier-agentic-modernization-rvas\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Frvap-brand\u002FSKILL.md",[215,216,217],{"categoryNo":143,"categoryName":144,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":146,"categoryName":147,"taxonomyType":84,"taxonomyTypeDesc":85},{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[219,220,221,222,223,224,225,184,226,227,228,229,230,231,232,233,234,235,236,237],"rvap brand","brand","css","identity","website","logo","github pages","html","mkdocs","patterns","layout","pages","trigger","transform","make","fonts","kit","value","brand kit"]