Loading...
Loading...
Found 198 Skills
Download sales, trends, financial, and analytics reports from App Store Connect using the `asc` CLI tool. Use this skill when: (1) Downloading sales reports: "asc sales-reports download --vendor-number ... --report-type SALES ..." (2) Downloading finance reports: "asc finance-reports download --vendor-number ... --report-type FINANCIAL ..." (3) Analytics reports: "asc analytics-reports request/list/reports/instances/segments" (4) Checking app sales, revenue, downloads, subscriptions, proceeds, or analytics (5) User says "download my sales report", "show sales data", "get financial report", "check my app revenue", "how many downloads", "subscription metrics", "app analytics", "app usage data", "engagement metrics"
Create implementation task plans in `_/local-plans/<plan-name>.md`. First investigate the codebase using the Explore Agent, then document it in verifiable granularity and parallel-executable units, following the standard format (Background & Purpose, Current Status, Design, File Structure Tree, Implementation Steps, Verification Methods) that can be validated by the plan-verifier Agent. Used for requests like "Make a plan", "Design", "Task decomposition", "Think about implementation approach". plan, planning, design, implementation plan, task decomposition, create-plan
Phase 分割された GitHub Issue ツリーを新規作成するスキル。「イシューツリー作って」「タスクを Phase 別に Issue 化」「Issue ツリーを起票して」で使用。 要件・タスク一覧を受け取り、タスク分解（4h 粒度）→ Phase 分割 → ルート（トラッキング）issue → Phase 親 issue → 子 issue の階層を sub_issues API で紐付け。 phase ラベル付与・ルート issue 本文の Phase 別表生成まで自動化。任意の phase 指定で部分起票にも対応。 ツリーの棚卸し・更新は update-issue-tree、実装消化は implement-issue-tree を参照。
End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.
Android app signing, keystores, and Play App Signing setup. Use when configuring signing for new apps or migrating to Play App Signing.
Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.
Orchestrate Google Play beta testing groups and distribution using gpd. Use when managing testers, internal testing, or beta rollouts.
Sync and validate Google Play metadata, listings, and assets with gpd, including Fastlane-style workflows. Use when updating store listings or translations.
Create git commits in Conventional Commits format. Estimate type/scope from staged changes, detect breaking changes and secret leaks (such as .env files). Must pass pre-commit hooks (`--no-verify` is not allowed). Use with instructions like "commit", "git commit", "record changes".
Apifox Test Scenario Modeling: Query, create, update, delete and run test-scenario; Import endpoints, single-interface test cases or other scenario steps; Add scenario reference steps; Best practices for complex step orchestration, connection of steps such as interface steps/conditions/loops/waiting/scripts/databases, pre/post operations, variable references, assertions, extractors and scenario debugging. Used when users need to create or maintain complex automated testing workflows.
Apifox API Test Cases: Query, create, update, delete, categorize and run test-case and test-data; handle test steps, assertions, variable extraction, pre/post processors, datasets, and issues such as 'CLI-created test steps not displaying in frontend'.
Use the ready-to-use qiqi command to handle general tasks of Qiqi Service Industry ERP. It is applicable for verifying identity and profile, discovering objects and fields, querying records or work views, handling pagination and large outputs, executing documents or approval actions, deleting records, processing attachments, or verifying writes with unclear results.