CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-builder

Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows, generative page intents for overview/dashboard surfaces, and an app module + sitemap. Runs an interactive authoring flow with plan approval and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", "add a business process flow", or "edit/add to my app". Do not use it for a generic web or React app or website, Power Pages, canvas apps, or Power Automate, or when the user rules out Power Platform, Dataverse, or model-driven apps (for example "no Power Platform"). This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpage instead.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/model-apps/skills/app-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

58%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 delivers an exceptionally actionable, well-sequenced workflow with genuine validation gates and error-recovery loops — among the strongest operational guidance a skill can have. But it pays for that with severe token bloat: ~27k tokens of dense, repetitive, exception-driven prose loaded on every invocation, much of it reference material that belongs in on-demand files. Actionability and workflow clarity are top-tier; conciseness and progressive disclosure pull the overall quality well down.

Suggestions

Move the Griffel shorthand list, longhand expansion rules, and iterator-compatibility rules into the referenced rules file, keeping only the check command and 'fix what it reports, rerun until exit 0' inline — this alone removes ~100 lines that duplicate the checker's own output.

Consolidate the table-publish scoping logic, which is stated at length twice (Phase 2 '--publish' section and Notes & limits), into one authoritative location and cross-reference it.

Move the per-feature 'minimumPluginVersion' gates and the declared form/dashboard/rule/BPF adoption and halt minutiae into the advanced schema reference, leaving one-line decision rules ('only when the maker asks; explain the approval') in the toolbox bullets.

DimensionReasoningScore

Conciseness

A ~1281-line / ~27k-token body that is severely padded: the Griffel section enumerates ten shorthands and their longhand expansions inline (~40 lines) instead of trusting the checker's own output; the table-publish scoping logic is stated at full length twice (Phase 2 and Notes & limits); single sentences run 300+ words (the declared-form bullet); and "minimumPluginVersion: \"2.21.0\"" is repeated inline ~15 times. Not 2: the verbosity is systemic and repetitive rather than a few padded sections — 'severely verbose ... heavily padded' is the closest anchor, and the guideline 'penalize verbosity even if accurate' applies fully.

1 / 5

Actionability

Every step ships a copy-paste-ready command with flags, expected output, and failure semantics: `build-model-app.js --env <envUrl> --spec @<working-dir>/app-spec.json --apply --verify`, "exits 3 and leaves app-spec.json untouched", `{ ok, planPath, pages: [{ name, key, file, dataMode, intent }] }`, and a complete verbatim worker-dispatch contract. Not 4: commands are fully executable, common cases are covered, and even exit codes and stderr behavior are specified.

5 / 5

Workflow Clarity

The workflow is clearly phased (Phase 0 → 1 → 1.5 → 2 → 3) with explicit validation at every gate: the lint hard gate ("errors block"), single plan-mode approval on the dry-run plan, the atomic promote-intent-pages check, `--verify` after apply, and teardown dry-run by default with `--allow-destructive` required. Feedback loops are spelled out ("fix what it reports and run it again", halt codes each with a recovery hint, "run the full build again" for recovery). Not 4: checkpoints and error-recovery loops are explicit throughout, including for the destructive teardown and batch data-fix paths.

5 / 5

Progressive Disclosure

References are well signaled and one level deep ("[references/authoring-flow.md]", "read app-spec-schema-advanced.md once your design calls for a conditional feature"), but hundreds of lines of reference-grade detail are inlined in SKILL.md itself — Griffel/iterator rules, publish scoping, declared form/dashboard/rule/BPF adoption minutiae, teardown ordering — and none of the referenced files (references/, scripts/, samples/) exist in the reviewed bundle. Not 3: the inlining is not one or two sections but the dominant structure of a 1281-line file that functions as its own reference manual; not 1: sections are well organized and references that are made are clearly signaled.

2 / 5

Total

13

/

20

Passed

Description

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

An excellent description: dense, third-person, and specific, listing concrete capabilities across the full build-and-edit lifecycle, with explicit quoted trigger phrases, named exclusions, and sibling-skill disambiguation. Its only cost is length, but every clause is substantive rather than padded. It matches the strongest anchor on all four dimensions.

DimensionReasoningScore

Specificity

Quotes: "Builds and edits a model-driven Power Apps app ... tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business process flows ... and an app module + sitemap" plus "can download a deployed app back into an editable spec to change it" — multiple concrete, named actions covering the data model, UI surfaces, automation, app shell, and the edit round-trip. Not 4: the capability list spans the whole build-and-edit lifecycle with no notable gap, matching the 'comprehensive coverage' anchor.

5 / 5

Completeness

Explicit what (builds/edits model-driven Power Apps apps, enumerating artifacts) and explicit when: "Use when the user says 'build an app for X' ...", with concrete quoted trigger phrases and a when-not clause. Not 4: the 'when' is fully explicit with quoted phrases rather than merely stated or implied.

5 / 5

Trigger Term Quality

Quotes natural user phrasings with synonym variants: "build an app for X", "create a model-driven app", "make me an app to manage Y", "add a business process flow", "edit/add to my app", plus the negative trigger "no Power Platform". Not 4: the quoted phrases cover the natural ask-space including the edit entry point, satisfying 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (model-driven Power Apps on Dataverse) with active disambiguation: "Do not use it for a generic web or React app or website, Power Pages, canvas apps, or Power Automate, or when the user rules out Power Platform, Dataverse, or model-driven apps" and the /genpage deferral for standalone generative pages. Not 4: overlap risk is not just minor but explicitly handled against named sibling tools.

5 / 5

Total

20

/

20

Passed

Validation

68%

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

Validation — 11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1281 lines); consider splitting into references/ and linking

Warning

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: 13 suspicious

Warning

referenced_paths_exist

Referenced path issues: 23 missing

Warning

Total

11

/

16

Passed

Repository

microsoft/power-platform-skills

Path

plugins/model-apps/skills/app-builder/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.