Skills expo-deployment

📦

expo-deployment

Name: expo-deployment
Author: expo

v1.0.0 Content revision r1 Safe ⚙️ External commands🌐 Network access🔑 Env variables

Deploy Expo Apps with EAS

Expo releases require platform-specific build, credential, and store submission steps. This skill guides EAS builds, submissions, metadata, workflows, and rollout planning.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "expo-deployment" from https://skillstore.io/skills/expo-expo-deployment.md and its manifest at https://skillstore.io/api/skills/expo-expo-deployment/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/expo-expo-deployment.md Signed manifest GET /api/skills/expo-expo-deployment/manifest Signed lockfile GET /api/skills/expo-expo-deployment/lockfile

Test it

Using "expo-deployment". I need to release my Expo app to both stores for the first time.

Expected outcome:

A release checklist covering account setup, production profiles, credential readiness, build commands, store records, review information, and final submission order.

Using "expo-deployment". Our team wants automated previews and tagged production releases.

Expected outcome:

A workflow plan that separates pull request previews, web deployment, native builds, store submissions, and approval checkpoints.

Using "expo-deployment". My Android release needs a safer rollout.

Expected outcome:

A staged rollout recommendation with internal testing first, track selection, service account checks, and monitoring steps after submission.

Security Audit

Safe

v4 • 7/5/2026 Open versioned report

The static findings are documentation examples, placeholders, or user-run Expo and EAS commands rather than hidden skill behavior. No evidence found of prompt injection, automatic command execution, credential exfiltration, or malicious network use in the cited files. The credential examples are legitimate but should keep strong warnings about secret storage.

Files scanned

1,534

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (24)

🌐 Network access (6)

references/app-store-metadata.md:272 references/app-store-metadata.md:51 references/app-store-metadata.md:52 references/app-store-metadata.md:53 references/app-store-metadata.md:273 references/workflows.md:19

🔑 Env variables (5)

references/app-store-metadata.md:292 references/app-store-metadata.md:292 references/ios-app-store.md:50 references/ios-app-store.md:51 references/ios-app-store.md:52

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/expo-expo-deployment/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/expo-expo-deployment/security.svg)](https://skillstore.io/skills/expo-expo-deployment?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/expo-expo-deployment?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/expo-expo-deployment/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/expo-expo-deployment.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

expo. (2026). expo-deployment security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/expo-expo-deployment/audits/4

BibTeX citation

@techreport{expo-expo-expo-deployment-2026,
  author = {expo},
  title = {expo-deployment security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/expo-expo-deployment/audits/4},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "expo-deployment security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
  - name: "expo"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/expo-expo-deployment/audits/4"
identifiers:
  - type: other
    value: "skillstore:expo-expo-deployment:audit:4"
    description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score

Author / source Skillstore Score Evidence Confidence Skillstore usage Updated

expo Recommended Current

expo-expo-deployment

Skillstore Score 78

Evidence Confidence High

Skillstore usage 8

Updated

2026-08-21

sickn33

sickn33-expo-deployment

Skillstore Score 77

Evidence Confidence High

Skillstore usage 12

Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Prepare a First Mobile Release

Plan the EAS setup, production build profile, and store submission sequence for a new Expo app.

Automate Release Workflows

Design build, submit, preview, and production deployment workflows for a team release process.

Improve Store Readiness

Review app metadata, rollout settings, track choices, and common rejection risks before launch.

Try These Prompts

Plan My First EAS Build

Help me prepare my Expo app for a first EAS production build. List the setup steps, required accounts, and checks before running commands.

Prepare Store Submission

Review my Expo release plan for App Store and Play Store submission. Identify missing credentials, metadata, store records, and testing steps.

Choose Release Tracks

Create a release-track plan for my Expo app. Include TestFlight, Play internal testing, staged rollout, and production release criteria.

Design Automated Deployment

Design an EAS Workflows strategy for builds, PR previews, web deploys, store submissions, and version management for a team Expo project.

Best Practices

Use EAS Secrets or protected CI variables for store credentials.
Start releases with internal testing before production rollout.
Verify store metadata, privacy details, and version numbers before submission.

Avoid

Committing service account keys or Apple private key files to source control.
Submitting directly to production before TestFlight or internal track validation.
Copying placeholder bundle identifiers, app IDs, URLs, or contact details unchanged.