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, providing extensive natural language phrases users would say and clearly stating both what the skill does and when to use it. Its main weakness is that the capability description is somewhat shallow—it focuses heavily on triggering conditions but doesn't enumerate the specific actions the skill can perform beyond creating/adding roles. The description also uses passive/imperative voice appropriately rather than first/second person.
Suggestions
Add more specific concrete actions beyond creation, such as 'configure role permissions, assign roles to contacts, set up authenticated and anonymous access levels' 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 web pages). 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 site users in Power Pages) and 'when' (with a clear 'Use when' equivalent at the start listing multiple trigger scenarios). | 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. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Power Pages web roles, a distinct niche. Terms like 'web roles', 'Power Pages code site', 'authenticated role', and 'anonymous role' are 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 content could be tightened by removing redundant sections (e.g., the progress tracking table duplicates the workflow overview) and trimming explanatory dialogue examples that pad the token count without adding unique value.
Suggestions
Remove or consolidate the progress tracking table at the end, as it largely duplicates the Phase 1-6 workflow section already defined above.
Trim the example dialogue snippets (e.g., 'I found the following existing web roles...') since Claude can generate appropriate conversational responses without scripted templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured but includes some verbosity that could be trimmed—e.g., the example dialogue snippets, the common web roles list (Claude knows these), and the repeated emphasis on task tracking. The progress tracking table at the end largely duplicates the workflow section. | 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 validation criteria. Everything is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | The six-phase workflow is clearly sequenced with explicit validation in Phase 5 (format checks, UUID validation, uniqueness constraints) and a fix-and-retry feedback loop. 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, deploy-site skill) but the main document is quite long and monolithic. The progress tracking table and important notes section could be separated or the overall content could be more concise to avoid the wall-of-text feel. | 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
66a61c6
- 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.