CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deploy

Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is an exemplary concise operational skill: a clear four-step workflow with explicit validation checkpoints and error-recovery feedback loops, fully executable commands, and clean delegation of shared concerns to clearly linked plugin files. No material weaknesses were found.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence throughout ("If not found, proceed — the project may have been created without the plugin"); there is no explanation of what Power Apps, builds, or deployment are, and every instruction is operational. Matches anchor 5 (lean and efficient; every token earns its place).

5 / 5

Actionability

Commands are copy-paste ready ("npm run build", "pa app push", "pa auth logout") and the common failure cases are concretely covered: a named TS error code with its fix, a dist/ existence check, and a specific config edit ("update `environmentId` in `power.config.json`"). Matches anchor 5 (fully executable, common cases covered).

5 / 5

Workflow Clarity

The four steps (Check Memory Bank → Build → Deploy → Update Memory Bank) are clearly sequenced with explicit validation checkpoints (build-failure handling, "Verify `dist/` exists with `index.html` before continuing", user confirmation before updating the live app) and feedback loops for error recovery (auth error → logout → retry; environment mismatch → fix → retry). Matches anchor 5; the destructive-operation cap does not apply since validation before deploying the live app is present.

5 / 5

Progressive Disclosure

A short, well-sectioned body that appropriately delegates cross-cutting concerns via clearly signaled one-level-deep links to shared plugin files (shared-instructions.md, cli-binary.md), with no inline content that belongs elsewhere. No local references/scripts/assets bundle exists to nest, and the structure is easy to navigate — matching the simple-skill case for anchor 5.

5 / 5

Total

20

/

20

Passed

Description

78%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, well-structured description with a clear third-person what-statement and an explicit 'Use when...' clause covering natural trigger phrases. Its only weakness is modest action specificity (build/deploy only) and trigger terms that are generic outside the Power Platform context.

Suggestions

Add one or two more concrete capabilities to the what-statement (e.g., resolving auth errors or updating the environment config) to lift specificity beyond the two-action level.

Add a synonym trigger such as "publishing or releasing the app" to broaden natural-term coverage and sharpen distinction from generic deploy skills.

DimensionReasoningScore

Specificity

"Builds and deploys a Power Apps code app to Power Platform" names the domain plus exactly two concrete actions (build, deploy), with no coverage of supporting capabilities like validation, configuration, or error recovery. This matches anchor 3 (1-2 concrete actions, not comprehensive); it is not 4 because 'builds' and 'deploys' alone don't constitute several specific actions.

3 / 5

Completeness

The description explicitly answers both: what ("Builds and deploys a Power Apps code app to Power Platform") and when ("Use when deploying changes, redeploying an existing app, or pushing updates") with three concrete trigger phrases. This matches the anchor-5 example structure exactly, so 4 (when 'could be more explicit') does not fit.

5 / 5

Trigger Term Quality

"deploying changes", "redeploying an existing app", and "pushing updates" are natural phrases a user would say, giving good keyword coverage. Not 5 because common synonyms such as "publish", "release", or "ship" are missing.

4 / 5

Distinctiveness Conflict Risk

"Power Apps code app to Power Platform" establishes a clear niche, keeping conflict risk low, but the trigger phrases themselves ("deploying changes", "pushing updates") are generic and could overlap with other deploy/release skills. Mostly distinct with minor overlap risk with closely related skills is the anchor-4 fit; not 5 because the triggers alone would not discriminate.

4 / 5

Total

16

/

20

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

Validation for skill structure

CriteriaDescriptionResult

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: 2 missing, 2 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

microsoft/power-platform-skills

Path

plugins/code-apps/skills/deploy/SKILL.md

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.