rn-native-features
Implement Expo Native Features
Expo apps often need native device features with careful permissions and platform handling. This skill provides focused patterns for adding camera, notifications, haptics, location, storage, app state, and keyboard behavior.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "rn-native-features" from https://skillstore.io/skills/cjharmath-rn-native-features.md and its manifest at https://skillstore.io/api/skills/cjharmath-rn-native-features/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "rn-native-features". Add camera support to my profile screen.
Expected outcome:
- Permission request flow before rendering the camera.
- Fallback copy for denied camera access.
- Photo capture approach with quality and metadata choices.
Using "rn-native-features". Prepare Expo push notifications for a beta release.
Expected outcome:
- Physical device requirement checklist.
- Client token registration plan.
- Foreground notification and tap-response handling steps.
- Backend sending responsibilities and token safety notes.
Using "rn-native-features". Choose storage for preferences and auth tokens.
Expected outcome:
- AsyncStorage recommendation for non-sensitive preferences.
- SecureStore recommendation for tokens and credentials.
- Warning about SecureStore size limits.
Security Audit
SafeThe static command findings are false positives caused by Markdown code fences in SKILL.md, not Ruby or shell execution. The hardcoded URL is the official Expo Push API endpoint in a backend notification example. The blocker finding is a keyboard layout comment, and no prompt injection or malicious intent was found.
Risk Factors
⚙️ External commands (30)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cjharmath-rn-native-features/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cjharmath-rn-native-features?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cjharmath-rn-native-features?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cjharmath-rn-native-features/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cjharmath-rn-native-features.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
CJHarmath. (2026). rn-native-features security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cjharmath-rn-native-features/audits/8BibTeX citation
@techreport{cjharmath-cjharmath-rn-native-features-2026,
author = {CJHarmath},
title = {rn-native-features security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cjharmath-rn-native-features/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "rn-native-features security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CJHarmath"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cjharmath-rn-native-features/audits/8"
identifiers:
- type: other
value: "skillstore:cjharmath-rn-native-features:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Permission-first camera flow
Add camera capture or gallery selection while handling granted, denied, and not-yet-requested states.
Push notification rollout
Plan Expo push token registration, local reminders, foreground behavior, tap handling, and backend sending.
Native capability review
Check location, haptics, secure storage, app lifecycle, and keyboard patterns before implementation.
Try These Prompts
Use rn-native-features to add camera permission handling for an Expo React Native screen. Explain the states before showing code.
Use rn-native-features to design an Expo image capture and gallery selection flow. Include permission handling, editing options, and user feedback.
Use rn-native-features to implement push notification registration, foreground handling, tap responses, and a secure backend sending plan for Expo.
Use rn-native-features to review my Expo native feature plan for permission gaps, device-only constraints, storage choices, and testing steps.
Best Practices
- Request and check permissions before rendering native controls.
- Test camera, haptics, location, and notifications on physical devices.
- Use SecureStore for tokens and AsyncStorage only for non-sensitive preferences.
Avoid
- Skipping denied-permission states and showing a blank native feature screen.
- Treating push notification payload routes as trusted without validation.
- Using SecureStore for large documents or general cache data.