What does this skill do, and when should you use it?
This skill guides AI coding assistants through create-react-native-library for React Native library creation. It covers standalone libraries that may be published to npm and local libraries inside existing apps. The scope includes JavaScript-only libraries, native modules, and native UI components. It selects the standalone or local workflow and points the implementation toward the corresponding reference documentation.
It first inspects the create-react-native-library CLI options, then runs npx create-react-native-library with scaffold parameters. The examples create a standalone library with an Expo example app or a local Turbo Module inside an existing React Native app. The shown options include non-interactive execution, Kotlin/Objective-C language selection, descriptions, and Turbo Module type.
- A React Native developer needs a new JavaScript or native library that may be published to npm.
- An application team needs to wrap a native SDK and expose it to JavaScript from an existing React Native app.
- A developer needs a React Native UI component that renders a native view.
- A team needs to add a local native module or view to an existing application.
How do you install this skill?
- The commands use npx create-react-native-library@latest, --yes, and non-interactive execution; users should confirm the CLI version, flags, target directory, and intended changes first.
- No rollback or recovery procedure is defined, and dependencies are not pinned with a compatibility matrix.
- External dependencies including CocoaPods, Expo, Nitro, and npm/Yarn registries may vary by network, platform, and version; mainland-China reachability is not documented.
- The standalone flow says to use only Yarn, while the local flow describes both Yarn and npm; this should be checked against the generator's actual behavior.
- Shell / CLI
- Network access
- Local filesystem
Node.js
The README documents standalone installation with $skill-installer install create-react-native-library from callstackincubator/agent-skills. Alternatively, clone the repository and copy the skills tree into project-level .codex/skills/ or user-level ~/.codex/skills/; the provided README command copies the whole skills/ directory. Restart Codex to recognize newly installed skills.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/callstackincubator/agent-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/create-react-native-library" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- A brief description of the library
For a new library that may be published to npm, ask the assistant to use skills/create-react-native-library/SKILL.md and run: npx create-react-native-library@latest awesome-library --no-interactive --yes --description "A brief description of the library" --type turbo-module --languages kotlin-objc --example expo. For a local module, change into the existing app directory and add --local.
What are this skill's strengths and limitations?
- Covers both standalone library scaffolding and local libraries inside existing apps.
- Provides copyable npx commands with concrete scaffold options.
- Clearly addresses JavaScript libraries, native modules, and native UI components.
- The repository is MIT-licensed and supplies follow-up references for standalone and local-library flows.
- The supplied material does not show a test suite, platform compatibility matrix, or failure-analysis results.
- The SKILL.md summarizes linked reference files but does not include their detailed contents.
- Using npx and create-react-native-library requires Node.js and a shell environment.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| React Native Library Builder this page | 50 · Use with care | ★ 1.7k | 18d ago | MIT |
| React Native Performance Playbook | 51 · Use with care | ★ 1.7k | 18d ago | MIT |
| React Native Performance Guide | 60 · Recommended | ★ 1.7k | 18d ago | MIT |
| Vibeyard: Add npm Dependency Skill | 55 · Use with care | ★ 1.4k | 1mo ago | MIT |
| Expo Integration Examples | 51 · Use with care | ★ 2.9k | 21d ago | MIT |
How did FollowSkills review this skill?
The instructions mainly perform scaffolding, dependency installation, pod installation, prebuild, and example-app execution. No malware, credential theft, covert exfiltration, or other red-line behavior is evident, and some dependency relationships are disclosed. However, default use of npx @latest, --yes, and non-interactive execution lacks stepwise confirmation, permission scoping, data-flow disclosure, rollback, and recovery guidance, so points are deducted.
The workflow separates standalone and local-library paths, gives mostly coherent type/language mappings, and asks the agent to inspect current CLI help first. It provides no executable test suite, version pinning, abnormal-input handling, or diagnostic failure feedback. The standalone path also says to use only Yarn while the local path supports npm, so consistency is incomplete and the static score is limited.
Audience, trigger scenarios, and Turbo/Fabric/Nitro/JS selection guidance are reasonably clear, covering both standalone libraries and modules in existing apps. Non-fit boundaries, compatibility ranges, mainland-China network reachability, and Chinese-language support are not addressed. The workflow also depends on external tooling such as npx, npm, Expo, and CocoaPods, so points are deducted.
The documentation has useful progressive structure through an overview, quick reference, reference files, problem mapping, prerequisites, examples, pitfalls, MIT licensing, and author metadata. It lacks skill-specific versioning, changelog, explicit maintenance ownership, update path, FAQ coverage, and systematic troubleshooting, so it does not receive full marks.
The commands, type/language mappings, generated layout, and follow-up build steps are directly actionable for the core scaffolding task. There is no in-file execution evidence, successful output, or key-path verification, and version drift and environment differences may leave users to perform additional debugging, so points are deducted.
The skill links to Callstack, React Native, and Nitro documentation and provides concrete commands and expected structure, giving it some auditability. This review is static only; there is no committed test suite, CI coverage, or third-party execution evidence for the selected skill, so reproducibility remains limited and points are deducted.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →