CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-deployment

Deploy Expo apps to production

32

Quality

26%

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/antigravity-bundle-expo-react-native/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

17%Scale 1-5

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

This skill is essentially a high-level outline or table of contents with no actionable content. It lacks any concrete commands (e.g., `eas build`, `eas update`, `eas submit`), configuration examples (e.g., `eas.json` profiles), or specific guidance that would help Claude actually deploy an Expo app. It reads more like a topic overview than a usable skill.

Suggestions

Add concrete EAS CLI commands for each workflow step (e.g., `eas build --platform ios --profile production`, `eas submit --platform ios`, `eas update --branch production`)

Include example `eas.json` and `app.json`/`app.config.js` configuration snippets for production builds

Add validation checkpoints such as verifying build success, checking update deployment status with `eas update:list`, and testing production builds locally with `npx expo start --no-dev`

Remove the redundant 'When to Use This Skill' section and the vague 'Instructions' preamble to reduce token waste

DimensionReasoningScore

Conciseness

The skill is padded with vague, high-level descriptions that Claude already knows. The 'When to Use This Skill' section repeats the overview, and the instructions section merely lists categories without adding actionable detail. Much of the content is filler.

2 / 5

Actionability

There are zero concrete commands, code snippets, or executable steps. Every instruction is abstract and vague (e.g., 'Build production binaries', 'Configure update channels') with no actual EAS CLI commands, configuration examples, or app.json/eas.json snippets.

1 / 5

Workflow Clarity

A rough sequence is present (pre-deployment, app store deployment, OTA updates) but steps are poorly defined with no specific commands, no validation checkpoints, and no error recovery guidance. Steps like 'Handle app review process' are not actionable workflow items.

2 / 5

Progressive Disclosure

There are no bundle files and only a single external link to a source repository. The content is a monolithic list of vague bullet points with no references to detailed guides for specific topics like EAS Build configuration, store submission, or OTA setup. Content that should be detailed somewhere is simply absent.

2 / 5

Total

7

/

20

Passed

Description

36%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 extremely terse, providing only a high-level action without detailing specific capabilities or when the skill should be triggered. It names the technology (Expo) which helps with distinctiveness, but lacks the concrete actions, trigger terms, and 'Use when...' guidance needed for reliable skill selection among many options.

Suggestions

Add a 'Use when...' clause with trigger terms like 'deploy', 'publish', 'app store', 'EAS', 'build for production', 'submit to Apple/Google'.

List specific concrete actions such as 'configure EAS Build, submit to App Store and Google Play, manage app signing, set up OTA updates'.

Include related natural keywords and synonyms users might say: 'React Native', 'mobile app release', 'expo build', '.apk', '.ipa', 'app bundle'.

DimensionReasoningScore

Specificity

Names the domain (Expo apps) and a single generic action (deploy to production), but provides no concrete sub-actions like building, submitting to app stores, configuring EAS, etc.

2 / 5

Completeness

Has a vague 'what' (deploy Expo apps to production) but completely lacks a 'when' clause or any trigger guidance for when Claude should select this skill.

2 / 5

Trigger Term Quality

Includes relevant keywords 'Expo' and 'deploy' and 'production' which users might say, but misses common synonyms and related terms like 'EAS', 'app store', 'publish', 'build', 'submit', 'React Native', or 'release'.

3 / 5

Distinctiveness Conflict Risk

Somewhat specific to Expo deployment which narrows the domain, but could overlap with general deployment skills, React Native skills, or mobile app publishing skills without clearer boundaries.

3 / 5

Total

10

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.