create-webroles
Creates and configures web roles for a Power Pages code site. Web roles control access and permissions for site users, including authenticated and anonymous roles. Use when the user wants to create, add, set up, or manage web roles for their site.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its domain (Power Pages web roles), explains what it does, and includes an explicit 'Use when' clause with natural trigger terms. The main area for improvement is listing more specific concrete actions beyond 'creates and configures' to better differentiate the full range of capabilities.
Suggestions
Add more specific concrete actions such as 'assign roles to users, configure role-based page access rules, set up table permissions' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (web roles for Power Pages) and some actions (creates, configures, control access and permissions), but doesn't list multiple specific concrete actions beyond create/configure. It mentions 'authenticated and anonymous roles' which adds some specificity, but overall it's not as comprehensive as a score of 3. | 2 / 3 |
Completeness | Clearly answers both 'what' (creates and configures web roles for Power Pages, controls access and permissions) and 'when' with an explicit 'Use when' clause specifying trigger scenarios (create, add, set up, or manage web roles). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'web roles', 'Power Pages', 'code site', 'access', 'permissions', 'authenticated', 'anonymous', 'create', 'add', 'set up', 'manage'. These cover natural variations of how a user would phrase requests about web role management. | 3 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — web roles for Power Pages code sites — which is unlikely to conflict with other skills. The combination of 'Power Pages' and 'web roles' creates a distinct trigger profile. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted workflow skill with excellent actionability and clear multi-step sequencing including proper validation checkpoints and error recovery. The main weakness is moderate verbosity—repeated constraint explanations, example dialogue templates, and inline task tracking tables add length without proportional value. The progressive disclosure is adequate but the skill is on the long side for a single file.
Suggestions
Consolidate the uniqueness constraint explanation (anonymoususersrole/authenticatedusersrole) into a single reference point rather than repeating it across Phases 2, 3, 4, and 5.
Move the progress tracking task table to a reference file or reduce it to a single line referencing a standard pattern, since the phase list already serves as the workflow outline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes some verbosity—example dialogue templates, repeated explanations of constraints (uniqueness flags mentioned in Phases 2, 3, 4, and 5), and the full task tracking table at the end. Some sections could be tightened, but most content is relevant and not explaining things Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable guidance: exact YAML file format, specific bash commands for UUID generation, clear file naming conventions (kebab-case), specific directory paths, and precise validation criteria. The instructions are copy-paste ready and leave no ambiguity about what to produce. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 6 phases with explicit validation in Phase 5 (checking UUID format, boolean validity, uniqueness constraints) and a feedback loop ('if any file fails validation, fix the issue before proceeding'). Decision points requiring user input are clearly identified, and the Phase 1 branching logic for missing directories is well-defined. | 3 / 3 |
Progressive Disclosure | The skill references external files (skill-tracking-reference.md, generate-uuid.js, check-version.js) appropriately, but the main SKILL.md itself is quite long and monolithic. The detailed phase instructions, example dialogues, and task tracking table could potentially be split into reference files. However, for a workflow-driven skill, keeping phases inline is reasonable. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
48e49c4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.