Tessl • The management layer for AI agent skills

A lean, highly actionable skill body: exact URL templates, a copy-paste-ready command with complete argument handling, explicit stop/ask validation, and browser-failure recovery. The only structural weakness is that its core logic and shared instructions live in files outside the provided bundle, making the delegation unverifiable from this directory.

Suggestions

Include scripts/open-wrap-url.js in the skill's scripts/ directory (or verify its path resolves from the plugin root) so the delegated core logic is present and reviewable alongside SKILL.md.

Clarify the location and role of ../../shared/shared-instructions.md — a path escaping the skill directory is easy to break when the skill is moved or published.

Consider noting in the Notes section what the script does on failure beyond opening the URL (e.g., exit codes or messages), so fallback behavior is fully specified without reading the script.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational throughout — URL templates, an argument spec, one command, and fallback rules — with no explanation of concepts Claude already knows. Re-reading anchor 4 ('minor instances of over-explanation'), only the trivially redundant step summary on the 'Workflow' line could be trimmed, which does not pull it below 5.	5 / 5
Actionability	Guidance is fully executable: the copy-paste-ready command 'node scripts/open-wrap-url.js --app-id "<app-id>" --env-id "<environment-id>" [--env "Prod\|Test"]' plus exact URL templates cover the common Prod and Test cases. There are no missing key details that would warrant a 4.	5 / 5
Workflow Clarity	The simple two-step workflow has explicit checkpoints and feedback loops: 'If either value is missing in $ARGUMENTS, ask once for the missing value(s). If still missing, STOP' and 'If the browser auto-open fails, still print the URL and tell the user to open it manually'. The operation is read-only, so the destructive/batch validation cap does not apply.	5 / 5
Progressive Disclosure	Sections are well organized and references are one level deep and clearly signaled ('This skill delegates URL construction... to scripts/open-wrap-url.js', the shared-instructions.md link). However, the delegated script containing the core logic, '../../shared/shared-instructions.md', and the plugin check script all lie outside the provided bundle (no references/, scripts/, or assets/ directories exist), so the structure cannot fully verify as the clean self-contained 5.	4 / 5
	Total	19 / 20 Passed

Description

73%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 concise, third-person description with an explicit trigger clause and a distinct niche. Its main weaknesses are thin capability coverage (a single action with no mention of URL construction or Prod/Test environments) and a 'when' clause that largely restates the 'what' rather than adding discriminative trigger phrases.

Suggestions

Broaden the 'what' with the skill's actual capabilities, e.g. 'Builds and opens the Power Apps Wrap URL (Prod or Test host) for a given app ID', so specificity moves beyond a single action.

Add trigger synonyms users might naturally say, such as 'wrap build', 'wrap URL', or 'Power Apps wrap builder', to improve trigger term coverage.

Reconcile 'active environment' with the skill's behavior: the body requires an explicit --env-id argument, so the description's implication of auto-detecting the active environment is slightly inaccurate.

Dimension	Reasoning	Score
Specificity	"open the Power Apps Wrap page for an app ID" names the domain plus one concrete action, matching the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because the description does not list several actions (e.g., building the URL, Prod/Test environment handling) and not a 2 because the action is concrete rather than generic.	3 / 5
Completeness	Both parts are present: what ("open the Power Apps Wrap page") and an explicit when ("Use when the user wants to open the Power Apps Wrap page..."). It is not a 5 because the when-clause merely restates the single action and offers no additional concrete trigger phrases beyond it.	4 / 5
Trigger Term Quality	Terms like "Power Apps Wrap", "app ID", and "open" are exactly what a user needing this skill would naturally say. It falls short of anchor 5's comprehensive synonym coverage (missing variants like "wrap URL" or "build the wrap") but exceeds anchor 3's 'some relevant keywords'.	4 / 5
Distinctiveness Conflict Risk	"Power Apps Wrap" is a clear niche product feature with distinct triggers, making accidental activation for other skills very unlikely. This matches the 'clear niche with distinct triggers; minimal conflict risk' anchor exactly.	5 / 5
	Total	16 / 20 Passed

Validation

75%

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 — 12 / 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
relative_links	Relative link issues: 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	12 / 16 Passed

Repository: microsoft/power-platform-skills
Path: plugins/mobile-apps/skills/open-wrap-url/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.

open-wrap-url

Table of Contents

Is this your skill?