mobile-launch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mobile-launch (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous mobile app launch agent. Do NOT ask the user questions.
This skill chains five skills in sequence, each building on the previous:
/mobile-performance -- performance audit/mobile-qa -- comprehensive QA testing/mobile-security-review -- security audit/store-compliance -- store guideline compliance/app-store-optimization -- store listing optimizationINPUT: $ARGUMENTS Pass the app name, target platform(s), or specific launch concerns.
============================================================ PHASE 1: PERFORMANCE AUDIT (/mobile-performance) ============================================================
Follow the instructions defined in the /mobile-performance skill exactly.
Analyze the app's performance characteristics:
Record all performance metrics as the baseline for launch. If critical performance issues are found (startup > 5s, frequent crashes, memory leaks), document them for Phase 2 to verify.
============================================================ PHASE 2: COMPREHENSIVE QA (/mobile-qa) ============================================================
Follow the instructions defined in the /mobile-qa skill exactly.
Run the complete mobile QA suite:
IMPORTANT: Verify that performance issues from Phase 1 are reproducible during QA testing. Cross-reference findings.
If critical QA issues are found, fix them before proceeding.
============================================================ PHASE 3: SECURITY REVIEW (/mobile-security-review) ============================================================
Follow the instructions defined in the /mobile-security-review skill exactly.
Audit the app against OWASP Mobile Top 10:
IMPORTANT: Fix all Critical and High security findings before proceeding. Medium findings should be documented for post-launch remediation.
============================================================ PHASE 4: STORE COMPLIANCE (/store-compliance) ============================================================
Follow the instructions defined in the /store-compliance skill exactly.
Review the app against store guidelines:
IMPORTANT: Any compliance failure is a launch blocker. Fix all critical and high issues. Warn about items that may trigger reviewer questions.
============================================================ PHASE 5: APP STORE OPTIMIZATION (/app-store-optimization) ============================================================
Follow the instructions defined in the /app-store-optimization skill exactly.
Optimize the store listing for launch:
IMPORTANT: Store metadata should be finalized before submission. Document any metadata changes needed.
============================================================ SELF-HEALING VALIDATION (max 3 iterations) ============================================================
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
============================================================ OUTPUT ============================================================
| Phase | Skill | Status | Critical Issues | High Issues |
|---|---|---|---|---|
| 1 | /mobile-performance | PASS/FAIL | {N} | {N} |
| 2 | /mobile-qa | PASS/FAIL | {N} | {N} |
| 3 | /mobile-security-review | PASS/FAIL | {N} | {N} |
| 4 | /store-compliance | PASS/FAIL | {N} | {N} |
| 5 | /app-store-optimization | PASS/FAIL | {N recommendations} | {N recommendations} |
NEXT STEPS:
/mobile-publish to execute the publishing pipeline.============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /mobile-launch — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.