mobile-publish — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited mobile-publish (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 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.
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 publishing agent. Do NOT ask the user questions.
This skill chains four skills in sequence, each building on the previous:
/mobile-ci-cd -- CI/CD pipeline setup/app-store-publish -- iOS App Store publishing/play-store-publish -- Google Play Store publishing/mobile-analytics -- analytics verificationINPUT: $ARGUMENTS Pass the app name, target platforms, or specific publishing requirements. If only one platform is targeted, skip the irrelevant store publishing phase.
============================================================ PHASE 1: CI/CD PIPELINE SETUP (/mobile-ci-cd) ============================================================
Follow the instructions defined in the /mobile-ci-cd skill exactly.
Set up the complete mobile CI/CD pipeline:
IMPORTANT: Record all required secrets and environment variables. Document how to obtain each credential. The CI/CD pipeline is the foundation for all subsequent publishing phases.
Commit all workflow files.
============================================================ PHASE 2: IOS APP STORE PUBLISHING (/app-store-publish) ============================================================
Follow the instructions defined in the /app-store-publish skill exactly.
Skip this phase if the app does not target iOS.
Configure the complete iOS publishing pipeline:
IMPORTANT: Ensure Fastlane lanes integrate with the CI/CD workflows from Phase 1. The beta lane should be triggered on merge to develop. The release lane should be triggered on version tags.
Commit all Fastlane iOS configuration.
============================================================ PHASE 3: GOOGLE PLAY STORE PUBLISHING (/play-store-publish) ============================================================
Follow the instructions defined in the /play-store-publish skill exactly.
Skip this phase if the app does not target Android.
Configure the complete Android publishing pipeline:
IMPORTANT: Ensure Fastlane lanes integrate with the CI/CD workflows from Phase 1. The internal lane should be triggered on merge to develop. The release lane should be triggered on version tags.
Commit all Fastlane Android configuration.
============================================================ PHASE 4: ANALYTICS VERIFICATION (/mobile-analytics) ============================================================
Follow the instructions defined in the /mobile-analytics skill exactly.
Verify the analytics implementation is complete before publishing:
IMPORTANT: Analytics must be verified before the first public release. Missing analytics cannot be backfilled -- the data is lost forever. Ensure crash reporting is configured with dSYM/mapping file upload in the CI/CD pipeline from Phase 1.
============================================================ 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 | Details |
|---|---|---|---|
| 1 | /mobile-ci-cd | PASS/FAIL | {platform}, {N} workflows, {N} jobs |
| 2 | /app-store-publish | PASS/FAIL/SKIPPED | Fastlane configured, {N} lanes |
| 3 | /play-store-publish | PASS/FAIL/SKIPPED | Fastlane configured, {N} lanes |
| 4 | /mobile-analytics | PASS/FAIL | {N}% event coverage, {N} funnels ready |
| Workflow | Trigger | iOS | Android |
|---|---|---|---|
| Test | PR | {configured} | {configured} |
| Beta | Merge to develop | TestFlight | Internal Track |
| Release | Version tag | App Store | Production (staged) |
| Secret | Platform | Status | How to Obtain |
|---|---|---|---|
| {secret} | {iOS/Android/Both} | {configured/needed} | {instructions} |
| Element | iOS | Android | Status |
|---|---|---|---|
| Title | {ready/template} | {ready/template} | {action} |
| Description | {ready/template} | {ready/template} | {action} |
| Screenshots | {ready/needed} | {ready/needed} | {action} |
| Keywords | {ready/template} | N/A | {action} |
| Privacy Policy | {url set/needed} | {url set/needed} | {action} |
{list all generated files: workflows, Fastlane configs, metadata}
NEXT STEPS:
/mobile-launch for the full pre-launch quality 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-publish — {{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.