CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-deployment

Deploy Expo apps to production

47

Quality

50%

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-claude/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 content is well-structured and reasonably concise, but it is more of an outline than an actionable playbook: it names steps without the commands to execute them and omits validation/rollback checkpoints for production-affecting operations. Adding concrete EAS commands and verification steps would substantially raise actionability and workflow clarity.

Suggestions

Replace the descriptive bullets with executable commands, e.g. `eas build --platform all --profile production`, `eas submit`, and `eas update --channel production`.

Add explicit validation checkpoints to each workflow phase (e.g. verify the production build runs locally, confirm the store submission status, monitor OTA update adoption before full rollout).

Collapse the redundant Instructions list into the Workflow section (or vice versa) to remove the repeated enumeration of the same five areas.

DimensionReasoningScore

Conciseness

The body is mostly lean and free of concept-explaining padding, but the Overview, "When to Use", and Instructions sections restate the same five deployment areas already detailed in the Workflow, which could be tightened.

3 / 5

Actionability

Guidance stays at a high level ("Build production binaries", "Submit to App Store Connect / Google Play Console", "Use EAS Build") with no actual commands or code such as `eas build`, `eas submit`, or `eas update`, leaving the specific execution steps missing.

2 / 5

Workflow Clarity

Pre-Deployment, App Store, and OTA phases give a clear sequenced workflow, but there are no validation checkpoints (e.g. verify the build, confirm submission status) and rollback is only a bullet, not a feedback loop; for production/OTA deployment the rubric caps workflow_clarity at 3.

3 / 5

Progressive Disclosure

It is a single concise, well-sectioned file with one clearly signaled external reference (the source repo) and no nested references; the minor duplication between the Instructions list and the Workflow keeps it just below a 5.

4 / 5

Total

12

/

20

Passed

Description

53%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 clear and distinct but bare: it states one action and omits any "Use when..." trigger guidance. Adding explicit trigger phrases and listing the concrete capabilities (build, store submission, OTA, release management) would lift specificity, trigger quality, and completeness.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g. "Use when publishing to the iOS App Store or Google Play, setting up OTA updates, or managing Expo release channels."

Expand the single action into a few concrete capabilities (e.g. "Build, submit to app stores, and push OTA updates for Expo apps") to raise specificity.

Include natural synonyms and file/tool terms users say (App Store, Google Play, EAS, OTA, release channel) to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Deploy Expo apps to production") but does not enumerate the several specific actions (build, submit, OTA, release channels) it covers, so it stops at the 1-2 concrete actions anchor rather than reaching 4.

3 / 5

Completeness

It gives a clear "what" (deploy Expo apps to production) but has no "Use when..." clause or explicit trigger guidance; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"Deploy Expo apps to production" includes a natural phrase a user would say, but misses common variations and synonyms (App Store, Google Play, OTA, EAS, publish, release), keeping it below the good-coverage anchor of 4.

3 / 5

Distinctiveness Conflict Risk

"Deploy Expo apps to production" carves out a clear niche (Expo deployment) with minimal conflict risk, sitting just below the comprehensive-trigger anchor of 5.

4 / 5

Total

13

/

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.