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.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill create-webroles78
Quality
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/power-pages/skills/create-webroles/SKILL.mdQuality
Discovery
72%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 distinctiveness, providing numerous natural phrases users would say and clearly targeting Power Pages web roles. However, it inverts the typical structure by focusing heavily on 'when to use' while neglecting 'what it does' - the actual capabilities and actions the skill performs are barely described beyond a vague mention of access and permissions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures web roles including authenticated and anonymous roles, assigns permissions, and manages role hierarchies'
Restructure to lead with capabilities before trigger phrases: 'Creates web roles for Power Pages sites, configures access permissions, and manages authenticated/anonymous role settings. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'web roles control access and permissions for site users' which provides some context, but lacks specific concrete actions like 'create', 'configure', 'assign permissions', or 'manage role hierarchies'. It focuses more on trigger phrases than capabilities. | 2 / 3 |
Completeness | The 'when' is very well covered with explicit trigger phrases, but the 'what' is weak - it only vaguely states that web roles 'control access and permissions' without explaining what specific actions the skill performs (e.g., creating role records, configuring permissions, setting up role hierarchies). | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like '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'. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific domain focus on 'Power Pages code site' and 'web roles'. The combination of platform-specific terminology and role-related triggers makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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, actionable skill with clear workflow phases and proper validation checkpoints. The main strengths are its explicit verification steps, concrete commands, and user decision points. However, it could be more concise by reducing repetitive explanations and trusting Claude to understand context without restating deployment instructions multiple times.
Suggestions
Remove redundant explanations of what web roles are and what deployment does - Claude understands these concepts
Consolidate the deployment reminder text that appears in multiple places (Phase 1, Phase 6) into a single reference
Consider moving the 'Common web roles' list and YAML format examples to a separate reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what web roles are, repeating deployment instructions multiple times). The phase structure adds overhead that could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific glob patterns, exact PowerShell commands, YAML file format with examples, and clear script paths for UUID generation. Copy-paste ready commands are provided. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with 6 clearly sequenced phases, explicit validation in Phase 5 (checking UUID format, uniqueness constraints, file existence), and clear decision points requiring user confirmation before proceeding. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one file. The skill references external files (skill-tracking-reference.md, deploy-site skill) appropriately, but the main content could benefit from splitting detailed YAML examples or common role templates into separate reference files. | 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 | |
- 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.