create-webroles
This skill should be used when the user asks to "create web roles", "add web roles", "set up web roles", "add roles", "create roles for my site", "manage web roles", "add authenticated role", "add anonymous role", or wants to create web roles for their Power Pages code site. Web roles control access and permissions for site users.
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 description excels at trigger term coverage and completeness, with a clear 'when to use' clause and many natural user phrasings. Its main weakness is that the specificity of capabilities is somewhat shallow—it mostly repeats variations of 'create/add roles' without detailing what the skill actually does beyond creation (e.g., configuring permissions, setting up role hierarchies). The description also uses passive/imperative voice appropriately and targets a clear niche.
Suggestions
Add more specific concrete actions beyond creation, such as 'assigns entity permissions to roles', 'configures authenticated vs anonymous access levels', or 'links web roles to page access rules' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions creating/adding/managing web roles and notes they 'control access and permissions for site users,' but it doesn't list specific concrete actions beyond creation (e.g., assigning permissions, configuring role hierarchies, linking to entity permissions). The actions are somewhat repetitive variations of 'create/add roles.' | 2 / 3 |
Completeness | The description explicitly answers both 'what' (creates web roles that control access and permissions for Power Pages site users) and 'when' (with a detailed 'Use when' clause listing multiple trigger phrases). The 'when' guidance is very explicit. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create web roles', 'add web roles', 'set up web roles', 'add roles', 'create roles for my site', 'manage web roles', 'add authenticated role', 'add anonymous role', and 'Power Pages' are all phrases users would naturally say. Good variety of phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to 'web roles' within 'Power Pages code site,' which is a very specific niche. The combination of 'web roles' and 'Power Pages' makes it highly unlikely to conflict with other skills. | 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-structured, highly actionable skill with a clear multi-phase workflow and proper validation checkpoints. Its main weakness is verbosity—the progress tracking table duplicates the workflow overview, and some sections (like quoted user messages and the common roles list) could be more concise. Overall it's a solid skill that would guide Claude effectively through web role creation.
Suggestions
Consolidate the progress tracking table into the existing workflow section rather than repeating phase descriptions at the end, or move it to a reference file.
Trim the quoted user-facing message examples—Claude can generate appropriate messages without verbatim scripts for each interaction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured but includes some verbosity that could be trimmed—e.g., the example YAML and role suggestions are repeated/explained at length, the progress tracking table at the end largely duplicates the workflow section, and some phrasing like quoted user-facing messages adds bulk. However, it mostly avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable commands (PowerShell for directory creation, Node script for UUID generation), exact YAML file formats with field specifications, specific naming conventions (kebab-case), and clear constraint rules. Everything is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The 6-phase workflow is clearly sequenced 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 marked, and each phase has defined goals and outputs. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (skill-tracking-reference.md, generate-uuid.js, check-version.js) and links to the deploy skill. However, the content is quite long as a single monolithic file—the progress tracking table, common role suggestions, and detailed phase instructions could potentially be split into references. The structure within the file is good with clear headers, but it's borderline for inline length. | 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
1132a35
- 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.