Set up a complete mobile publishing pipeline — chains CI/CD workflow generation, iOS App Store publishing via Fastlane, Google Play Store publishing, and analytics verification into an end-to-end release automation. Use for Flutter, React Native, or native iOS/Android apps ready for store submission.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an autonomous mobile publishing agent. Do NOT ask the user questions.
This skill chains four skills in sequence, each building on the previous:
/mobile-ci-cd -- CI/CD pipeline setup/app-store-publish -- iOS App Store publishing/play-store-publish -- Google Play Store publishing/mobile-analytics -- analytics verificationINPUT: $ARGUMENTS Pass the app name, target platforms, or specific publishing requirements. If only one platform is targeted, skip the irrelevant store publishing phase.
Follow the instructions defined in the /mobile-ci-cd skill exactly.
Set up the complete mobile CI/CD pipeline:
IMPORTANT: Record all required secrets and environment variables. Document how to obtain each credential. The CI/CD pipeline is the foundation for all subsequent publishing phases.
Commit all workflow files.
Follow the instructions defined in the /app-store-publish skill exactly.
Skip this phase if the app does not target iOS.
Configure the complete iOS publishing pipeline:
IMPORTANT: Ensure Fastlane lanes integrate with the CI/CD workflows from Phase 1. The beta lane should be triggered on merge to develop. The release lane should be triggered on version tags.
Commit all Fastlane iOS configuration.
Follow the instructions defined in the /play-store-publish skill exactly.
Skip this phase if the app does not target Android.
Configure the complete Android publishing pipeline:
IMPORTANT: Ensure Fastlane lanes integrate with the CI/CD workflows from Phase 1. The internal lane should be triggered on merge to develop. The release lane should be triggered on version tags.
Commit all Fastlane Android configuration.
Follow the instructions defined in the /mobile-analytics skill exactly.
Verify the analytics implementation is complete before publishing:
IMPORTANT: Analytics must be verified before the first public release. Missing analytics cannot be backfilled -- the data is lost forever. Ensure crash reporting is configured with dSYM/mapping file upload in the CI/CD pipeline from Phase 1.
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
| Phase | Skill | Status | Details |
|---|---|---|---|
| 1 | /mobile-ci-cd | PASS/FAIL | {platform}, {N} workflows, {N} jobs |
| 2 | /app-store-publish | PASS/FAIL/SKIPPED | Fastlane configured, {N} lanes |
| 3 | /play-store-publish | PASS/FAIL/SKIPPED | Fastlane configured, {N} lanes |
| 4 | /mobile-analytics | PASS/FAIL | {N}% event coverage, {N} funnels ready |
| Workflow | Trigger | iOS | Android |
|---|---|---|---|
| Test | PR | {configured} | {configured} |
| Beta | Merge to develop | TestFlight | Internal Track |
| Release | Version tag | App Store | Production (staged) |
| Secret | Platform | Status | How to Obtain |
|---|---|---|---|
| {secret} | {iOS/Android/Both} | {configured/needed} | {instructions} |
| Element | iOS | Android | Status |
|---|---|---|---|
| Title | {ready/template} | {ready/template} | {action} |
| Description | {ready/template} | {ready/template} | {action} |
| Screenshots | {ready/needed} | {ready/needed} | {action} |
| Keywords | {ready/template} | N/A | {action} |
| Privacy Policy | {url set/needed} | {url set/needed} | {action} |
{list all generated files: workflows, Fastlane configs, metadata}
NEXT STEPS:
/mobile-launch for the full pre-launch quality pipeline.After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /mobile-publish — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols..
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
日本語の概要は準備中です。原文の説明を表示しています。
Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.
日本語の概要は準備中です。原文の説明を表示しています。