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.
71
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 well-crafted skill description that clearly identifies the domain (Power Pages web roles), lists concrete actions, and includes an explicit 'Use when' clause with multiple natural trigger terms. It is concise, uses third-person voice correctly, and is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists specific concrete actions: 'Creates and configures web roles', 'control access and permissions', and mentions specific role types like 'authenticated and anonymous roles'. It clearly names the domain (Power Pages code site) and the specific entity being managed (web roles). | 3 / 3 |
Completeness | Clearly answers both 'what' (creates and configures web roles for Power Pages, controls access and permissions) and 'when' with an explicit trigger clause: 'Use when the user wants to create, add, set up, or manage web roles for their site.' | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'web roles', 'Power Pages', 'create', 'add', 'set up', 'manage', 'permissions', 'authenticated', 'anonymous'. Good coverage of action verbs and domain-specific terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: 'web roles' for 'Power Pages code site' is a very specific domain. The combination of Power Pages + web roles + permissions creates distinct triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 strong actionability and clear multi-step sequencing including proper validation checkpoints. The main weaknesses are moderate verbosity from repeated constraint explanations and inline dialogue templates, and the monolithic structure that could benefit from splitting some reference content into separate files. Overall, it provides Claude with clear, executable guidance for creating Power Pages web roles.
Suggestions
Consolidate the uniqueness constraint explanation (anonymoususersrole/authenticatedusersrole) into a single reference point rather than repeating it across Phases 2, 3, 4, and 5.
Consider moving the progress tracking task table and example dialogue templates into a separate reference file to reduce the main skill's token footprint.
| 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 little ambiguity. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced across 6 phases with explicit validation in Phase 5 (format checks, UUID validation, 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 progress tracking table provides additional structure. | 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 separate reference files. However, for a workflow-oriented skill, having everything inline is somewhat justified. | 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
b4c46e9
- 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.