Loading...
Loading...
Found 7,366 Skills
Manage customer reviews and developer responses using the `asc` CLI tool. Use this skill when: (1) Listing customer reviews for an app: "asc reviews list --app-id <id>" (2) Getting a specific review: "asc reviews get --review-id <id>" (3) Getting the response to a review: "asc review-responses get --review-id <id>" (4) Creating a response to a review: "asc review-responses create --review-id <id> --response-body <text>" (5) Deleting a response: "asc review-responses delete --response-id <id>" (6) User says "list reviews", "respond to review", "delete response", "check customer feedback", "reply to App Store review", or any customer review management task
Manage beta app review submissions and review contact details for TestFlight external testing using the `asc` CLI tool. Use this skill when: (1) Submitting a build for beta app review: "asc beta-review submissions create --build-id ID" (2) Checking beta review submission status: "asc beta-review submissions list --build-id ID" (3) Getting a specific submission: "asc beta-review submissions get --submission-id ID" (4) Getting beta review contact details: "asc beta-review detail get --app-id ID" (5) Updating beta review contact info or demo account: "asc beta-review detail update --detail-id ID ..." (6) User says "submit for beta review", "TestFlight review", "beta review status", "beta review contact", "external testing review", or any beta app review task
Set up and run an autonomous experiment loop for any optimization target. Gathers what to optimize, then starts the loop immediately. Use when asked to "run autoresearch", "optimize X in a loop", "set up autoresearch for X", or "start experiments".
Create a new skill. When to use: When the user says "create skill", "new skill", "add skill", "initialize skill".
Manage ASC plugins that extend the CLI with custom event handlers using the `asc` CLI tool. Use this skill when: (1) Listing installed plugins: "asc plugins list" (2) Installing a plugin: "asc plugins install PATH" (3) Removing a plugin: "asc plugins uninstall --name NAME" (4) Enabling or disabling plugins: "asc plugins enable/disable --name NAME" (5) Testing a plugin manually: "asc plugins run --name NAME --event EVENT" (6) User asks to "create a plugin", "add Slack notifications", "wire up a Telegram bot on build upload", or "extend the CLI with a custom handler" (7) Explaining the plugin protocol (manifest.json + run executable + JSON stdin/stdout)
Manage App Store app preview video sets and uploads using the `asc` CLI tool. Use this skill when: (1) Listing preview sets for a localization: "asc app-preview-sets list --localization-id ID" (2) Creating a preview set: "asc app-preview-sets create --localization-id ID --preview-type IPHONE_67" (3) Listing previews in a set: "asc app-previews list --set-id ID" (4) Uploading a preview video: "asc app-previews upload --set-id ID --file preview.mp4" (5) User says "upload app preview", "add preview video", "create preview set", or "list previews"
Manage App Clips and App Clip default experiences using the `asc` CLI tool. Use this skill when: (1) Listing App Clips for an app: "asc app-clips list --app-id ID" (2) Listing default experiences for an App Clip: "asc app-clip-experiences list --app-clip-id ID" (3) Creating a default experience: "asc app-clip-experiences create --app-clip-id ID [--action OPEN|VIEW|PLAY]" (4) Deleting a default experience: "asc app-clip-experiences delete --experience-id ID" (5) Listing experience localizations: "asc app-clip-experience-localizations list --experience-id ID" (6) Creating an experience localization: "asc app-clip-experience-localizations create --experience-id ID --locale CODE [--subtitle TEXT]" (7) Deleting an experience localization: "asc app-clip-experience-localizations delete --localization-id ID" Trigger phrases: "app clip", "app clips", "clip experience", "clip localization", "default experience", "OPEN action", "VIEW action", "PLAY action", "App Clip card", "App Clip subtitle"
Manage App Store Connect team members and user invitations using the `asc` CLI tool. Use this skill when: (1) Listing team members with their roles (`asc users list`) (2) Filtering members by role (`asc users list --role DEVELOPER`) (3) Updating or replacing a member's roles (asc users update --user-id ID --role ADMIN) (4) Revoking or removing access for a departing employee (asc users remove --user-id ID) (5) Listing pending invitations (asc user-invitations list) (6) Inviting a new team member by email (asc user-invitations invite) (7) Cancelling a pending invitation (asc user-invitations cancel) (8) User says "revoke access", "remove team member", "offboard user", "invite developer", "add someone to App Store Connect", "manage team roles", "who has admin access", "grant access", "onboard", or any team/user management task in App Store Connect
Agent Teams Orchestration Playbook for Claude Code. This skill should be used when the user requests to "create agent teams", "use agent swarm", "set up multi-agent collaboration", "orchestrate agents", "coordinate parallel agents", "organize team collaboration", "build agent teams", "implement swarm orchestration", "set up multi-agent system", "coordinate agent collaboration", or needs guidance on adaptive team formation, quality gates, skill discovery, task distribution, team coordination strategies, or Agent Teams best practices. It should also be used when the user mentions terms like "multi-agent", "agent collaboration", "agent orchestration", "parallel agents", "divisional collaboration", "assemble a team", "put together a team", "multi-agent collaboration", "swarm orchestration", "agent team". Note: "swarm" is a generic industry term; Claude Code's official concept is "Agent Teams".
Automatically updates terminal window title to reflect the current high-level task. Use at the start of every Claude Code session when the user provides their first prompt, and whenever the user switches to a distinctly new high-level task. Helps developers manage multiple Claude Code terminals by providing clear, at-a-glance identification of what each terminal is working on.
Interact with the Overvy kanban board via curl. Use when the user wants to list issues, list AI tickets, work on a ticket, move issues between lanes, or check board status. Triggers include "overvy", "list AI tickets", "show me ready tickets", "what tickets are available", "what should I work on", "work on ticket", "work on any ticket", "pick a ticket", "start a ticket", "pick up an issue", "my issues", "kanban board", "move issue", "list issues", "board status", or references to lanes like "ready", "in progress", "in review", "done". Requires OVERVY_API_KEY environment variable.
Send notifications via Notifery API using curl. Use when the user wants to be notified about task completions, errors, or progress. Also use proactively after long-running tasks, failed operations, or when the user has asked to be kept informed. Triggers include "notify me", "send notification", "let me know when done", "alert me", "ping me", "notifery", or when a long task completes and the user previously asked for notifications. Requires NOTIFERY_API_KEY environment variable.