SKILLEMALL.ai
GitHub ↗ RU Sign in

BF debug-extension

Diagnose and fix failures in a built third-party `.ppmplugin` control: crashes, silent no-ops, PCF error outputs, or incorrect behavior. Uses the reported symptom, `shared/error-codes.md`, and file-level evidence to trace the manifest, Android/iOS modules, PCF dispatch, and build configuration. Produces a ranked diagnosis, asks for approval, then applies a surgical fix while keeping the committed manifest and affected contracts synchronized. Re-validates manifest changes through /generate-ppmplugin-manifest.

microsoft/power-platform-skills Agent Skills author: microsoft 1 file body ≈ 6 636 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Diagnose and fix failures in a built third-party .ppmplugin control: crashes, silent no-ops, PCF error outputs, or incorrect behavior. Uses the reported…

As a process F 43/100 · Will not run — References files that are not bundled: ../../shared/naming-conventions.md, ../../shared/self-critique-protocol.md

AnalyzerSoftware developmentData and analyticsWriting and documentstype 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
78/100
safety, quality, tests
Safety 60%
95
Quality 40%
53
Run on models
none yet
Process rating
F
43/100
Will not run
References files that are not bundled: ../../shared/naming-conventions.md, ../../shared/self-critique-protocol.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 AskUserQuestion Skill

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 6636 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: ../../shared/naming-conventions.md
  • warning missing-ref reference to a missing file: ../../shared/self-critique-protocol.md

Process rating: all ten parameters 43/100

Will not run. References files that are not bundled: ../../shared/naming-conventions.md, ../../shared/self-critique-protocol.md
  • 0Tools and files. 2 referenced file(s) missing: ../../shared/naming-conventions.md, ../../shared/self-critique-protocol.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 12 mutating operations with no state check
  • 70Execution cost. Instruction body is 6636 tokens
  • 100Steps. 67 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 15 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (20 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 513: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 67 items
  • +4Has examples (7 code blocks)

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