Token导航 LogoToken导航

Agent Skill · 研究检索

senior-mobile(高级手机)

senior-mobile 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

senior-mobile 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 49,494。

总安装 649周安装 26GitHub Stars 公开资料未说明下载 210核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:senior-mobile(高级手机)
来源仓库:https://github.com/rickydwilson-dcs/claude-skills
仓库路径:skills/senior-mobile
安装命令:
npx skills add rickydwilson-dcs/claude-skills --skill "senior-mobile"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add rickydwilson-dcs/claude-skills --skill "senior-mobile"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

高级手机用于查找、检索和筛选相关信息,辅助快速定位候选结果。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景使用。发现并安装 AI 代理的技能,提升工具集成能力。

安装命令:npx skills add rickydwilson-dcs/claude-skills --skill "senior-mobile"。建议确认权限范围和维护状态,避免触发联网或命令执行。

来源仓库内路径:skills/senior-mobile

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add rickydwilson-dcs/claude-skills --skill "senior-mobile";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

senior-mobile 怎么安装?

在终端执行 npx skills add rickydwilson-dcs/claude-skills --skill "senior-mobile"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

senior-mobile 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

senior-mobile 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

senior-mobile 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

senior-mobile 用的人多吗?

公开数据是累计安装 649 次,近一周安装 26 次,下载 210 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

senior-mobile 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
senior-mobile

高级手机 · 本页

649—接触敏感数据MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
senior-mobile
title
Senior Mobile Skill Package
description
Comprehensive cross-platform mobile development skill for React Native, Flutter, and Expo. Includes project scaffolding, platform detection, app store validation, and CI/CD setup. Use when building mobile apps, selecting frameworks, validating releases, or setting up mobile development workflows.
domain
engineering
subdomain
mobile-development
difficulty
advanced
time-saved
60% faster project setup, 80% fewer store rejections
frequency
Weekly for active mobile development
use-cases
related-agents
related-skills
related-commands
[]
orchestrated-by
dependencies
scripts
references
assets
[]
compatibility
python-version
3.8+
platforms
[macos, linux, windows]
tech-stack
examples
title
Generate React Native Project
input
python3 mobile_scaffolder.py --framework react-native --platforms ios,android --navigation react-navigation --state redux
output
Complete project structure with TypeScript, navigation, state management, and CI/CD config
title
Detect Platform Capabilities
input
python3 platform_detector.py --check all --depth full
output
Detailed report of iOS/Android capabilities, signing status, and configuration
title
Validate for App Store
input
python3 app_store_validator.py --store apple --strict
output
Compliance report with required fixes for App Store submission
stats
downloads
0
stars
0
rating
0.0
reviews
0
version
v1.0.0
author
Claude Skills Team
contributors
[]
created
2025-12-13
updated
2025-12-13
license
MIT
tags
featured
true
verified
true

Senior Mobile

Comprehensive cross-platform mobile development skill package with Python automation tools for project scaffolding, platform detection, and app store validation.

Overview

This skill provides a complete toolkit for cross-platform mobile development targeting React Native, Flutter, and Expo frameworks. It includes three Python CLI tools that automate project setup, platform analysis, and app store validation, saving significant time and reducing store rejection rates.

Quick Start

# Generate a new React Native project
python3 scripts/mobile_scaffolder.py --framework react-native --platforms ios,android --output ./my-app

# Analyze an existing project
python3 scripts/platform_detector.py --check all --depth full

# Validate before App Store submission
python3 scripts/app_store_validator.py --store apple --strict

Core Capabilities

  • Project Scaffolding - Generate complete React Native, Flutter, or Expo projects with TypeScript, navigation, state management, and CI/CD
  • Platform Detection - Analyze mobile projects to detect framework type, iOS/Android capabilities, and configuration status
  • App Store Validation - Pre-submission checks for Apple App Store and Google Play Store compliance
  • Framework Selection - Data-driven framework comparison (React Native vs Flutter) based on project requirements

Key Workflows

Workflow 1: New Mobile Project Setup

Time: 15-30 minutes (vs 2-4 hours manual)

Steps:

  1. Determine project requirements (platforms, navigation, state management)
  2. Run mobile_scaffolder.py with appropriate options
  3. Review generated structure and customize as needed
  4. Initialize git repository and configure CI/CD
  5. Verify build for both platforms

Tool: scripts/mobile_scaffolder.py

# React Native with TypeScript, React Navigation, Redux
python3 scripts/mobile_scaffolder.py \
  --framework react-native \
  --platforms ios,android \
  --navigation react-navigation \
  --state redux \
  --ci github-actions \
  --output ./my-app

# Flutter with Riverpod and GoRouter
python3 scripts/mobile_scaffolder.py \
  --framework flutter \
  --platforms ios,android,web \
  --navigation go-router \
  --state riverpod \
  --ci github-actions \
  --output ./my-flutter-app

# Expo managed workflow
python3 scripts/mobile_scaffolder.py \
  --framework expo \
  --platforms ios,android \
  --navigation expo-router \
  --state zustand \
  --output ./my-expo-app

Workflow 2: Platform Capability Assessment

Time: 5-10 minutes

Steps:

  1. Navigate to mobile project root
  2. Run platform_detector.py with full depth
  3. Review iOS and Android capability reports
  4. Address any configuration issues identified
  5. Re-run to verify fixes

Tool: scripts/platform_detector.py

# Full project analysis
python3 scripts/platform_detector.py --check all --depth full

# iOS-only analysis
python3 scripts/platform_detector.py --check ios --output json

# Android signing verification
python3 scripts/platform_detector.py --check android --depth signing

Output includes:

  • Project type detection (React Native, Flutter, Expo, Native)
  • iOS: Bundle ID, provisioning profiles, entitlements, Info.plist analysis
  • Android: Package name, Gradle configuration, signing config, manifest permissions
  • Configuration health score with recommendations

Workflow 3: Pre-Release App Store Validation

Time: 10-15 minutes

Steps:

  1. Build release versions for target stores
  2. Run app_store_validator.py with strict mode
  3. Review compliance report
  4. Fix any critical or high-priority issues
  5. Re-validate until passing
  6. Submit to stores with confidence

Tool: scripts/app_store_validator.py

# Apple App Store validation
python3 scripts/app_store_validator.py \
  --store apple \
  --build-path ./ios/build/Release \
  --strict

# Google Play Store validation
python3 scripts/app_store_validator.py \
  --store google \
  --build-path ./android/app/build/outputs/apk/release \
  --strict

# Both stores (universal validation)
python3 scripts/app_store_validator.py \
  --store both \
  --check all \
  --output markdown > validation-report.md

Validates:

  • Apple: Info.plist completeness, privacy manifest, icon sizes, entitlements, minimum iOS version
  • Google: AndroidManifest.xml, target SDK version, 64-bit support, signing, permissions declarations

Workflow 4: Framework Selection Analysis

Time: 20-30 minutes

Steps:

  1. Document project requirements (team skills, timeline, features)
  2. Review references/frameworks.md decision matrix
  3. Score each framework against requirements
  4. Consider long-term maintenance and ecosystem factors
  5. Document decision with rationale

Reference: references/frameworks.md

Decision Factors:

FactorReact NativeFlutterWhen to Weight Heavily
Team JavaScript experience+++++Existing web team
UI consistency across platforms++++++Brand-critical apps
Native module needs+++++Hardware integration
Hot reload speed+++++++Rapid iteration
Bundle size+++++Download-sensitive markets
Web support++++++PWA requirements

Workflow 5: CI/CD Pipeline Setup

Time: 30-45 minutes

Steps:

  1. Generate project with --ci flag for base configuration
  2. Configure signing credentials in CI secrets
  3. Set up Fastlane for iOS/Android automation
  4. Configure TestFlight/Play Console deployment
  5. Add automated testing stages
  6. Enable release automation

Generated CI Configurations:

  • GitHub Actions workflows for iOS and Android
  • Fastlane configuration files
  • Environment variable templates
  • Code signing setup guides

Python Tools

mobile_scaffolder.py

Generate complete mobile project structures with best practices.

python3 scripts/mobile_scaffolder.py --help

Options:
  --framework      react-native|flutter|expo (required)
  --platforms      ios,android,web (default: ios,android)
  --navigation     react-navigation|expo-router|go-router|auto-route
  --state          redux|zustand|mobx|riverpod|bloc|provider
  --ci             github-actions|gitlab-ci|bitrise|none
  --output         Output directory path
  --dry-run        Preview without creating files

platform_detector.py

Analyze mobile projects for capabilities and configuration.

python3 scripts/platform_detector.py --help

Options:
  --check          ios|android|all (default: all)
  --depth          quick|standard|full|signing
  --output         text|json|csv (default: text)
  --project-path   Path to project root (default: current directory)

app_store_validator.py

Validate builds against App Store and Play Store requirements.

python3 scripts/app_store_validator.py --help

Options:
  --store          apple|google|both (required)
  --build-path     Path to build artifacts
  --check          all|icons|manifest|signing|privacy
  --strict         Fail on warnings (recommended for release)
  --output         text|json|markdown

References

Best Practices

Project Structure

  • Use monorepo structure for shared code between platforms
  • Separate platform-specific code into dedicated directories
  • Implement feature-based module organization
  • Use environment configuration for different build variants

Performance

  • Implement lazy loading for screens and heavy components
  • Use native driver for animations where possible
  • Optimize images and assets for mobile
  • Profile and monitor app performance regularly

Security

  • Never commit signing credentials
  • Use secure storage for sensitive data
  • Implement certificate pinning for API calls
  • Follow platform-specific security guidelines

Testing

  • Write unit tests for business logic
  • Implement integration tests for critical flows
  • Use snapshot testing for UI components
  • Test on real devices before release

Success Metrics

  • Project Setup Time: 15-30 minutes (vs 2-4 hours manual)
  • Store Rejection Rate: <5% (vs industry average 30%)
  • Platform Detection Accuracy: 99%+
  • CI/CD Setup Time: 30-45 minutes (vs 4-8 hours manual)

平台分布

Claude Code

29.87%
按下载量换算63

OpenCode

24.73%
按下载量换算52

windsurf

15.57%
按下载量换算33

trae

11.65%
按下载量换算24

Cursor

7.86%
按下载量换算17

Codex

3.09%
按下载量换算6

安全审计

暂无安全审计结果可展示。

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills