asc-cli-usage

rudrankriyam/asc-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-cli-usage
0 commentsdiscussion
summary

Use this skill when you need to run or design asc commands for App Store Connect.

skill.md

asc cli usage

Use this skill when you need to run or design asc commands for App Store Connect.

Command discovery

  • Always use --help to discover commands and flags.
    • asc --help
    • asc builds --help
    • asc builds list --help

Canonical verbs (current asc)

  • Prefer view over legacy get aliases for read-only commands in docs and automation.
    • asc apps view --id "APP_ID"
    • asc versions view --version-id "VERSION_ID"
    • asc pricing availability view --app "APP_ID"
  • Prefer edit for update-only availability surfaces and other canonical edit flows.
    • asc pricing availability edit --app "APP_ID" --territory "USA,GBR" --available true
    • asc app-setup availability edit --app "APP_ID" --territory "USA,GBR" --available true
    • asc xcode version edit --build-number "42"
  • Keep set where the CLI intentionally models a higher-level replacement/configuration flow and --help still shows set as the canonical verb.

Flag conventions

  • Use explicit long flags (e.g., --app, --output).
  • Prefer explicit flags in automation; some newer commands can prompt for missing fields when run interactively.
  • Destructive operations require --confirm.
  • Use --paginate when the user wants all pages.

Output formats

  • Output defaults are TTY-aware: table in interactive terminals, json when piped or non-interactive.
  • Use --output table or --output markdown only for human-readable output.
  • --pretty is only valid with JSON output.

Authentication and defaults

  • Prefer keychain auth via asc auth login.
  • Fallback env vars: ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH, ASC_PRIVATE_KEY, ASC_PRIVATE_KEY_B64.
  • ASC_APP_ID can provide a default app ID.
  • When permissions are unclear, inspect exact API key role coverage with asc web auth capabilities.
    • This lives under the experimental web auth surface.
    • It can resolve the current local auth by default, or inspect a specific key with --key-id.

Timeouts

  • ASC_TIMEOUT / ASC_TIMEOUT_SECONDS control request timeouts.
  • ASC_UPLOAD_TIMEOUT / ASC_UPLOAD_TIMEOUT_SECONDS control upload timeouts.
how to use asc-cli-usage

How to use asc-cli-usage on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add asc-cli-usage
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-cli-usage

The skills CLI fetches asc-cli-usage from GitHub repository rudrankriyam/asc-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/asc-cli-usage

Reload or restart Cursor to activate asc-cli-usage. Access the skill through slash commands (e.g., /asc-cli-usage) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.639 reviews
  • Sakura Robinson· Dec 8, 2024

    asc-cli-usage has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Hiroshi Garcia· Nov 27, 2024

    Solid pick for teams standardizing on skills: asc-cli-usage is focused, and the summary matches what you get after install.

  • Yash Thakker· Nov 15, 2024

    asc-cli-usage reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Diego Thompson· Oct 18, 2024

    asc-cli-usage is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hana White· Oct 18, 2024

    asc-cli-usage reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Dhruvi Jain· Oct 6, 2024

    We added asc-cli-usage from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Diego Okafor· Sep 25, 2024

    Keeps context tight: asc-cli-usage is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Piyush G· Sep 21, 2024

    Solid pick for teams standardizing on skills: asc-cli-usage is focused, and the summary matches what you get after install.

  • Fatima Li· Sep 9, 2024

    asc-cli-usage has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Chinedu Perez· Sep 1, 2024

    asc-cli-usage is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 39

1 / 4