app-storePublish and manage iOS and Android apps with account setup, submission workflows, review compliance, and rejection handling.
Install via ClawdBot CLI:
clawdbot install ivangdavila/app-storeGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://api.appstoreconnect.apple.com/v1/appsUses known external API (expected, informational)
googleapis.comAudited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
A startup needs to publish its first iOS and Android apps to market quickly while ensuring compliance with platform policies. This involves setting up developer accounts, handling signing and provisioning for iOS, and navigating initial review processes to avoid common rejections like 4.2 (minimum functionality) or deceptive behavior.
An e-commerce company regularly updates its mobile apps with new features, bug fixes, and seasonal promotions. The process includes submitting builds to both App Store Connect and Google Play Console, verifying pre-submission checklists, and coordinating cross-platform releases to maintain consistency and user experience.
A gaming studio faces app rejections due to issues like crashes (2.1 on iOS) or broken functionality on Android. The studio must debug the app, implement fixes such as App Tracking Transparency for data collection, and craft effective appeal strategies with evidence like screenshots or videos to expedite re-approval.
A fitness app developer wants to implement in-app purchases and subscriptions to generate recurring revenue. This requires creating products in both platforms, integrating StoreKit and BillingClient, setting up server-side validation, and testing with sandbox accounts to ensure smooth payment flows and compliance with revenue split rules.
A large enterprise with multiple apps across iOS and Android needs to manage team roles, permissions, and release workflows efficiently. This involves structuring organizations in App Store Connect and Google Play Console, separating duties like build submission and production releases, and using phased rollouts to minimize risks during updates.
Offer the app for free with basic features and monetize through one-time purchases or consumables for premium content. This model requires setting up IAP products, implementing client-side libraries like StoreKit, and handling server-side receipt validation to prevent fraud and ensure reliable revenue streams.
Charge users a recurring fee for access to app features or content, such as streaming or productivity tools. This involves configuring subscriptions with introductory offers and free trials, managing lifecycle events like renewals, and setting up server notifications for real-time updates to maximize retention and revenue.
Sell the app at a one-time price on the App Store and Google Play, targeting users willing to pay for a complete experience without ads or in-app purchases. This model simplifies monetization but requires strong value proposition and marketing to drive downloads, with revenue subject to platform fees.
💬 Integration Tip
Use the app-store-optimization skill for keyword and A/B testing, and refer to automation.md for CI/CD tools like fastlane to streamline submission workflows.
Scored Apr 19, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.