SkillsAdd

revylai/revyl-cli · Archived

revyl-mcp-analyze

Analyze failed Revyl MCP test executions and classify them as real bugs, flaky tests, infra issues, or test-design improvements.

First seen May 15, 2026

Installation

$ npx skills add revylai/revyl-cli --skill revyl-mcp-analyze
View on skills.sh ↗ GitHub repository ↗

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

revyl-cli-auth-bypass-react-native Same source · more installs
revylai/revyl-cli

React Native bare leaf recipe for test-only auth bypass deep links using Revyl launch variables.

4 installs
revyl-cli-auth-bypass-expo Same source · more installs
revylai/revyl-cli

Expo and Expo Router leaf recipe for test-only auth bypass deep links using Revyl launch variab…

4 installs
revyl-cli-dev-loop Same source · more installs
revylai/revyl-cli

Generic CLI-first Revyl dev loop for hot reload, rebuild-loop, and device exploration.

4 installs
revyl-cli-create Same source · more installs
revylai/revyl-cli

Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessio…

4 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
terraform-azurerm-set-diff-analyzer Similar name
github/awesome-copilot

Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive d…

8.9K installs
analyze Similar name
anthropics/knowledge-work-plugins

Answer data questions -- from quick lookups to full analyses. Use when looking up a single metr…

5.3K installs

Also in this package

Other skills from revylai/revyl-cli · top by installs.

npx skills add revylai/revyl-cli
revyl-cli-auth-bypass-react-native 4 revyl-cli-auth-bypass-expo 4 revyl-cli-dev-loop 4 revyl-cli-create 4 revyl-cli-auth-bypass 4 revyl-cli-auth-bypass-ios 3 revyl-cli-auth-bypass-android 3 revyl-cli-auth-bypass-flutter 3 revyl-mcp 3 revyl-mcp-dev-loop 3

Browse all from revylai/revyl-cli

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 510
License MIT
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,120 B
  • docs SUMMARY.md 153 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Revyl MCP Analyze Skill

Evidence Flow

  1. Start from task ID after run_test.
  2. Pull status payload:

- getteststatus(task_id="...")

  1. Inspect failed step expectations and observed reasoning.
  2. Classify:

- REAL BUG - FLAKY TEST - INFRA ISSUE - TEST IMPROVEMENT

  1. Recommend exact next tool/action.

Classification Rules

  • REAL BUG: actions complete but app behavior contradicts expected outcome.
  • FLAKY TEST: app behavior is acceptable but validation is too brittle.
  • INFRA ISSUE: no meaningful app steps executed or setup/device/build failure.
  • TEST IMPROVEMENT: test structure is weak or allows ambiguity.

Required Output

Task: <task-id>
Classification: <REAL BUG | FLAKY TEST | INFRA ISSUE | TEST IMPROVEMENT>
Confidence: <HIGH | MEDIUM | LOW>
Evidence:
- Expected: <summary>
- Observed: <summary>
- Why: <short rationale>
Next action:
- <specific update_test / rerun / bug filing action>