[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699SPQB24115VPGSQZ80CSA":3,"skill-same:01M699SPQB24115VPGSQZ80CSA":145},{"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":31,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":68,"ownerHtmlUrl":69,"ownerBlogUrl":70,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M699SPQB24115VPGSQZ80CSA","author-webpage-content",null,"Generates and fills the localized HTML body of an existing webpage in a PAC CLI-downloaded non-SPA Power Pages site from a resolved page-content specification. Use whenever a caller has resolved the existing webpage metadata and asks to compose, replace, append, or modify the exact localized `.webpage.copy.html` file with Design Studio-compatible sections, columns, flex containers, text, images, buttons, videos, iframes, Generative AI Search components, basic forms, lists, multistep forms, or spacers. This skill owns only HTML generation and the supplied target file; the coordinator's webpage reference workflow owns discovery, records, metadata, languages, routes, templates, navigation, and companion-file creation. Do not use for React, Angular, Vue, or Astro SPA sites.","microsoft\u002Fpower-platform-skills","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699JVYJFB75D9JM70BN4H0Q",1149,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"author","author webpage content","content","Bash","generative","studio","coordinator","false","creation","spa","specification","images","only","power","design","angular","search","power pages","react","components","workflow","generative ai","containers","cli","2026-11-10 10:12:30",false,"---\nname: author-webpage-content\ndescription: >-\n  Generates and fills the localized HTML body of an existing webpage in a PAC\n  CLI-downloaded non-SPA Power Pages site from a resolved page-content\n  specification. Use whenever a caller has resolved the existing webpage metadata\n  and asks to compose, replace, append, or modify\n  the exact localized `.webpage.copy.html` file with Design Studio-compatible\n  sections, columns, flex containers, text, images, buttons, videos, iframes,\n  Generative AI Search components, basic forms, lists, multistep forms, or\n  spacers. This skill owns\n  only HTML generation and the supplied target file; the coordinator's webpage\n  reference workflow owns discovery, records, metadata, languages, routes, templates,\n  navigation, and companion-file creation. Do not use for React, Angular, Vue,\n  or Astro SPA sites.\nuser-invocable: false\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash, TaskCreate, TaskUpdate, TaskList\nmodel: sonnet\n---\n\n> **Plugin check**: Run `node \"${PLUGIN_ROOT}\u002Fscripts\u002Fcheck-version.js\"` — if it outputs a message, show it to the user before proceeding.\n\n# Author Webpage Content\n\nGenerate and fill one supplied localized Design Studio-compatible webpage body.\n\n**Initial request:** $ARGUMENTS\n\n## Preview disclosure\n\nRead `${PLUGIN_ROOT}\u002Freferences\u002Fnon-spa-preview.md` and apply its **Entry and handoff\nprotocol**. Unless the initial request contains the explicit marker from an actual covered-skill\nhandoff, present the **Customization notice** before project inspection or task creation.\n\n## Authoritative references\n\nAlways read and follow:\n\n- `${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fwebpage-content-composition.md`\n- `${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-component-authoring.md`\n\nRead only the page-element references used by the requested composition:\n\n- `design-studio-section-layouts.md`\n- `design-studio-flex-container-component.md`\n- `design-studio-text-component.md`\n- `design-studio-image-component.md`\n- `design-studio-button-component.md`\n- `design-studio-video-component.md`\n- `design-studio-iframe-component.md`\n- `design-studio-generative-ai-search-component.md`\n- `design-studio-basic-form-component.md`\n- `design-studio-list-component.md`\n- `design-studio-multistep-form-component.md`\n- `design-studio-spacer-component.md`\n\nAll page-element references are under:\n\n```text\n${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002F\n```\n\nThese references own serialized section and component markup, editing\nboundaries, preservation, accessibility, and verification rules. Do not invent\ncompeting markup contracts.\n\nFor an add or edit Generative AI Search component request, target only\n`{% codecomponent name:Pages.SearchSummary ... %}`. Do not substitute\n`{% include 'Search' %}`, a Search web template, Search content snippets, the\nSearch Results page record, site markers, or search indexing\u002Fsettings.\n\nFor an add or edit Basic Form, List, or Multistep form request, target only\n`{% entityform name:'...' %}`, `{% include 'entity_list' key:'...' ... %}`, or\n`{% webform name:'...' %}` respectively, pointing at a record already present in\nthe downloaded site. This skill does not create the backing basic form, list,\nmultistep form, Dataverse table form\u002Fview, or table permissions — see each\ncomponent reference's **Scope** section. If the named (or implied) record is\nnot found in the downloaded site, do not assist with constructing it: do not\nquery Dataverse (API, SDK, Web API, or CLI) and do not ask the user for IDs,\nGUIDs, or permissions to assemble it locally. When asking the user how to\nproceed, the only valid options are (a) embed an existing record, or (b) stop.\n\n## Ownership boundary\n\nThis skill receives and edits exactly one existing localized file per\ninvocation:\n\n```text\nweb-pages\u002F\u003Cpage-directory>\u002Fcontent-pages\u002F\u003CPage>.\u003Clocale>.webpage.copy.html\n```\n\nIt may compose multiple sections and page elements in that file as one coherent\noperation.\n\nThis skill does not create or modify:\n\n- root or localized webpage YAML;\n- page routes, parents, page-template assignments, or navigation;\n- page-template or web-template records;\n- content-snippet records;\n- web files or their metadata;\n- basic form, list, multistep form (advanced form\u002Fstep), Dataverse table\n  form\u002Fview, or table-permission records;\n- localized summary, custom CSS, or custom JavaScript companion files;\n- another locale unless the request supplies a separately resolved composition\n  for that locale.\n\nThe calling orchestrator must create or confirm the file and resolve its webpage and locale\nidentity before invoking this skill. `edit-site` uses\n`${PLUGIN_ROOT}\u002Fskills\u002Fedit-site\u002Freferences\u002Fwebpage-authoring.md`\nfor that metadata workflow.\nThis skill does not search for or select a webpage record.\n\nIf the target file or any required content, URL, snippet name, or other rendered\nvalue is unresolved, stop before writing and return the exact missing input.\nDo not manufacture a placeholder or expand this skill into metadata or\ndependency authoring.\n\n## Autonomy policy\n\nComplete routine composition without asking the user to approve mechanical\ndetails. Infer safe formatting, escaping, indentation, and accessibility\ndetails from the resolved specification, authoritative references, existing\npage markup, and site-local conventions.\n\nChoose independently when safe:\n\n- exact indentation and line endings;\n- the documented section serialization matching a named layout;\n- component markup matching a resolved element type and source;\n- safe link attributes and output encoding;\n- preservation of empty columns required by the selected layout;\n- the smallest coherent edit for a modification.\n\nStop before writing when a material choice remains unresolved, including:\n\n- multiple target files, target sections, or components;\n- an unresolved section geometry or ambiguous component-to-column mapping, not merely\n  a layout name missing from the recipe examples;\n- missing Flex Container child mapping, visitor-facing text, image source, destination,\n  alternative text, video title, iframe title, or search behavior\u002Ftext required by the\n  selected component;\n- an unresolved web-file URL, snippet name, or page destination;\n- a requested basic form, list, or multistep form record not found in the\n  downloaded site — never query Dataverse or assist with constructing it\n  locally, and never present \"create a new one\" as a selectable option in a\n  clarification question;\n- a replacement that does not state what existing content must be preserved;\n- custom HTML whose safety or intended rendering boundary cannot be established.\n\n## Expected resolved handoff\n\nPrefer a structured specification containing:\n\n- the exact existing target file and its already-resolved locale;\n- the verified Bootstrap major and any approved `designContext`; require version evidence for\n  new sections, especially when the target page is blank;\n- operation mode: `create`, `replace`, `append`, or `modify`;\n- ordered sections;\n- each section's supported layout and ordered elements by column;\n- optional explicit `columns[].span` values and intended wrapping\u002Funused space; otherwise\n  resolve CSS-driven widths with the styling owner instead of guessing a preset;\n- resolved content, URLs, snippet names, and accessibility values;\n- explicit preservation requirements for an existing page.\n\nThe specification may be Markdown, YAML, JSON, or an unambiguous natural\nlanguage plan. Normalize it internally according to the composition reference;\ndo not require the user to rewrite a complete plan merely to match an example\nformat.\n\nAn approved new-site handoff requires custom composition using supported native sections,\ncolumns and elements, not just text\u002Fimage substitutions. Follow its resolved composition and\n`designContext`, not the creation template's arrangement. Retain\u002Fplace required existing components through the\nresolved-source rules in **Whole-page composition**, without inventing new native element types.\nRemove unneeded starter sections or component placements when the approved handoff accounts for\ntheir removal and dependencies. Do not retain them solely because they came with the template,\nhide them with CSS, or delete their backing records.\nPreserve required content\u002Fcapabilities and native serialization as described in **Whole-page\ncomposition**; an unrelated existing-site `append` or `modify` remains a narrow edit.\n\n## Workflow\n\n1. Validate the supplied target file and resolved composition.\n2. Read the complete target HTML and only the required page-element references.\n3. Generate or modify the complete section\u002Fcolumn\u002Felement tree in document\n   order.\n4. Fill the target file once as one coherent page-content change.\n5. Verify structure, preservation, rendered values, safety, and the final diff.\n\nDo not upload, deploy, or modify Dataverse directly.\n\n## Phase 1: Validate the supplied target\n\nRequire one exact existing file path under:\n\n```text\nweb-pages\u002F\u003Cpage-directory>\u002Fcontent-pages\u002F\u003CPage>.\u003Clocale>.webpage.copy.html\n```\n\nThe caller owns proving that the path belongs to the intended localized webpage.\nReject a missing file, directory path, root-level copy file, wildcard, or\nmultiple targets. Do not create directories, companion files, or webpage\nmetadata.\n\n## Phase 2: Normalize and validate the plan\n\nFollow **Resolved composition contract** in the composition reference. Preserve\nthe supplied section order, column assignment, element order, content,\ndestinations, sources, and accessibility requirements.\n\nRequire final rendered URLs, snippet names, Liquid expressions, text, and\naccessibility values. The caller owns creating and resolving their underlying\nrecords. Do not continue with symbolic asset names or design-tool placeholders.\n\n## Phase 3: Load only required markup contracts\n\nRead the section-layout reference whenever the operation creates a section or\nchanges a section's column structure. Then read one component-specific reference\nfor each element type present in the normalized plan.\nUse its Bootstrap 5 examples only with verified Bootstrap 5 evidence. Preserve inspected\nBootstrap 3\u002Fnative and RTL patterns for existing sites; return missing evidence to the caller\nrather than assuming the creation default or changing the framework.\n\nDo not invoke one skill per page element. This skill is the single writer for\nthe target HTML and assembles all approved element markup in memory before\nediting the file.\n\n## Phase 4: Compose or modify\n\nFor `create` or `replace`, follow **Whole-page composition** in the composition\nreference. Build sections in plan order, columns in layout order, and elements\nin their specified order within each column.\n\nFor `append` or `modify`, follow **Existing-page operations**. Resolve exact\nstructural boundaries before changing the file, preserve unrelated markup, and\ndo not reserialize the entire page for a narrow edit.\n\nUse the section-layout reference's recipes as defaults, not exhaustive geometry constraints.\nBroader safe local layouts may proceed with **Studio editing compatibility unverified**\ndisclosed in the existing review and final report. Other page-element serialization contracts\nremain unchanged; do not invent Studio controls, preview components, or an additional gate.\nReplace every sample\nvalue and marker with resolved plan values. Do not leave placeholder text,\nplaceholder URLs, `\u003C!-- COMPONENT_HTML -->`, TODOs, or unexplained empty\ncomponents.\n\n## Phase 5: Verify and report\n\nRun the complete verification checklist from the composition reference and each\npage-element reference used. Review the final diff and confirm that only the\nselected localized HTML file changed.\n\nReport:\n\n- target file and supplied locale;\n- created, replaced, appended, or modified sections;\n- element types and final rendered references used;\n- material preservation decisions.\n\nState that the change is local and was not uploaded or deployed.\n\n### Record skill usage\n\n> Reference: `${PLUGIN_ROOT}\u002Freferences\u002Fskill-tracking-reference.md`\n\nFollow the skill tracking instructions in the reference using\n`--skillName \"AuthorWebpageContent\"`.\n","> **Plugin check**: Run `node \"${PLUGIN_ROOT}\u002Fscripts\u002Fcheck-version.js\"` — if it outputs a message, show it to the user before proceeding.\n\n# Author Webpage Content\n\nGenerate and fill one supplied localized Design Studio-compatible webpage body.\n\n**Initial request:** $ARGUMENTS\n\n## Preview disclosure\n\nRead `${PLUGIN_ROOT}\u002Freferences\u002Fnon-spa-preview.md` and apply its **Entry and handoff\nprotocol**. Unless the initial request contains the explicit marker from an actual covered-skill\nhandoff, present the **Customization notice** before project inspection or task creation.\n\n## Authoritative references\n\nAlways read and follow:\n\n- `${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fwebpage-content-composition.md`\n- `${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-component-authoring.md`\n\nRead only the page-element references used by the requested composition:\n\n- `design-studio-section-layouts.md`\n- `design-studio-flex-container-component.md`\n- `design-studio-text-component.md`\n- `design-studio-image-component.md`\n- `design-studio-button-component.md`\n- `design-studio-video-component.md`\n- `design-studio-iframe-component.md`\n- `design-studio-generative-ai-search-component.md`\n- `design-studio-basic-form-component.md`\n- `design-studio-list-component.md`\n- `design-studio-multistep-form-component.md`\n- `design-studio-spacer-component.md`\n\nAll page-element references are under:\n\n```text\n${PLUGIN_ROOT}\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002F\n```\n\nThese references own serialized section and component markup, editing\nboundaries, preservation, accessibility, and verification rules. Do not invent\ncompeting markup contracts.\n\nFor an add or edit Generative AI Search component request, target only\n`{% codecomponent name:Pages.SearchSummary ... %}`. Do not substitute\n`{% include 'Search' %}`, a Search web template, Search content snippets, the\nSearch Results page record, site markers, or search indexing\u002Fsettings.\n\nFor an add or edit Basic Form, List, or Multistep form request, target only\n`{% entityform name:'...' %}`, `{% include 'entity_list' key:'...' ... %}`, or\n`{% webform name:'...' %}` respectively, pointing at a record already present in\nthe downloaded site. This skill does not create the backing basic form, list,\nmultistep form, Dataverse table form\u002Fview, or table permissions — see each\ncomponent reference's **Scope** section. If the named (or implied) record is\nnot found in the downloaded site, do not assist with constructing it: do not\nquery Dataverse (API, SDK, Web API, or CLI) and do not ask the user for IDs,\nGUIDs, or permissions to assemble it locally. When asking the user how to\nproceed, the only valid options are (a) embed an existing record, or (b) stop.\n\n## Ownership boundary\n\nThis skill receives and edits exactly one existing localized file per\ninvocation:\n\n```text\nweb-pages\u002F\u003Cpage-directory>\u002Fcontent-pages\u002F\u003CPage>.\u003Clocale>.webpage.copy.html\n```\n\nIt may compose multiple sections and page elements in that file as one coherent\noperation.\n\nThis skill does not create or modify:\n\n- root or localized webpage YAML;\n- page routes, parents, page-template assignments, or navigation;\n- page-template or web-template records;\n- content-snippet records;\n- web files or their metadata;\n- basic form, list, multistep form (advanced form\u002Fstep), Dataverse table\n  form\u002Fview, or table-permission records;\n- localized summary, custom CSS, or custom JavaScript companion files;\n- another locale unless the request supplies a separately resolved composition\n  for that locale.\n\nThe calling orchestrator must create or confirm the file and resolve its webpage and locale\nidentity before invoking this skill. `edit-site` uses\n`${PLUGIN_ROOT}\u002Fskills\u002Fedit-site\u002Freferences\u002Fwebpage-authoring.md`\nfor that metadata workflow.\nThis skill does not search for or select a webpage record.\n\nIf the target file or any required content, URL, snippet name, or other rendered\nvalue is unresolved, stop before writing and return the exact missing input.\nDo not manufacture a placeholder or expand this skill into metadata or\ndependency authoring.\n\n## Autonomy policy\n\nComplete routine composition without asking the user to approve mechanical\ndetails. Infer safe formatting, escaping, indentation, and accessibility\ndetails from the resolved specification, authoritative references, existing\npage markup, and site-local conventions.\n\nChoose independently when safe:\n\n- exact indentation and line endings;\n- the documented section serialization matching a named layout;\n- component markup matching a resolved element type and source;\n- safe link attributes and output encoding;\n- preservation of empty columns required by the selected layout;\n- the smallest coherent edit for a modification.\n\nStop before writing when a material choice remains unresolved, including:\n\n- multiple target files, target sections, or components;\n- an unresolved section geometry or ambiguous component-to-column mapping, not merely\n  a layout name missing from the recipe examples;\n- missing Flex Container child mapping, visitor-facing text, image source, destination,\n  alternative text, video title, iframe title, or search behavior\u002Ftext required by the\n  selected component;\n- an unresolved web-file URL, snippet name, or page destination;\n- a requested basic form, list, or multistep form record not found in the\n  downloaded site — never query Dataverse or assist with constructing it\n  locally, and never present \"create a new one\" as a selectable option in a\n  clarification question;\n- a replacement that does not state what existing content must be preserved;\n- custom HTML whose safety or intended rendering boundary cannot be established.\n\n## Expected resolved handoff\n\nPrefer a structured specification containing:\n\n- the exact existing target file and its already-resolved locale;\n- the verified Bootstrap major and any approved `designContext`; require version evidence for\n  new sections, especially when the target page is blank;\n- operation mode: `create`, `replace`, `append`, or `modify`;\n- ordered sections;\n- each section's supported layout and ordered elements by column;\n- optional explicit `columns[].span` values and intended wrapping\u002Funused space; otherwise\n  resolve CSS-driven widths with the styling owner instead of guessing a preset;\n- resolved content, URLs, snippet names, and accessibility values;\n- explicit preservation requirements for an existing page.\n\nThe specification may be Markdown, YAML, JSON, or an unambiguous natural\nlanguage plan. Normalize it internally according to the composition reference;\ndo not require the user to rewrite a complete plan merely to match an example\nformat.\n\nAn approved new-site handoff requires custom composition using supported native sections,\ncolumns and elements, not just text\u002Fimage substitutions. Follow its resolved composition and\n`designContext`, not the creation template's arrangement. Retain\u002Fplace required existing components through the\nresolved-source rules in **Whole-page composition**, without inventing new native element types.\nRemove unneeded starter sections or component placements when the approved handoff accounts for\ntheir removal and dependencies. Do not retain them solely because they came with the template,\nhide them with CSS, or delete their backing records.\nPreserve required content\u002Fcapabilities and native serialization as described in **Whole-page\ncomposition**; an unrelated existing-site `append` or `modify` remains a narrow edit.\n\n## Workflow\n\n1. Validate the supplied target file and resolved composition.\n2. Read the complete target HTML and only the required page-element references.\n3. Generate or modify the complete section\u002Fcolumn\u002Felement tree in document\n   order.\n4. Fill the target file once as one coherent page-content change.\n5. Verify structure, preservation, rendered values, safety, and the final diff.\n\nDo not upload, deploy, or modify Dataverse directly.\n\n## Phase 1: Validate the supplied target\n\nRequire one exact existing file path under:\n\n```text\nweb-pages\u002F\u003Cpage-directory>\u002Fcontent-pages\u002F\u003CPage>.\u003Clocale>.webpage.copy.html\n```\n\nThe caller owns proving that the path belongs to the intended localized webpage.\nReject a missing file, directory path, root-level copy file, wildcard, or\nmultiple targets. Do not create directories, companion files, or webpage\nmetadata.\n\n## Phase 2: Normalize and validate the plan\n\nFollow **Resolved composition contract** in the composition reference. Preserve\nthe supplied section order, column assignment, element order, content,\ndestinations, sources, and accessibility requirements.\n\nRequire final rendered URLs, snippet names, Liquid expressions, text, and\naccessibility values. The caller owns creating and resolving their underlying\nrecords. Do not continue with symbolic asset names or design-tool placeholders.\n\n## Phase 3: Load only required markup contracts\n\nRead the section-layout reference whenever the operation creates a section or\nchanges a section's column structure. Then read one component-specific reference\nfor each element type present in the normalized plan.\nUse its Bootstrap 5 examples only with verified Bootstrap 5 evidence. Preserve inspected\nBootstrap 3\u002Fnative and RTL patterns for existing sites; return missing evidence to the caller\nrather than assuming the creation default or changing the framework.\n\nDo not invoke one skill per page element. This skill is the single writer for\nthe target HTML and assembles all approved element markup in memory before\nediting the file.\n\n## Phase 4: Compose or modify\n\nFor `create` or `replace`, follow **Whole-page composition** in the composition\nreference. Build sections in plan order, columns in layout order, and elements\nin their specified order within each column.\n\nFor `append` or `modify`, follow **Existing-page operations**. Resolve exact\nstructural boundaries before changing the file, preserve unrelated markup, and\ndo not reserialize the entire page for a narrow edit.\n\nUse the section-layout reference's recipes as defaults, not exhaustive geometry constraints.\nBroader safe local layouts may proceed with **Studio editing compatibility unverified**\ndisclosed in the existing review and final report. Other page-element serialization contracts\nremain unchanged; do not invent Studio controls, preview components, or an additional gate.\nReplace every sample\nvalue and marker with resolved plan values. Do not leave placeholder text,\nplaceholder URLs, `\u003C!-- COMPONENT_HTML -->`, TODOs, or unexplained empty\ncomponents.\n\n## Phase 5: Verify and report\n\nRun the complete verification checklist from the composition reference and each\npage-element reference used. Review the final diff and confirm that only the\nselected localized HTML file changed.\n\nReport:\n\n- target file and supplied locale;\n- created, replaced, appended, or modified sections;\n- element types and final rendered references used;\n- material preservation decisions.\n\nState that the change is local and was not uploaded or deployed.\n\n### Record skill usage\n\n> Reference: `${PLUGIN_ROOT}\u002Freferences\u002Fskill-tracking-reference.md`\n\nFollow the skill tracking instructions in the reference using\n`--skillName \"AuthorWebpageContent\"`.\n",{"name":5,"model":61,"description":7,"allowed-tools":62,"user-invocable":57},"sonnet","Read, Write, Edit, Grep, Glob, Bash, TaskCreate, TaskUpdate, TaskList","main","0a55a88fa2855404029d1e5450faf92878baf763","plugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content",232,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills","https:\u002F\u002Fmicrosoft.github.io\u002Fpower-platform-skills\u002F","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 21:46:39",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add microsoft\u002Fpower-platform-skills --skill author-webpage-content",{"tool":79,"command":80},"bunx","bunx skills add microsoft\u002Fpower-platform-skills --skill author-webpage-content",{"tool":82,"command":83},"pnpm","pnpm dlx skills add microsoft\u002Fpower-platform-skills --skill author-webpage-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002FSKILL.md",true,[87,93,97,101,105,109,113,117,121,125,129,133,137,141],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fdesign-studio-basic-form-component.md","REFERENCE","参考文档",4620,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-basic-form-component.md",{"path":94,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fdesign-studio-button-component.md",10409,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-button-component.md",{"path":98,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fdesign-studio-component-authoring.md",4439,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-component-authoring.md",{"path":102,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fdesign-studio-flex-container-component.md",4305,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-flex-container-component.md",{"path":106,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fdesign-studio-generative-ai-search-component.md",5519,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-generative-ai-search-component.md",{"path":110,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fdesign-studio-iframe-component.md",8172,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-iframe-component.md",{"path":114,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fdesign-studio-image-component.md",10969,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-image-component.md",{"path":118,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fdesign-studio-list-component.md",5753,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-list-component.md",{"path":122,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fdesign-studio-multistep-form-component.md",5181,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-multistep-form-component.md",{"path":126,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fdesign-studio-section-layouts.md",12160,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-section-layouts.md",{"path":130,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fdesign-studio-spacer-component.md",8129,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-spacer-component.md",{"path":134,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fdesign-studio-text-component.md",9049,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-text-component.md",{"path":138,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fdesign-studio-video-component.md",11343,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fdesign-studio-video-component.md",{"path":142,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Fwebpage-content-composition.md",13951,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fauthor-webpage-content\u002Freferences\u002Fwebpage-content-composition.md",[146,154,175,196,214,228],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":153},"01M78JN2BFRRV1J54Q6WKZQ08D","compare-site-configurations","Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fpower-pages\u002Fskills\u002Fcompare-site-configurations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":56},"01M699WVHX0XN59EPBTTPEKYPG","setup","Use when Process Intelligence needs building, explicit cloud\u002Faccount\u002Fenvironment configuration, sign-in, connection diagnostics, or recovery from an authentication error.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fsetup\u002FSKILL.md",[],[156,161,162,163,164,165,166,167,168,169,35,170,171,172,173,174],"configuration","diagnostics","error","environment","cloud","when","connection","authentication","use","recovery","process","sign","read","intelligence",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":56},"01M699WSR9EX55YY1WD9J22FEG","report-issue","Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Freport-issue\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000034","行政与办公人员",[185,186,187,188,169,166,189,190,171,191,174,192,193,194,195],"issue","report","report issue","bug-report","operation","draft","bug","summary","user","for","support",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":202,"publishedAt":56},"01M699WR26YQ9Q21KE6MJF5B2G","investigate-process","Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Finvestigate-process\u002FSKILL.md",[],[203,171,204,205,169,206,207,166,208,209,210,173,211,212,213],"investigate","investigate process","question","process mining","business","across","perspectives","mining","pattern","investigation","analytical",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":56},"01M699WP9SDG5ZR12P8VYNXKTN","derive-metric","Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fderive-metric\u002FSKILL.md",[],[221,222,223,224,225,226,169,166,227,173],"metric","derive metric","missing","formula","custom","reuse","saved",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":232,"categories":233,"keywords":234,"publishedAt":56},"01M699WMG5R8P6SMTDAS1TKF9E","compare-cohorts","Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Fpower-platform-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fprocess-intelligence\u002Fskills\u002Fcompare-cohorts\u002FSKILL.md",[],[235,236,169,166,237,171,173],"compare","compare cohorts","results"]