rn-observability
Improve React Native Observability
Silent failures and weak error messages make mobile bugs hard to diagnose. This skill gives practical React Native patterns for logs, errors, tracing, and safe reporting.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "rn-observability" from https://skillstore.io/skills/cjharmath-rn-observability.md and its manifest at https://skillstore.io/api/skills/cjharmath-rn-observability/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-observability". A save flow returns early when a retake area is missing.
Expected outcome:
The response identifies the silent return, recommends a warning log, and includes only safe identifiers and counts for diagnosis.
Using "rn-observability". A production crash report says only that no answers were found.
Expected outcome:
- The response proposes a clearer message with function location and state counts.
- It explains which values are safe to include and which values should be redacted.
- It suggests a likely timing or state synchronization cause to investigate.
Using "rn-observability". An async assessment flow fails without showing the failed step.
Expected outcome:
The response recommends a flow identifier, step logs, state snapshots, and a single error capture point.
Security Audit
SafeAll static findings were adjudicated as false positives. The external command alerts are Markdown code fences or TypeScript template literals, and the sensitive-file alerts are object key counts or redaction helper examples rather than certificate or key file access. No prompt injection or malicious intent was found in SKILL.md.
Risk Factors
⚙️ External commands (48)
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-observability/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cjharmath-rn-observability?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cjharmath-rn-observability?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cjharmath-rn-observability/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cjharmath-rn-observability.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-observability security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cjharmath-rn-observability/audits/7BibTeX citation
@techreport{cjharmath-cjharmath-rn-observability-2026,
author = {CJHarmath},
title = {rn-observability security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/cjharmath-rn-observability/audits/7},
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-observability security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "CJHarmath"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cjharmath-rn-observability/audits/7"
identifiers:
- type: other
value: "skillstore:cjharmath-rn-observability:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add Feature Logging
Add clear log events to a React Native feature without exposing sensitive values.
Debug Production Failures
Design error messages and flow traces that show where a mobile workflow failed.
Standardize Observability Patterns
Create team guidance for logging levels, assertions, redaction, and crash reporting context.
Try These Prompts
Review this React Native function and suggest where to add logs for early returns. Include the reason and minimal safe context for each log.
Rewrite these React Native error messages so they include location, failed condition, relevant state counts, and a likely cause. Avoid sensitive values.
Design observability for this async React Native workflow. Add flow identifiers, step-level logs, state snapshots, and error reporting boundaries.
Audit this React Native observability plan for production. Check log levels, redaction, crash reporting context, temporary debug logs, and missing failure paths.
Best Practices
- Log the reason for every early return with minimal diagnostic context.
- Redact secrets and personal data before logs or crash reports leave the device.
- Use flow identifiers for multi-step async operations that may fail in production.
Avoid
- Logging full answer objects, tokens, or personal values in production.
- Catching errors without logging or rethrowing enough diagnostic context.
- Leaving temporary debug logging enabled in release builds.