SKILLEMALL.ai

BF build-ios-binary

Compile a PAM control's iOS Obj-C/Swift module into the FLAT device-slice `.framework` for a `.ppmplugin` bundle (never an `.xcframework` — the wrap CI won't descend into one). Mac-only (Xcode). Builds from a throwaway staged copy so canonical `ios/` and the podspec stay untouched, references React-Core headers only (React is weak-linked and provided by the wrap host at runtime, no CocoaPods), generates the required umbrella header, module map and Info.plist, sets the critical build settings, asserts manifest conformance, then runs a device-only `xcodebuild archive` and copies out the flat framework to `ppmplugin/staging/ios/`. Known limitation — the React weak-link flags aren't yet validated against a live wrap host and the RN pin must match the host's. Run after /generate-ppmplugin-manifest for an iOS or Both target, before /assemble-ppmplugin.

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

Compile a PAM control's iOS Obj-C/Swift module into the FLAT device-slice .framework for a .ppmplugin bundle (never an .xcframework — the wrap CI won't…

As a process F 46/100 · Will not run — References files that are not bundled: ../build-android-binary/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/naming-conventions.md

GeneratorSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: ../build-android-binary/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/naming-conventions.md
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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  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 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 missing-ref reference to a missing file: ../build-android-binary/SKILL.md
  • warning missing-ref reference to a missing file: ../../shared/ppmplugin-format.md
  • warning missing-ref reference to a missing file: ../../shared/naming-conventions.md
  • warning missing-ref reference to a missing file: ../generate-ppmplugin-manifest/SKILL.md
  • warning missing-ref reference to a missing file: ../assemble-ppmplugin/SKILL.md
  • warning missing-ref reference to a missing file: ../../shared/shared-instructions.md
  • note edit-residue the text marks something as outdated (lines 50): 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: ../build-android-binary/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/naming-conventions.md
  • 0Tools and files. 6 referenced file(s) missing: ../build-android-binary/SKILL.md, ../../shared/ppmplugin-format.md, ../../shared/naming-conventions.md
  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 26 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3574 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (11 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)
  • +3Description length 858: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 26 items
  • +4Has examples (3 code blocks)

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