Tessl • The management layer for AI agent skills

SkillPublic

create-webroles

Creates and configures web roles for a Power Pages SPA 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. Also supports PAC-downloaded non-SPA sites with nested or directly opened metadata roots.

Quality

84%

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

Quality

Content

81%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 highly actionable, well-sequenced multi-phase workflow with strong validation gates and a correct one-level-deep reference split for the non-SPA variant. The main cost is token efficiency: the caller-suppress contract and the trailing 'Important Notes' section repeat content already stated in the phases.

Suggestions

State the caller-suppress contract once in Phase 0 and have Phases 1 and 6 reference the flag in a single line (e.g. 'skip the deploy ask per Phase 0') instead of restating the full rules at each site.

Drop or compress the 'Important Notes' section: the Key Decision Points list duplicates the three gates, and the Progress Tracking task table restates each phase's Goal/Output lines verbatim — a one-line TaskCreate instruction per phase would suffice.

Tighten the intro: the sentence after the H1 ('Web roles define the permissions and access levels...') repeats the frontmatter description and adds little for the executing model.

Dimension	Reasoning	Score
Conciseness	The core workflow is dense and information-bearing, but the caller-suppress contract is explained in full in four places (Core Principles, Phase 0, Phase 1 step 2, Phase 6 step 3) and the trailing 'Important Notes' Progress Tracking table and Key Decision Points largely restate the phase goals and gates already given inline. This is noticeably redundant but not padded with concept explanation.	3 / 5
Actionability	Guidance is fully executable throughout: exact commands (`node "${PLUGIN_ROOT}/scripts/generate-uuid.js"`), an exact 4-field YAML template, kebab-case filename rules with examples, exact AskUserQuestion option strings, and concrete paths for every referenced script and file.	5 / 5
Workflow Clarity	Six phases are clearly sequenced, each with Goal/Actions/Output, an explicit validation phase (Phase 5) with a fix-and-retry feedback loop, uniqueness checks across existing plus new roles, and gates that define trigger, rationale, and cancel semantics. This matches the top anchor: clear sequence with explicit validation and error-recovery loops.	5 / 5
Progressive Disclosure	The non-SPA variant workflow is properly offloaded to a real, clearly-signaled, one-level-deep reference (references/non-spa-site-workflow.md), and the bundle scripts (create-web-role.js, validate-webroles.js) are referenced from that workflow as deterministic writers. However, the ~310-line main file carries notable internal duplication (caller-suppress rules and the trailing notes section), leaving minor organization gaps that keep it below a 5.	4 / 5
	Total	17 / 20 Passed

Description

82%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 description: it clearly states what the skill does and gives an explicit, synonym-rich 'Use when' trigger clause in a distinctive Power Pages niche. The only weakness is modest action specificity — 'creates and configures' is the extent of the concrete action inventory.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Power Pages SPA site" web roles) and 1-2 concrete actions ("Creates and configures web roles"), matching the domain-plus-couple-actions anchor. It does not list several distinct specific actions the way the score-4/5 anchors require.	3 / 5
Completeness	It explicitly answers what ("Creates and configures web roles... Web roles control access and permissions for site users, including authenticated and anonymous roles") and when ("Use when the user wants to create, add, set up, or manage web roles for their site") with concrete trigger verbs, matching the top anchor exactly.	5 / 5
Trigger Term Quality	"Use when the user wants to create, add, set up, or manage web roles" covers natural synonym phrasings users would say, plus domain keywords like "authenticated and anonymous roles" and "PAC-downloaded non-SPA sites". A few natural variants (e.g. "user roles", "site permissions" as trigger phrases) are absent, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The Power Pages web-roles niche (including PAC-downloaded non-SPA sites) is highly specific with distinct triggers, so overlap with other skills is minimal. Voice is third person, so no specificity penalty applies.	5 / 5
	Total	17 / 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
Revision: da8ea7a

Reviewed: 9 days ago

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.

create-webroles

Table of Contents

Is this your skill?