CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deploy

Use to deploy, publish, or push an Expo/React Native Power Apps mobile app to a Power Platform tenant.

Quality

81%

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

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

An exemplary operational skill body: every step is executable, validated, and gated, with genuinely non-obvious project knowledge (the first-deploy two-cycle requirement, the export hang workaround) that earns its tokens. The only structural improvement is pushing more of the Step 2.5 reconciliation handoff detail and known-issue exposition into the referenced files to slim the main body.

DimensionReasoningScore

Conciseness

Efficient, operationally dense content with almost no general-knowledge padding — the long explanations (export hang, two-cycle first deploy) are non-obvious project-specific gotchas, not things Claude already knows. Minor trimming possible: the two-cycle rationale is explained in Step 1.5 (including the user-facing quote) and repeated in Step 3's "First-deploy loop-back".

4 / 5

Actionability

Fully executable throughout: copy-paste bash blocks (schema regeneration, Node version gate, Hermes c61fbc03 magic-byte verification, detached export with log polling), exact confirmation phrases ("yes deploy to <env-name>", "deploy without offline"), and an error-to-fix table. All common cases are covered.

5 / 5

Workflow Clarity

Explicit numbered sequence (1 → 1.5 → 2 → 2.4 → 2.5 → 3 → 4) with validation checkpoints at every risky step (dist verification, Node gate, bundle/manifest checks, offline delta gate, environment mismatch gate), feedback loops for error recovery (fix-and-retry, re-run delta check after reconciliation), explicit STOP conditions, and hard confirmation gates before the live push.

5 / 5

Progressive Disclosure

References to shared/plugin files are clearly signaled, one level deep, and each states its purpose (cli-binary.md, offline-profile-reconciliation.md, app-working-directory.md, version-check.md, memory-bank.md), with a bottom Reference section. However, ~150 lines of gate and reconciliation detail (Step 2.5's scoped-helper handoffs, the export-hang known issue) are inlined in the body and could partly live in the referenced files.

4 / 5

Total

18

/

20

Passed

Description

70%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 clear, specific, and distinctive description that names its niche precisely, but it omits any "Use when..." trigger guidance, so an agent deciding when to invoke it must infer the trigger from context. Adding an explicit trigger clause would make it fully self-describing.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to deploy, publish, push, or release their Power Apps mobile app, or mentions deploying to a Power Platform environment/tenant."

Include common synonyms users actually say ("release", "ship", "roll out", "update the live app") so the description triggers on natural phrasing.

Optionally mention the end state (app updates for every user in the tenant) so the what/when pair answers both questions concretely.

DimensionReasoningScore

Specificity

Lists concrete actions ("deploy, publish, or push") with a highly specific target ("Expo/React Native Power Apps mobile app to a Power Platform tenant"), but deploy/publish/push are near-synonyms and sub-capabilities are uncovered — minor gaps in coverage rather than comprehensive.

4 / 5

Completeness

The "what" is clear and concrete, but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3. It is not a 4 because the "when" is absent rather than merely underspecific.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("deploy", "publish", "push", "mobile app", "Power Apps", "Power Platform", "tenant") with good keyword coverage; a few natural variants like "release", "ship", or platform file extensions are missing.

4 / 5

Distinctiveness Conflict Risk

"Expo/React Native Power Apps mobile app to a Power Platform tenant" carves out a clear niche with distinct triggers; no generic phrasing that could fire this for an unrelated skill.

5 / 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: 8 missing, 8 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

microsoft/power-platform-skills

Path

plugins/mobile-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.