SKILLEMALL.ai
GitHub ↗ RU Sign in

BF configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a deployment-settings.json file with per-stage override values. Use when asked to: "configure environment variables", "add env vars", "set up deployment variables", "make site settings environment-specific", "configure ALM variables", "set up env-specific settings", "add deployment settings", "configure per-environment settings".

microsoft/power-platform-skills Claude Code author: microsoft 2 files body ≈ 8 230 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Configures environment variables for Power Pages site settings to support ALM across environments.

As a process F 46/100 · Will not run — References files that are not bundled: scripts/lib/link-site-setting-to-env-var.js, scripts/lib/validate-deployment-settings.js, scripts/lib/verify-env-var-values.js

AnalyzerAzureInfrastructuretype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
81/100
safety, quality, tests
Safety 60%
95
Quality 40%
59
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: scripts/lib/link-site-setting-to-env-var.js, scripts/lib/validate-deployment-settings.js, scripts/lib/verify-env-var-values.js
Tools and files w 18
0
Result and completion w 14
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Edit Bash Glob Grep TaskCreate TaskUpdate TaskList AskUserQuestion

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 8230 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/lib/link-site-setting-to-env-var.js
  • warning missing-ref reference to a missing file: scripts/lib/validate-deployment-settings.js
  • warning missing-ref reference to a missing file: scripts/lib/verify-env-var-values.js
  • note edit-residue the text marks something as outdated (lines 262, 275, 280): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: scripts/lib/link-site-setting-to-env-var.js, scripts/lib/validate-deployment-settings.js, scripts/lib/verify-env-var-values.js
  • 0Tools and files. 3 referenced file(s) missing: scripts/lib/link-site-setting-to-env-var.js, scripts/lib/validate-deployment-settings.js, scripts/lib/verify-env-var-values.js
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 65 mutating operations with no state check
  • 40Execution cost. Instruction body is 8230 tokens: crowds the task out of the window
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 40 steps, 1 vague phrases
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 12 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (10 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 8 example trigger phrases
  • +3Description length 636: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (28 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.