Agent skill

Mobile QA Release

by suntay44 in suntay44/web-to-mobile-magic-plugin

Verify a web-to-mobile implementation before completion. An agent skill from suntay44/web-to-mobile-magic-plugin.

MITAuto-check passedMobile

Install Mobile QA Release

skills CLI
$ npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-qa-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install suntay44/web-to-mobile-magic-plugin mobile-qa-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/suntay44/web-to-mobile-magic-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mobile-qa-release .claude/skills/mobile-qa-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-qa-release
GitHub stars
108
Token cost
~843 tokens
SKILL.md length
419 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Verify a web-to-mobile implementation before completion. An agent skill from suntay44/web-to-mobile-magic-plugin.

  • Tasks that involve Cross-platform mobile apps
  • SKILL.md covers Verification Rules, Plan Updates and Release Readiness
  • Calls npx
  • Tasks that involve Linting and formatting

What it does

Mobile QA Release is an agent skill from suntay44/web-to-mobile-magic-plugin. Verify a web-to-mobile implementation before completion. Use after build work to run lint, typecheck, tests, Expo smoke checks, device checks, update the checklist, and document risks.

Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Cross-platform mobile apps and Linting and formatting. It works with Expo. The repository describes itself as: Website to React Native mobile app Plugin. Audit, Plan, QA scan, and deep review. Plan-first, approval-gated and Token Efficient. The licence is MIT.

When your agent uses it

  • Tasks that involve Cross-platform mobile apps
  • Tasks that involve Linting and formatting

Example prompts

  • “/mobile-qa-release”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit e6eb780. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile QA Release loads about 843 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 419 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~843

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from suntay44/web-to-mobile-magic-plugin at commit e6eb780, republished under its MIT licence (© suntay44). 419 words, ~843 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-qa-release/SKILL.md (or your agent's skills folder).
name
mobile-qa-release
description
Verify a web-to-mobile implementation before completion. Use after build work to run lint, typecheck, tests, Expo smoke checks, device checks, update the checklist, and document risks.
license
MIT

Mobile QA Release

Verify before claiming the mobile migration is complete.

Verification Rules

Do not claim completion without fresh evidence. Paste each command, its exit code, and key output beneath the check — no ✅ without proof (see ../mobile-migration-plan/references/output-contracts.md). Work from the approved Markdown plan (under docs/web-to-mobile/ or docs/mobile-resume/ depending on the workflow) and the implementation changes. If no plan file exists, proceed with generic checks, note the absence in the report, and skip checklist update steps.

Run relevant checks from the plan and repo, such as:

  • Dependency install or resolution.
  • Lint.
  • Typecheck.
  • Unit tests.
  • Integration or component tests.
  • Expo start, export, build, or prebuild smoke check.
  • iOS simulator, Android emulator, browser preview, or physical-device smoke test when available.
  • Manual checks for navigation, auth, forms, API calls, storage, media, permissions, loading states, and error states.

Performance:

  • Run npx expo-doctor, npx expo install --check, and npx expo export for Expo projects. Compare per-platform JavaScript/assets against the project's recorded baseline or budget; if none exists, record a baseline without inventing a universal threshold.
  • Observe cold-start time on simulator or device; note if sluggish.
  • Spot-check scroll and transition FPS on list screens; note jank.
  • Confirm images are appropriately sized and not loading full-resolution web assets.

Accessibility:

  • Confirm every interactive element has an accessible name. Native text children may already provide one; add accessibilityLabel when the visible content does not describe the action (for example, icon-only controls).
  • Confirm text respects system font scaling (no fixed-height containers that clip scaled text).
  • Confirm accessibilityRole is set on custom interactive components.
  • Note any color-only information that may fail contrast requirements.

Responsive Layout:

  • Spot-check core screens at 375px width (small phone) and 430px width (large phone).
  • Confirm portrait and landscape orientations do not break layout on core screens.

If a check cannot be run, state why and record the risk in the plan.

Show full SKILL.md (116 more words)Show less

Plan Updates

Before final response:

  • Mark completed verification checklist items with - [x].
  • Leave incomplete items unchecked.
  • Add a "Verification Notes" section if the plan does not already have one.
  • Record commands run, pass/fail status, and remaining risks.

Release Readiness

Confirm or document:

  • All mapped web routes have mobile destinations or explicit deferrals.
  • Auth/session behavior works or has a documented blocker.
  • API calls work or have documented failures.
  • Native permissions are configured or deferred.
  • App can start/build in the available environment.
  • Performance and accessibility checks passed or risks are documented.
  • Parity review completed or deferred items documented (web-to-mobile flow only).
  • Remaining manual QA and store-release tasks are listed.

Only then provide a concise completion summary with evidence.

© suntay44, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/mobile-qa-release of suntay44/web-to-mobile-magic-plugin.

Open the folder on GitHubat commit e6eb780

Compare with similar skills

Mobile QA Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile QA Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile QA Release this skillsuntay44/web-to-mobile-magic-plugin108—~843Automated safety check: PassMIT
React Native Best Practicesvercel-labs/openreview1.7k17 repos~1.1kAutomated safety check: PassMIT
ThemingCode-with-Beto/skills140—~2.5kAutomated safety check: PassNone
Expo Playground Patternsbpinheiroms/dotfiles108—~9.3kAutomated safety check: PassNone
UniwindCherryHQ/cherry-studio-app4k—~20kAutomated safety check: WarnAGPL-3.0
React Native Experttech-leads-club/agent-skills7k—~3.2kAutomated safety check: PassCC-BY-4.0

Similar skills

  • React Native Best Practices

    vercel-labs/openreview

    Official

    A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.

    1.7k GitHub starsUsed in 17 repos~1.1k tokens
    MobileAuto-check passed
  • Theming

    Code-with-Beto/skills

    Scaffold a unified, cross-platform color theme system into an Expo Router app.

    140 GitHub stars~2.5k tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Expo Playground Patterns

    bpinheiroms/dotfiles

    Comprehensive UI/animation patterns reference from expo-playground.

    108 GitHub stars~9.3k tokensUpdated 4 mo ago
    MobileAuto-check passed
  • Uniwind

    CherryHQ/cherry-studio-app

    Uniwind — Tailwind CSS v4 styling for React Native. An agent skill from CherryHQ/cherry-studio-app.

    4k GitHub stars~20k tokensUpdated today
    MobileAuto-check: warnings
  • React Native Expert

    tech-leads-club/agent-skills

    Guides React Native and Expo work for cross-platform apps: Expo Router navigation, fast lists, Reanimated animation, platform-specific code and project structure.

    7k GitHub stars~3.2k tokensUpdated yesterday
    MobileAuto-check passed
  • Official

    Folder structure for a new Expo app. An agent skill from expo/skills.

    2.7k GitHub starsUsed in 2 repos~1.5k tokens
    MobileAuto-check passed

More from suntay44/web-to-mobile-magic-plugin

All 11 skills in this repo
  • Mobile App Audit

    suntay44/web-to-mobile-magic-plugin

    Audit an existing unfinished Expo React Native or Swift mobile app.

    108 GitHub stars~871 tokensUpdated 26 days ago
    Auto-check passed
  • Web To Mobile

    suntay44/web-to-mobile-magic-plugin

    Orchestrate website or web app conversion into a mobile app.

    108 GitHub stars~781 tokensUpdated 26 days ago
    Auto-check passed
  • Web To Mobile Audit

    suntay44/web-to-mobile-magic-plugin

    Audit a website, GitHub repo, local folder, or workspace before web-to-mobile work.

    108 GitHub stars~811 tokensUpdated 26 days ago
    Auto-check passed
  • Mobile Deep Review

    suntay44/web-to-mobile-magic-plugin

    Senior-level deep review of an existing mobile app. An agent skill from suntay44/web-to-mobile-magic-plugin.

    108 GitHub stars~692 tokensUpdated 26 days ago
    Auto-check passed
  • Mobile QA Scan

    suntay44/web-to-mobile-magic-plugin

    QA scan of an existing mobile app. An agent skill from suntay44/web-to-mobile-magic-plugin.

    108 GitHub stars~793 tokensUpdated 26 days ago
    Auto-check passed
  • Mobile Migration Plan

    suntay44/web-to-mobile-magic-plugin

    Create an approval-gated web-to-mobile plan with a route map, stack verdict, reuse/rewrite split, checklist, tests, and acceptance criteria.

    108 GitHub stars~712 tokensUpdated 26 days ago
    Auto-check passed

Works with

Categories

Questions about Mobile QA Release

What does Mobile QA Release do?

Verify a web-to-mobile implementation before completion. An agent skill from suntay44/web-to-mobile-magic-plugin. Mobile QA Release is an agent skill from suntay44/web-to-mobile-magic-plugin. Verify a web-to-mobile implementation before completion.

When should I use Mobile QA Release?

Mobile QA Release fits situations like: tasks that involve Cross-platform mobile apps; tasks that involve Linting and formatting.

How do I install Mobile QA Release in Claude Code?

Run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-qa-release -a claude-code`. Or copy the skill folder (skills/mobile-qa-release in suntay44/web-to-mobile-magic-plugin) into .claude/skills/mobile-qa-release in your project. Claude Code loads it when a task matches its description.

How do I install Mobile QA Release in Codex?

Run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-qa-release -a codex`. Or copy the skill folder (skills/mobile-qa-release in suntay44/web-to-mobile-magic-plugin) into .agents/skills/mobile-qa-release in your project. Codex loads it when a task matches its description.

Can I use Mobile QA Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add suntay44/web-to-mobile-magic-plugin --skill mobile-qa-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-qa-release, .gemini/skills/mobile-qa-release, .github/skills/mobile-qa-release and .opencode/skills/mobile-qa-release in your project.

What does Mobile QA Release need to run?

Going by SKILL.md and its folder, Mobile QA Release needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Mobile QA Release access the network?

SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Mobile QA Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mobile QA Release use?

Mobile QA Release is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile QA Release use?

About 843 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Mobile QA Release?

Skills that share tags, products or a category with Mobile QA Release: React Native Best Practices (vercel-labs/openreview, 1.7k stars), Theming (Code-with-Beto/skills, 140 stars), Expo Playground Patterns (bpinheiroms/dotfiles, 108 stars) and Uniwind (CherryHQ/cherry-studio-app, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile QA Release?

suntay44 (a GitHub user) maintains it in suntay44/web-to-mobile-magic-plugin, which has 108 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 13, 2026.

Source: suntay44/web-to-mobile-magic-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.