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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/power-pages/skills/create-webroles/SKILL.md

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-sequenced, actionable workflow with strong validation checkpoints, but it suffers from redundant caller-suppress explanations and a broken relationship between the SKILL.md body and its bundled scripts.

Suggestions

Define caller-suppress mode once in Phase 0 and have Core Principles, Phase 1, and Phase 6 reference it instead of re-explaining the behavior each time.

Reference and use the bundled scripts/create-web-role.js from Phase 4 instead of the manual UUID-script-plus-handwritten-YAML path, so Claude uses the all-in-one executable helper that is already provided.

Reconcile referenced paths with the bundle: either add the referenced generate-uuid.js and references/skill-tracking-reference.md to the skill bundle, or point the body at paths that actually exist alongside SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly instructional rather than padded with concepts Claude knows, but the caller-suppress mode is explained in four places (Core Principles, Phase 0, Phase 1, Phase 6) and Important Notes reiterates already-covered decision points, so it could be meaningfully tightened.	3 / 5
Actionability	Concrete commands, exact YAML format, kebab-case filename rules, and verbatim AskUserQuestion options make it mostly executable; the gap is that the bundled create-web-role.js helper (UUID + write in one call) is never referenced.	4 / 5
Workflow Clarity	Six phases are clearly sequenced with an explicit Phase 5 validation step, a fix-and-retry feedback loop, uniqueness-constraint checks, and a task-tracking checklist; validation is present so the batch-operation cap does not apply.	5 / 5
Progressive Disclosure	Internal phase structure is clear and references are signaled, but the body references plugin-root paths (generate-uuid.js, skill-tracking-reference.md) absent from this bundle while the two bundled scripts (create-web-role.js, validate-webroles.js) are orphaned and never referenced, leaving navigation gaps.	3 / 5
	Total	15 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does and when to use it with concrete trigger phrases. The main weakness is single-term noun coverage on the trigger side.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Creates and configures web roles') plus trigger verbs (create, add, set up, manage), but coverage stays within a single narrow domain rather than being comprehensive.	4 / 5
Completeness	Explicitly answers both 'what' ('Creates and configures web roles for a Power Pages code site') and 'when' via a concrete 'Use when the user wants to create, add, set up, or manage web roles' trigger clause.	5 / 5
Trigger Term Quality	Good action-synonym coverage ('create, add, set up, or manage') that users would naturally say, but the noun side is a single term ('web roles') with no synonyms like 'user roles' or 'site permissions'.	4 / 5
Distinctiveness Conflict Risk	The 'Power Pages code site' + 'web roles' niche is specific with distinct triggers and minimal overlap risk with other skills; written in third person.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/power-pages/skills/create-webroles/SKILL.md
Commit: 4c284ab

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.