How do I install the Rn Self Feedback skill?

Run npx skillmds@latest add tomevault-io/rn-self-feedback in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rn Self Feedback safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rn Self Feedback?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rn Self Feedback free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rn Self Feedback?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rn Self Feedback by tomevault-io — Agent Skill

Name: Rn Self Feedback
Author: tomevault-io

Rn Self Feedback

Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results). Use when this capability is needed.

tomevault-io 848d96e 2 files · 2.9 KB Updated Sep 17, 2026

File contents

RN Self-Feedback (Maestro + Tauri MCP)

When you change React Native or Inspector code and need to verify behavior, use Maestro MCP and Tauri MCP to run the app, run flows, and capture state—then evaluate the results yourself.

When to use

After changing packages/react-native-inspector or related RN/Inspector code.
When the user or context implies "verify this" or "check if it works" for RN.
When you want to give yourself feedback on whether a change behaves correctly.

Prerequisites

MCP setup: MCP is configured so the tauri and maestro servers use the correct mise path. If this repo provides it, run bun run setup-mcp once per machine.
Tauri MCP: Inspector (Tauri) app running in debug (bun run dev:inspector:tauri) so Tauri MCP can connect.
Maestro MCP: Maestro available via mise (.mise.toml); Maestro MCP enabled in Cursor.

Workflow

Run / drive the RN app
- Use Maestro MCP to run flows or start the app as needed (e.g. maestro run ... or equivalent MCP tools). Check available Maestro MCP tools for run, tap, assert, etc.
Capture Inspector / UI state
- Use Tauri MCP to take a screenshot of the Inspector (e.g. "Take a screenshot of my app") or to interact (click, type) if needed.
Evaluate
- From the screenshot or flow result, decide: does the change work as intended? Note any failures or UI mismatches and suggest fixes.

Notes

MCP tools are provided by the configured maestro and tauri servers in your MCP configuration. Call them when you need to run or inspect the RN/Inspector stack.
If Tauri MCP cannot connect, confirm Inspector is running with bun run dev:inspector:tauri (debug build).
If Maestro MCP fails, ensure MCP is configured (e.g. run bun run setup-mcp if available) and Maestro is installed via mise.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: rn-self-feedbackdescription: Use Maestro MCP and Tauri MCP to run React Native flows and capture Inspector state for self-validation. Use when working on RN/Inspector code and you need to verify changes (run app, run Maestro flows, capture screenshots, then evaluate results). Use when this capability is needed.---# RN Self-Feedback (Maestro + Tauri MCP)When you change React Native or Inspector code and need to verify behavior, use Maestro MCP and Tauri MCP to run the app, run flows, and capture state—then evaluate the results yourself.## When to use- After changing `packages/react-native-inspector` or related RN/Inspector code.- When the user or context implies "verify this" or "check if it works" for RN.- When you want to give yourself feedback on whether a change behaves correctly.## Prerequisites- **MCP setup**: MCP is configured so the `tauri` and `maestro` servers use the correct `mise` path. If this repo provides it, run `bun run setup-mcp` once per machine.- **Tauri MCP**: Inspector (Tauri) app running in debug (`bun run dev:inspector:tauri`) so Tauri MCP can connect.- **Maestro MCP**: Maestro available via mise (`.mise.toml`); Maestro MCP enabled in Cursor.## Workflow1. **Run / drive the RN app** - Use Maestro MCP to run flows or start the app as needed (e.g. `maestro run ...` or equivalent MCP tools). Check available Maestro MCP tools for run, tap, assert, etc.2. **Capture Inspector / UI state** - Use Tauri MCP to take a screenshot of the Inspector (e.g. "Take a screenshot of my app") or to interact (click, type) if needed.3. **Evaluate** - From the screenshot or flow result, decide: does the change work as intended? Note any failures or UI mismatches and suggest fixes.## Notes- MCP tools are provided by the configured `maestro` and `tauri` servers in your MCP configuration. Call them when you need to run or inspect the RN/Inspector stack.- If Tauri MCP cannot connect, confirm Inspector is running with `bun run dev:inspector:tauri` (debug build).- If Maestro MCP fails, ensure MCP is configured (e.g. run `bun run setup-mcp` if available) and Maestro is installed via mise.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/ohah) — claim your Tome and manage your conversions.

Frequently asked questions