Skip to content
TrustedSkillsbeta
Back to all skills

Expo Router

Checked
jchaselubitz·vlatest·frontend

Automates Expo Router project setup, navigation generation, and component scaffolding for rapid React Native web app development.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jchaselubitz/drill-app --skill expo-router -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jchaselubitz

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jchaselubitz/drill-app at 1070527074.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1070527074
Manifest
.claude/skills/expo-router/SKILL.md
Scanned
2 files, 106 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

expo-router

What it does

Expo Router enables declarative navigation and file-based routing within Expo applications, replacing complex manual navigation logic with a filesystem-driven structure. It allows developers to define app routes directly in code files, streamlining the development of mobile interfaces.

When to use it

  • Building new Expo projects that require a scalable, maintainable navigation architecture from the start.
  • Replacing legacy react-navigation setups where file-based organization is preferred over complex configuration objects.
  • Developing apps that need seamless integration between static routes and dynamic parameters without boilerplate code.

Key capabilities

  • File-based routing: Routes are defined by creating files in the project directory structure.
  • Declarative navigation: Navigation logic is inferred from the file system rather than imperative commands.
  • Type safety: Provides built-in type checking for route parameters and query strings.
  • Nested layouts: Supports complex UI structures with nested layout definitions for consistent headers or footers.

Example prompts

  • "Create a new page component at /settings/profile that displays user details."
  • "Set up a dynamic route pattern to handle multiple product pages based on an ID parameter."
  • "Configure a root layout that wraps all child screens with a consistent navigation bar."

Tips & gotchas

Ensure your project is initialized with the expo-router package and configured correctly in app.json before attempting to use file-based routes. Avoid mixing imperative navigation calls with declarative routing patterns, as this can lead to inconsistent state management.