Loading...
Loading...
Found 162 Skills
Manage Claude Code agent skills using the `asc` CLI tool. Use this skill when: (1) Listing available skills: "asc skills list", "what skills are available", "show me asc skills" (2) Installing skills: "asc skills install --name asc-cli", "install all skills", "add asc skills to my agent" (3) Viewing installed skills: "asc skills installed", "what skills do I have", "show my installed skills" (4) Removing a skill: "asc skills uninstall --name asc-auth", "remove a skill" (5) Checking for skill updates: "asc skills check", "are my skills up to date" (6) Updating skills: "asc skills update", "update my asc skills" (7) User asks "how do I install asc skills", "set up asc CLI skills", or "get the latest asc skills" (8) Troubleshooting skill installation or update issues (npx, skills CLI)
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
Build, edit, analyze, and improve PowerPoint presentations (.pptx). Use when a user asks to: (1) Create a new presentation from scratch, (2) Edit or modify slides, text, images, or layouts, (3) Analyze a presentation for quality, consistency, or content, (4) Improve an existing presentation's design, structure, or readability, (5) Extract text or speaker notes, (6) Add charts, tables, or media to slides, (7) Review or critique a presentation.
Weekly summary: this week's meetings, unread email breakdown by category, and team assignment status.
Read a GitHub Issue, create a detailed plan in `_/local-plans/<issue-number>-<slug>.md`, and implement the code **after user approval**. After implementation, perform a security review (OWASP Top 10) → run tests → commit using Conventional Commits. Used for implementation requests where an Issue number or URL is provided, such as "Implement Issue #N" or "Start working on this Issue".
Batch archive project items with Status set to Done using `gh project item-archive`. Also checks and guides on the configuration status of the Auto-archive built-in workflow (manual execution is basically unnecessary if enabled). Used for scenarios like "archive completed items", "organize Done items", "clean up the board", etc.
Run the full deal lifecycle from CLI — discover pipelines/stages, qualify MQLs into deals with associations, advance/reassign in bulk, hunt stalled deals, and close.
Daily briefings, pipeline snapshots, and win/loss analysis from the terminal — closing-this-week, open pipeline by stage/owner, and closed-won vs closed-lost over a period.
Assign and reassign CRM record ownership, audit who-owns-what across object types, and handle rep transitions. Built on `bulk-operations`.
Pre-submission validation for Google Play releases covering metadata, screenshots, bundle integrity, data safety, and policy compliance. Use when preparing a release to avoid rejections and catch issues before submitting.
Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using the existing generate-and-PR flow. Use when the user says "submit to wall of apps", "add my app to the wall", "wall-of-apps", or asks for make generate app + PR help.
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