[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CYDPT0JCGV4Q6FSWKSAG4N":3,"skill-same:01M7CYDPT0JCGV4Q6FSWKSAG4N":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7CYDPT0JCGV4Q6FSWKSAG4N","pr-review",null,"Reviews a pull request from outside the core team on an open-source Umbraco package: runs the `reviewer` agent, then checks what's unsafe to build locally, security, contribution rules, docs, and whether the diff does what it claims. Drafts the review for approval; never posts or merges on its own. Use for community PRs. For your own task's diff, use `reviewer` through `feature-build` or `quick-fix`.","mattbrailsford\u002Fumbraco-devkit","mattbrailsford","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F527305?v=4","01M7CY974D4XX1P90YSXQC1T39","Matt Brailsford","01M7CY9751PSRA3EHBH03G936J",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pr-review\ndescription: >-\n  Reviews a pull request from outside the core team on an open-source Umbraco package: runs\n  the `reviewer` agent, then checks what's unsafe to build locally, security, contribution\n  rules, docs, and whether the diff does what it claims. Drafts the review for approval;\n  never posts or merges on its own. Use for community PRs. For your own task's diff, use\n  `reviewer` through `feature-build` or `quick-fix`.\nuser-invocable: true\nargument-hint: \u003CPR number or URL>\n---\n\n# Review a contribution\n\nFor a pull request filed against an Umbraco package's public repo by someone outside the core\nmaintainer team. Most packages in this space are open source, so this is a steady trickle, not\nan edge case. The diff didn't come from your own `builder`\u002Fplan-folder pipeline, so three\nthings are different from a normal in-house review: you don't know the author's intent beyond\nwhat the PR says, you haven't vetted the code that's about to run on your machine, and the\ntrust bar for \"does this quietly break something\" needs to sit higher by default.\n\nThis skill doesn't replace `reviewer` — it wraps it. `reviewer` already carries the\nUmbraco-aware checklist that matters most here: public API impact, a renamed manifest `alias`,\nmulti-version\u002Fprovider parity, layering, and the security skills. This skill adds the handful\nof checks that only exist *because* the diff came from outside.\n\n## Scope\n\n- IN: a PR on a package's public repo, opened by someone who isn't a core maintainer. Fetching\n  it, reviewing it, drafting a review comment.\n- OUT: a `feature-build` task's own diff (dispatch `reviewer` directly — that's what\n  `feature-build`\u002F`quick-fix` already do); merging, approving, or requesting changes without\n  you confirming the drafted comment first; fixing the contribution yourself (if it's close\n  but needs a small push, say so in the comment and let the contributor or a maintainer decide\n  who pushes it); clicking through it on the demo site yourself (`pr-demo`).\n\n## Argument\n\n`$ARGUMENTS` is a PR number or URL. If empty, ask which PR.\n\n## Workflow\n\n1. **Fetch the PR, don't run anything yet.**\n   `gh pr view \u003Cnumber> --json title,body,author,baseRefName,headRefName,additions,deletions,files`\n   and `gh pr diff \u003Cnumber>`. Read the diff before touching your working tree.\n\n2. **Scan for anything that would execute on your machine before you build or test.** A\n   malicious or careless PR can put code where CI, a build, or a package restore will run it\n   automatically. Flag any of these as `Critical` and read them by hand before continuing:\n   a changed `.github\u002Fworkflows\u002F*`, a build script (`.ps1`, `.sh`, `csproj`\u002F`build.cake`\n   targets), `NuGet.config` (a changed package source can redirect where packages come from),\n   a new or changed `npm`\u002F`package.json` `scripts` entry (`postinstall` runs unattended), or\n   any new binary\u002Fexecutable file. None of these block the review outright, but don't run\n   `dotnet build`\u002F`npm install` against the PR branch until you've read what they'd execute.\n\n3. **Check out the branch.** `git status` first (per this project's own safety rules — don't\n   discard uncommitted work). Then `gh pr checkout \u003Cnumber>`.\n\n4. **Treat the PR's own description as its task.** There's no `PLAN.md` task text for an\n   outside contribution — the PR title\u002Fbody (and the issue it links, if any) is the closest\n   equivalent. Read it before judging the diff: `reviewer` needs a task to judge scope against\n   in its own step 8, and \"what the PR says it does\" is that task here.\n\n5. **Dispatch `reviewer`** (Agent tool, `subagent_type: reviewer`), passing the PR's stated\n   intent as the task. With the PR branch already checked out, its own step 1 (`git diff`\n   against the base branch) finds the same diff you just scanned. Let it run its full\n   workflow — build, test, docs\u002Fsibling comparison, consumer-impact, entry-point trace, ghost\n   code, multi-version\u002Fprovider parity, verdict.\n\n6. **Add the checks `reviewer` doesn't know to make for outside code:**\n   - **The security skill runs unconditionally.** `reviewer` only reaches for\n     `umbraco-security` when the diff visibly touches auth, user input, the Management API,\n     or secrets. For a PR from outside the team, load `umbraco-security` yourself regardless\n     of what the diff looks like it touches, and whether or not `reviewer` ran. A security\n     pass from memory doesn't replace it: the skill holds the Umbraco-specific checks you\n     won't think of unprompted. An external diff is a new trust boundary, and \"doesn't look\n     security-relevant\" is exactly the blind spot a deliberately disguised change would aim\n     for.\n   - **Contribution hygiene.** If the repo has a `CONTRIBUTING.md`, check the PR follows it:\n     target branch, commit\u002FPR conventions, sign-off trailer (DCO\u002FCLA) if the repo requires\n     one, tests included for new behavior.\n   - **Docs flag, no assumed location.** If the diff adds or changes a public feature, flag\n     that it probably needs a docs update — but don't assume where. Only Umbraco HQ-owned\n     packages keep docs in the UmbracoDocs repo; everyone else keeps docs in their own repo, a\n     separate site, or nowhere formal. Say \"this looks like it needs a docs update, check\n     wherever this project keeps its docs\" and leave it there.\n   - **Intent match.** Compare the diff against the PR's own stated purpose (and linked issue,\n     if any). Flag anything beyond it — an unrelated reformat, a drive-by refactor of a file\n     the stated fix never needed to touch — as a `Suggestion` if small and harmless, `Important`\n     if it changes behavior outside the stated scope. This isn't `reviewer`'s own scope check\n     (step 8 in its workflow), which judges against a plan-folder task; here there is no plan,\n     so the PR's own description is the only scope boundary there is.\n\n7. **Check every finding before it reaches the contributor.** A wrong finding on an outside\n   PR costs the contributor a round trip and makes the next finding easier to ignore. Do\n   this on every PR, however small, and don't check the findings yourself instead: you\n   collected them, so you're the wrong one to doubt them. Dispatch one fresh general-purpose\n   subagent (Agent tool) on the checked-out branch with every finding from steps 5 and 6.\n   Tell it to try to disprove each one by reading the code around the cited file:line and\n   beyond the diff: a guard in a base class, attribute or caller, a handler elsewhere that\n   already covers it, an API that doesn't behave the way the finding assumes. It returns\n   each finding as confirmed, refuted, or unsure, with the evidence. Drop refuted ones, and\n   turn unsure ones into a question for the contributor instead of a demand. List what was\n   dropped, and why, for the user under the draft, not in it.\n\n8. **Draft the review, don't post it yet.** Combine `reviewer`'s verdict and the findings\n   that survived step 7 into one comment. Before the first finding, give one line with the\n   verdict and the count per tier, such as `Changes needed: 1 Important, 2 Suggestions`;\n   with nothing to fix, say so in those words. Then the findings, grouped the same way\n   `reviewer` tiers them (Critical \u002F Important \u002F Suggestion \u002F Pre-existing). Pre-existing\n   ones are for the maintainer, so say plainly the contributor doesn't need to fix them.\n   Write it following `plain-writing` — a contributor who doesn't know this codebase needs to be able to act on\n   it. Say what's blocking and what's a nice-to-have; don't bury a `Critical` finding in a\n   wall of Suggestions.\n\n9. **Show the draft and ask before posting.** A PR comment on a public repo is visible to the\n   contributor and anyone else watching the repo — confirm with the user first, every time.\n   Once confirmed, post with `gh pr review \u003Cnumber> --comment --body-file \u003Cpath>` for a plain\n   comment, or `--request-changes`\u002F`--approve` instead of `--comment` only if the user\n   explicitly wants the review state set, not just a comment left. Never pass `--approve`\n   without the user having said so. Same sanity rules as `git-workflow`: never `--no-verify`,\n   never force-push, re-check the diff for secrets before anything is staged locally.\n\n## Hand off\n\nOne line: the PR, the verdict (`reviewer`'s tier plus anything step 6 added), and whether the\ncomment was posted or is still waiting on confirmation.\n","# Review a contribution\n\nFor a pull request filed against an Umbraco package's public repo by someone outside the core\nmaintainer team. Most packages in this space are open source, so this is a steady trickle, not\nan edge case. The diff didn't come from your own `builder`\u002Fplan-folder pipeline, so three\nthings are different from a normal in-house review: you don't know the author's intent beyond\nwhat the PR says, you haven't vetted the code that's about to run on your machine, and the\ntrust bar for \"does this quietly break something\" needs to sit higher by default.\n\nThis skill doesn't replace `reviewer` — it wraps it. `reviewer` already carries the\nUmbraco-aware checklist that matters most here: public API impact, a renamed manifest `alias`,\nmulti-version\u002Fprovider parity, layering, and the security skills. This skill adds the handful\nof checks that only exist *because* the diff came from outside.\n\n## Scope\n\n- IN: a PR on a package's public repo, opened by someone who isn't a core maintainer. Fetching\n  it, reviewing it, drafting a review comment.\n- OUT: a `feature-build` task's own diff (dispatch `reviewer` directly — that's what\n  `feature-build`\u002F`quick-fix` already do); merging, approving, or requesting changes without\n  you confirming the drafted comment first; fixing the contribution yourself (if it's close\n  but needs a small push, say so in the comment and let the contributor or a maintainer decide\n  who pushes it); clicking through it on the demo site yourself (`pr-demo`).\n\n## Argument\n\n`$ARGUMENTS` is a PR number or URL. If empty, ask which PR.\n\n## Workflow\n\n1. **Fetch the PR, don't run anything yet.**\n   `gh pr view \u003Cnumber> --json title,body,author,baseRefName,headRefName,additions,deletions,files`\n   and `gh pr diff \u003Cnumber>`. Read the diff before touching your working tree.\n\n2. **Scan for anything that would execute on your machine before you build or test.** A\n   malicious or careless PR can put code where CI, a build, or a package restore will run it\n   automatically. Flag any of these as `Critical` and read them by hand before continuing:\n   a changed `.github\u002Fworkflows\u002F*`, a build script (`.ps1`, `.sh`, `csproj`\u002F`build.cake`\n   targets), `NuGet.config` (a changed package source can redirect where packages come from),\n   a new or changed `npm`\u002F`package.json` `scripts` entry (`postinstall` runs unattended), or\n   any new binary\u002Fexecutable file. None of these block the review outright, but don't run\n   `dotnet build`\u002F`npm install` against the PR branch until you've read what they'd execute.\n\n3. **Check out the branch.** `git status` first (per this project's own safety rules — don't\n   discard uncommitted work). Then `gh pr checkout \u003Cnumber>`.\n\n4. **Treat the PR's own description as its task.** There's no `PLAN.md` task text for an\n   outside contribution — the PR title\u002Fbody (and the issue it links, if any) is the closest\n   equivalent. Read it before judging the diff: `reviewer` needs a task to judge scope against\n   in its own step 8, and \"what the PR says it does\" is that task here.\n\n5. **Dispatch `reviewer`** (Agent tool, `subagent_type: reviewer`), passing the PR's stated\n   intent as the task. With the PR branch already checked out, its own step 1 (`git diff`\n   against the base branch) finds the same diff you just scanned. Let it run its full\n   workflow — build, test, docs\u002Fsibling comparison, consumer-impact, entry-point trace, ghost\n   code, multi-version\u002Fprovider parity, verdict.\n\n6. **Add the checks `reviewer` doesn't know to make for outside code:**\n   - **The security skill runs unconditionally.** `reviewer` only reaches for\n     `umbraco-security` when the diff visibly touches auth, user input, the Management API,\n     or secrets. For a PR from outside the team, load `umbraco-security` yourself regardless\n     of what the diff looks like it touches, and whether or not `reviewer` ran. A security\n     pass from memory doesn't replace it: the skill holds the Umbraco-specific checks you\n     won't think of unprompted. An external diff is a new trust boundary, and \"doesn't look\n     security-relevant\" is exactly the blind spot a deliberately disguised change would aim\n     for.\n   - **Contribution hygiene.** If the repo has a `CONTRIBUTING.md`, check the PR follows it:\n     target branch, commit\u002FPR conventions, sign-off trailer (DCO\u002FCLA) if the repo requires\n     one, tests included for new behavior.\n   - **Docs flag, no assumed location.** If the diff adds or changes a public feature, flag\n     that it probably needs a docs update — but don't assume where. Only Umbraco HQ-owned\n     packages keep docs in the UmbracoDocs repo; everyone else keeps docs in their own repo, a\n     separate site, or nowhere formal. Say \"this looks like it needs a docs update, check\n     wherever this project keeps its docs\" and leave it there.\n   - **Intent match.** Compare the diff against the PR's own stated purpose (and linked issue,\n     if any). Flag anything beyond it — an unrelated reformat, a drive-by refactor of a file\n     the stated fix never needed to touch — as a `Suggestion` if small and harmless, `Important`\n     if it changes behavior outside the stated scope. This isn't `reviewer`'s own scope check\n     (step 8 in its workflow), which judges against a plan-folder task; here there is no plan,\n     so the PR's own description is the only scope boundary there is.\n\n7. **Check every finding before it reaches the contributor.** A wrong finding on an outside\n   PR costs the contributor a round trip and makes the next finding easier to ignore. Do\n   this on every PR, however small, and don't check the findings yourself instead: you\n   collected them, so you're the wrong one to doubt them. Dispatch one fresh general-purpose\n   subagent (Agent tool) on the checked-out branch with every finding from steps 5 and 6.\n   Tell it to try to disprove each one by reading the code around the cited file:line and\n   beyond the diff: a guard in a base class, attribute or caller, a handler elsewhere that\n   already covers it, an API that doesn't behave the way the finding assumes. It returns\n   each finding as confirmed, refuted, or unsure, with the evidence. Drop refuted ones, and\n   turn unsure ones into a question for the contributor instead of a demand. List what was\n   dropped, and why, for the user under the draft, not in it.\n\n8. **Draft the review, don't post it yet.** Combine `reviewer`'s verdict and the findings\n   that survived step 7 into one comment. Before the first finding, give one line with the\n   verdict and the count per tier, such as `Changes needed: 1 Important, 2 Suggestions`;\n   with nothing to fix, say so in those words. Then the findings, grouped the same way\n   `reviewer` tiers them (Critical \u002F Important \u002F Suggestion \u002F Pre-existing). Pre-existing\n   ones are for the maintainer, so say plainly the contributor doesn't need to fix them.\n   Write it following `plain-writing` — a contributor who doesn't know this codebase needs to be able to act on\n   it. Say what's blocking and what's a nice-to-have; don't bury a `Critical` finding in a\n   wall of Suggestions.\n\n9. **Show the draft and ask before posting.** A PR comment on a public repo is visible to the\n   contributor and anyone else watching the repo — confirm with the user first, every time.\n   Once confirmed, post with `gh pr review \u003Cnumber> --comment --body-file \u003Cpath>` for a plain\n   comment, or `--request-changes`\u002F`--approve` instead of `--comment` only if the user\n   explicitly wants the review state set, not just a comment left. Never pass `--approve`\n   without the user having said so. Same sanity rules as `git-workflow`: never `--no-verify`,\n   never force-push, re-check the diff for secrets before anything is staged locally.\n\n## Hand off\n\nOne line: the PR, the verdict (`reviewer`'s tier plus anything step 6 added), and whether the\ncomment was posted or is still waiting on confirmation.\n",{"name":5,"description":7,"argument-hint":24,"user-invocable":25},"\u003CPR number or URL>",true,"main","a2f9c28bc56802b4e6db01e03972e497b30ad001","plugins\u002Fumbraco-devkit\u002Fskills\u002Fpr-review",1,"https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit","https:\u002F\u002Fgithub.com\u002Fmattbrailsford","https:\u002F\u002Fmattbrailsford.dev","AI Staff Engineer @umbraco ","2026-11-12 18:33:53",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add mattbrailsford\u002Fumbraco-devkit --skill pr-review",{"tool":41,"command":42},"bunx","bunx skills add mattbrailsford\u002Fumbraco-devkit --skill pr-review",{"tool":44,"command":45},"pnpm","pnpm dlx skills add mattbrailsford\u002Fumbraco-devkit --skill pr-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CYGRPVNP8H9YNHGMZ6CP3C","user-stories","Writes, splits and refines user stories with Given\u002FWhen\u002FThen acceptance criteria in STORIES.md, feeding bdd-specs. Use when turning a feature request or a vague ask into a testable backlog entry.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fuser-stories\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CYGJB26N83DXKMDEKY2X48","umbraco-security","What Umbraco provides for keeping a package secure, on the server and in the backoffice: Management API authorization and policies, settings that hold secrets, endpoints outside the Management API, sanitizeHTML and escapeHTML, DOMPurify rules for custom elements, and umbHttpClient instead of handling tokens in the browser. Use when writing or reviewing a Management API controller, a secret setting, a custom endpoint, a backoffice template that uses unsafeHTML, or frontend code that calls an API.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fumbraco-security\u002FSKILL.md",[],[],{"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":69,"publishedAt":19},"01M7CYGBEZ2Q4AXDDNADWW4Q9H","umbraco-performance","Keeping a package fast on the sites that install it: the published cache over the services layer, tree traversal, caching lookups and clearing them, data type config and converter cache levels, output cache eviction, light hot paths, and backoffice screens that don't over-fetch. Use when writing, changing or reviewing code that runs per request, per save, per indexed item or at startup (property value converters, notification handlers, indexing), code that loops over every content item (a full rebuild, an import, a sync), or a list or search screen. Not for a site's own templates.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fumbraco-performance\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CYG59CZN1K2KERB0SSDGSY","umbraco-package-conventions","Backend conventions for an Umbraco package: async naming, internal by default, Attempt-based results for routine failures, public-API backwards compatibility, and where extension methods live. Use when naming a method, choosing visibility, shaping a service's result, changing a public signature (including adding a dependency to a public class's constructor), or organizing extension methods. For extension mechanisms, see `umbraco-extensibility`.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fumbraco-package-conventions\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CYG0J10QH8J2GS825WTTET","umbraco-marketplace","Gets a finished package listed on the Umbraco Marketplace: the NuGet tag, the dependency Marketplace reads version support from, the v14+ compatibility gotcha, and umbraco-marketplace.json. Use when a package is ready to publish, or when reviewing its packaging.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fumbraco-marketplace\u002FSKILL.md",[],[],{"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":90,"publishedAt":19},"01M7CYFT7MSYW4GRDSQRDPG020","umbraco-extensibility","Umbraco's extension mechanisms (Composers, collection builders, notification handlers, attribute discovery) and a catalogue of backend CMS extension points: property value converters, Management API endpoints, content finders, health checks, search indexing, package migrations, background jobs, and more. Use when making a feature extensible or choosing which extension point fits. Not for property editor UI, dashboards, sections or trees, which the official Backoffice Skills plugin covers.","https:\u002F\u002Fgithub.com\u002Fmattbrailsford\u002Fumbraco-devkit\u002Fblob\u002Fmain\u002Fplugins\u002Fumbraco-devkit\u002Fskills\u002Fumbraco-extensibility\u002FSKILL.md",[],[]]