用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/rdmptv/AdbAutoPlayer --skill adb-bypass命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | adb-bypass |
| description | PlayIntegrityFork bypass verification and validation for Play Integrity spoofing detection |
| version | 1.0.0 |
| modularized | true |
| scripts_enabled | true |
| tier | 2 |
| category | adb-automation |
| last_updated | "2025-12-02T00:00:00.000Z" |
| compliance_score | 100 |
| dependencies | ["uiautomator2>=3.0.0","pyyaml>=6.0","click>=8.1.7"] |
| auto_trigger_keywords | ["bypass","playintegrity","verification","validation","spoofing-detection"] |
| scripts | [{"name":"preflight-validation.py","purpose":"Pre-flight checks for bypass prerequisites and configuration","type":"python","command":"uv run .claude/skills/adb-bypass/scripts/preflight-validation.py","zero_context":false,"version":"1.0.0","last_updated":"2025-12-02T00:00:00.000Z"}] |
| color | purple |
PlayIntegrityFork Bypass Verification and Validation
What It Does: Verifies PlayIntegrityFork installation status, validates bypass effectiveness, and checks device integrity spoofing detection. Used after Magisk module installation to confirm Play Integrity bypass is working.
Core Capabilities:
When to Use:
Pre-flight checks for bypass prerequisites and configuration.
# Basic validation
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py
# Specify device
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py --device 127.0.0.1:5555
# Detailed check (verbose output)
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py \
--device 127.0.0.1:5555 \
--detailed
# Check specific component
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py \
--check magisk \
--check playintegrity \
--check zygisk
# JSON output
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py --json
Features:
This skill includes TOON-based workflow definitions for automation.
TOON (Task-Oriented Orchestration Notation) is a structured workflow definition language that pairs with Markdown documentation. Each workflow consists of:
This TOON+MD pairing approach is inspired by the BMAD METHOD pattern, adapted to use TOON instead of YAML for better orchestration support.
Workflow files are located in workflow/ directory:
Example Workflows (adb-bypass):
workflow/bypass-validation.toon - Verify PlayIntegrityFork installation and bypass statusworkflow/detection-check.toon - Check if app detects the bypassworkflow/integrity-verification.toon - Validate device signature spoofingExecute any workflow using the ADB workflow orchestrator:
uv run .claude/skills/adb-workflow-orchestrator/scripts/adb-run-workflow.py \
--workflow .claude/skills/adb-bypass/workflow/bypass-validation.toon \
--param device="127.0.0.1:5555"
Each workflow includes comprehensive documentation in the corresponding .md file:
See the workflow/ directory for complete TOON file definitions and documentation.
To create custom workflows for this skill:
.toon file in the workflow/ directory.md file with comprehensive documentationFor more information, refer to the TOON specification and the workflow orchestrator documentation.
# Run comprehensive pre-flight checks
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py \
--device 127.0.0.1:5555 \
--detailed
# Check returns detailed status:
# - Magisk: installed, version, root status
# - PlayIntegrityFork: installed, version, enabled
# - Zygisk: enabled, subsystem status
# - Device: integrity signature, spoofing status
# Complete validation workflow
uv run .claude/skills/adb-workflow-orchestrator/scripts/adb-run-workflow.py \
--workflow .claude/skills/adb-bypass/workflow/bypass-validation.toon \
--param device=127.0.0.1:5555 \
--verbose
# 1. Validate bypass is active
uv run .claude/skills/adb-bypass/scripts/preflight-validation.py \
--device 127.0.0.1:5555
# 2. If validation passes, run app tests
if [ $? -eq 0 ]; then
uv run .claude/skills/adb-karrot/scripts/adb-karrot-test-login.py \
--device 127.0.0.1:5555
fi
Depends On:
adb command-line toolUsed By:
adb-karrot (for bypass validation before app testing)adb-magisk (for post-installation verification)Complements:
adb-magisk (installs PlayIntegrityFork module)adb-karrot (tests apps after bypass activation)adb-workflow-orchestrator (orchestrates validation flows)What is PlayIntegrityFork? PlayIntegrityFork is a Magisk module that hooks into Android's Play Integrity API to spoof device integrity and prevent detection of running on emulators or rooted devices.
How It Works:
Google Play Integrity API
├─ deviceIntegrity() check
├─ serverIntegrity() check
└─ Error handling
PlayIntegrityFork Hook (via Zygisk)
└─ Intercepts integrity requests
└─ Returns spoofed device signature
└─ App receives valid integrity response
Prerequisites:
Validation Checks:
# Check Magisk modules
uv run .claude/skills/adb-magisk/scripts/adb-magisk-launch.py \
--device 127.0.0.1:5555 \
--wait-text "PlayIntegrityFork"
# Solution: Ensure Zygisk is enabled and device rebooted
# Enable Zygisk
uv run .claude/skills/adb-magisk/scripts/adb-magisk-enable-zygisk.py \
--device 127.0.0.1:5555 \
--auto-reboot
# Check logcat for errors
adb logcat | grep -i "integrity\|playintegrity"
# Common issues:
# - Module needs reboot to activate
# - Zygisk disabled or not loaded
# - Incompatible module version
Design Principles:
Validation Sequence:
1. Magisk Root Verification
└─ Check root access, version
2. Module Installation Check
└─ PlayIntegrityFork installed?
3. Zygisk Verification
└─ Subsystem enabled and loaded?
4. Device Signature Check
└─ Integrity spoofing active?
5. Status Reporting
└─ Return detailed validation results
Version: 1.0.0 Status: ✅ Validation/Verification Tier Scripts: 1 (comprehensive pre-flight) Workflows: 3 (validation, detection, integrity) Last Updated: 2025-12-02 Tier: 2 (Foundation)