CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-deployment

Deploy Expo apps to production

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/expo-deployment/SKILL.md

The canonical home for this skill is expo-deployment in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

46%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured as an overview but provides no executable commands or concrete examples, and its deployment workflows lack validation checkpoints and feedback loops despite covering risky production-release operations.

Suggestions

Replace abstract steps with concrete EAS commands, e.g. `eas build --platform all --profile production`, `eas submit`, and `eas update --channel production`.

Add explicit validation checkpoints and feedback loops, e.g. verify the build succeeds and tests pass before submission, and check submission status with retry on failure.

Remove the redundant restatement in "When to Use" (the lead sentence duplicates the first bullet) and de-duplicate the Instructions list against the Deployment Workflow.

DimensionReasoningScore

Conciseness

The body is reasonably lean and avoids explaining concepts Claude already knows, but the "When to Use" section restates its opening sentence verbatim as the first bullet and the Instructions list overlaps the Deployment Workflow, so it could be tightened.

3 / 5

Actionability

It only describes steps at a high level ("Build production binaries", "Submit to App Store Connect / Google Play Console") with no executable commands such as `eas build` or `eas submit`, matching the anchor for minimal concrete guidance missing the specific steps to execute.

2 / 5

Workflow Clarity

Steps are sequenced across Pre-Deployment, App Store, and OTA sections, but there are no explicit validation checkpoints or feedback loops (validate -> fix -> retry); since production submission and OTA rollout are risky operations, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

The body is well-organized into clearly labeled sections with no deeply nested references, and this thin overview does not require external bundle files; it falls just short of a 5 because at ~65 lines it exceeds the under-50-line simple-skill exception and contains no progressive pointers.

4 / 5

Total

12

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and clearly niched to Expo deployment, but it states only one generic action and omits any explicit "Use when..." trigger guidance, capping both specificity and completeness.

Suggestions

Add 2-3 concrete actions to raise specificity, e.g. "Submit to the iOS App Store and Google Play, publish OTA updates, and manage release channels."

Append an explicit trigger clause: "Use when deploying an Expo/React Native app to production, publishing to app stores, or pushing OTA updates."

Include natural synonyms users say (EAS, app store, OTA, release) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description "Deploy Expo apps to production" names the domain (Expo apps) but offers only one generic action (Deploy), matching the anchor for minimal/generic actions rather than the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

It gives a clear "what" (deploy Expo apps to production) but lacks any explicit "Use when..." trigger clause, so per the judging guidelines completeness is capped at 3 for a clear what with missing/weakly-implied when.

3 / 5

Trigger Term Quality

Natural terms like "Deploy", "Expo apps", and "production" are present, but common variations and synonyms a user might say (app store, EAS, OTA, release) are missing, fitting the anchor for some relevant keywords with gaps.

3 / 5

Distinctiveness Conflict Risk

The Expo-specific niche is mostly distinct with only minor overlap risk against closely related general mobile or React Native deployment skills, matching the anchor for mostly distinct with minor overlap.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.