Skip to content
Back to skills

Metamask Official Check Nesting

ASecurity

Audit a React Native component for unnecessary wrapper nesting and suggest flattening opportunities. Also flags non-interactive containers missing accessible={false}. Use when reviewing or generating components to reduce native view depth and accessibility node count.

  • 76 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
designreactnodegitperformance

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add jiayaoqijia/cryptoskill --skill metamask-official-check-nesting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Metamask Official Check Nesting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Metamask Official Check Nesting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jiayaoqijia-metamask-official-check-nesting/badge)](https://www.skillsdirectory.com/skills/jiayaoqijia-metamask-official-check-nesting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: check-nesting
description: Audit a React Native component for unnecessary wrapper nesting and suggest flattening opportunities. Also flags non-interactive containers missing accessible={false}. Use when reviewing or generating components to reduce native view depth and accessibility node count.
---

## When To Use

- Reviewing or authoring a React Native component and suspecting unnecessary layout wrappers
- Reducing native view depth to improve rendering performance
- Flagging non-interactive containers that are missing `accessible={false}` to lower accessibility node count
- Running a broad audit across a folder or the entire project

## Workflow

See the repo overlay for the full step-by-step playbook (locate files → identify patterns A–F → format findings → ask before fixing → verify tests → open PR → risk report). At a high level:

1. Locate the target file(s) based on user input (path, component name, folder, `--all`, or git diff)
2. Identify removable wrappers (Patterns A–E) and accessibility gaps (Pattern F)
3. Report findings grouped by file with a summary table
4. Ask the user whether to fix all, fix one by one, or just report
5. If fixing: apply edits, run tests per file, then open a PR if requested

Files in this skill

  • LICENSE1 KB
  • SKILL.md1.2 KB
  • SOURCE.md368 B
  • TRUST.auto.yaml2.2 KB
  • repos/metamask-mobile.md15.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…