e2e 100/100 — SaferSkills

Is e2e safe to install?

SaferSkills independently audited e2e (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/e2e/SKILL.md · 1 file

skills/e2e/SKILL.md1.0 KB · Markdown

description: "Run or author a Maestro E2E flow on an iOS simulator. Usage: /podium-mcp:e2e <UDID> <BUNDLE_ID> [<flow-path-or-description>]"

Parse $ARGUMENTS as:

token 1 → UDID
token 2 → BUNDLE_ID
remaining text → either a file path (ends in .yaml/.yml) or a plain-language description of the journey to author

If a file path was given: Call run_flow with udid and files: [<path>]. Report every step's pass/fail. If any step fails, quote the relevant raw output lines.

If a description was given (or nothing):

Call inspect_screen on the UDID to enumerate tappable elements and their exact text/ids.
Author an inline Maestro YAML that only uses selectors you actually observed — never invent text. The flow must start with appId: <BUNDLE_ID> and launchApp: {stopApp: false}.
Call run_flow with the inline yaml.
Report each step result. If it fails, revise the flow once using the error and re-run.

Always show the per-step steps array in your response, not just a top-level pass/fail.

e2e— agent skill

Is e2e safe to install?

Audit the pieces. Scan the whole. Decide.