expo-cicd-workflows
Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.
87
83%
Does it follow best practices?
Impact
96%
1.26xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and completeness. It clearly identifies both what the skill does and when to use it, with domain-specific keywords that minimize conflict risk. The main weakness is that the 'what' portion could be more specific about the concrete actions beyond 'understand and write'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Helps understand, write, and debug EAS workflow YAML files—including configuring build steps, triggers, environment variables, and deployment targets—for Expo projects.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (EAS workflow YAML files for Expo projects) and mentions some actions ('understand and write'), but doesn't list multiple specific concrete actions like validating, debugging, creating build steps, configuring triggers, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (understand and write EAS workflow YAML files for Expo projects) and 'when' (explicit 'Use this skill when...' clause with multiple trigger scenarios including CI/CD questions, .eas/workflows/ mentions, and build pipeline/deployment automation needs). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'CI/CD', 'workflows', 'Expo', 'EAS', '.eas/workflows/', 'build pipelines', 'deployment automation', 'YAML files'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting EAS workflow YAML files specifically for Expo projects. The combination of EAS, Expo, workflow YAML, and .eas/workflows/ path makes it highly distinct and unlikely to conflict with generic CI/CD or YAML skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides clear workflows for generating and validating EAS workflow YAML files. Its main strengths are concrete executable commands, explicit validation steps with feedback loops, and smart use of remote schema fetching. Its weaknesses are moderate redundancy with information that the fetched schema already provides (expression contexts, top-level keys) and the inability to verify referenced bundle scripts exist.
Suggestions
Remove or significantly trim the 'Expressions' and 'Top-Level Structure' sections since this information is available in the fetched schema and syntax documentation — just note that these exist in the schema.
Provide the bundle files (scripts/fetch.js, scripts/validate.js) or note their expected behavior so the skill is self-contained and verifiable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary elaboration. Phrases like 'Do not rely on memorized values; these resources evolve as new features are added' and the enumeration of all expression contexts (github.*, inputs.*, etc.) add moderate bloat since Claude can derive these from the fetched schema. The top-level structure section partially duplicates what the schema provides. | 2 / 3 |
Actionability | Provides concrete, executable commands for fetching resources, installing dependencies, and validating workflows. The fetch and validate scripts have clear invocation syntax with actual paths. The 'Generating Workflows' section gives a specific checklist of validation steps to perform. | 3 / 3 |
Workflow Clarity | The workflow for generating/editing is clearly sequenced: fetch schema → validate required fields → verify references → check expressions → validate constraints. The validation step is explicit with a concrete command, and there's a clear feedback loop ('Fix any reported errors before considering the workflow complete'). The dependency installation check is also a nice pre-validation step. | 3 / 3 |
Progressive Disclosure | The skill references external scripts (fetch.js, validate.js) and remote resources appropriately, but no bundle files were provided to verify these exist. Some content like the full expression contexts list and top-level structure keys could be deferred to the schema itself rather than duplicated inline. The structure is reasonable but not optimally split. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- expo/skills
- Commit
47f0ef6
- 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.