SKILLEMALL.ai
GitHub ↗ RU Sign in

BF report-issue

Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.

microsoft/power-platform-skills Claude Code author: microsoft 1 file body ≈ 1 544 tokens Open the sourcegithub.com↗ analyzed 2 h ago

Generates a fully-populated GitHub issue body for the microsoft/power-platform-skills repo, scoped to the mobile-app plugin.

As a process F 50/100 · Will not run — References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md

ProcedureData and analyticstype 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
88/100
safety, quality, tests
Safety 60%
95
Quality 40%
78
Run on models
none yet
Process rating
F
50/100
Will not run
References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.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. 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 Bash Glob Grep AskUserQuestion

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ${PLUGIN_ROOT}/shared/shared-instructions.md
  • note edit-residue the text marks something as outdated (lines 132): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ${PLUGIN_ROOT}/shared/shared-instructions.md
  • 0Tools and files. 1 referenced file(s) missing: ${PLUGIN_ROOT}/shared/shared-instructions.md
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 65Failures and branches. 3 branches
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 12 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1544 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (3 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 126: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (6 code blocks)

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