Index of every page on this site: llms.txt
All skills
neha avatar

/security

@eb9f097
Run it yourself

Review React Native code for secret handling, secure storage, transport security, PII in logs, deep-link validation, input validation, and privacy compliance. Use when handling auth, payments, personal data, or before a security review.

  • 1 file
  • 3.7 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/neha/rn-developer-skills/security

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈62 tokens for metadata: the name and description. ≈836 when used: this file.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈247 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Security Skill

Applicability

  • Platforms: iOS and Android
  • React Native: 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)

When to Use

  • Handling authentication, tokens, or payments
  • Storing or transmitting personal or sensitive data
  • Adding or reviewing deep links
  • Preparing for a security or privacy review

Severity

  • Merge-blocking: a secret or token in the client bundle, payment credentials stored on the device, or a link target this diff adds that is not an allowed route.
  • Should-fix: pinning, retention copy, and SDK log review.

Guidance

Secrets & Storage

A secret does not belong in the client. Environment variables in React Native are compiled into the JavaScript bundle.

  • No private keys, tokens, or shared secrets in source, native projects, or env values that ship in the bundle
  • A public host or a publishable key may come from an env var
  • Sensitive data stored in the Keychain (iOS) / Keystore (Android), not plain storage
  • Payment credentials never stored locally (PCI)

Incorrect:

const apiSecret = process.env.API_SECRET;

Correct:

const apiHost = process.env.API_HOST;

Transport

  • Pin transport for payments or auth only when the threat model requires it, and document how the pin rotates. Do not pin local debug builds
  • Client-side validation is never trusted alone — the server validates too

Logging & PII

  • No PII (names, emails, payment info) logged to console or crash reports
  • Third-party SDK log output audited (SDKs may log sensitive data internally)

Incorrect:

console.log('Payment response:', JSON.stringify(paymentResult));
// Logs a card token to console; ends up in crash reports

Correct:

logger.info('Payment completed', {
  transactionId: paymentResult.id,
  status: paymentResult.status,
});
// Only non-sensitive identifiers

Deep Links & Input

Missing route params that crash are owned by architecture. This skill checks the target.

  • The link target is one of the routes the app allows (prevent open redirect)
  • Input validated on the client (in addition to, not instead of, the server)

Auth Lifecycle

Startup order and the navigation reset on sign-out are owned by architecture.

  • Token refresh handled silently on 401, without losing form state
  • Sign-out deletes the session token from secure storage

Privacy & Compliance

Permission prompt timing is owned by native-integration.

  • No analytics or device-data collection before user consent (ATT on iOS, GDPR)
  • The product has a path for export and deletion; this screen does not have to invent one unless the diff is that path
  • User data not retained beyond the retention policy

Pitfalls

  • Crash and analytics tools often capture console.log by default — disable or filter them so PII does not leak.
  • Third-party SDKs may log sensitive payloads internally; verify their output, not just your own.
  • Client validation is a UX nicety, not a security control — the server is the source of truth.
  • An unvalidated deep link can redirect users into unintended or authenticated content; validate params first.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at eb9f097. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
version
1.2.0
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "security",
  "privacy",
  "compliance"
]

README badge

README badge for neha/rn-developer-skills/security