agentleFS
Sign inStart free
everpcpceverpcpc/KMReader/.agents/skills/testflight/SKILL.md

testflight

Skill118 starsChanged 7 days agoMITView on GitHub

Distribute KMReader builds to TestFlight groups via the asc CLI. Use when asked to add a build to TestFlight groups, check which groups a build is in, or submit a build for Beta App Review.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. zhu-xiaowei/Baton★ 14same name
    2. Sassy-Dog/skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

Create a free account to mount
Files
SKILL.md

TestFlight

Distribute uploaded KMReader builds to TestFlight groups with the asc CLI.

Groups

KMReader App Store app ID is 6755198424. List groups to get current names and IDs:

asc testflight groups list --app 6755198424 --pretty
  • Internal groups receive new builds automatically; no action needed.
  • External groups require a Beta App Review submission per build before testers see it.

Add A Build To Groups

asc builds add-groups --build-id "$build_id" \
  --group "$group_id_1,$group_id_2" \
  --submit --confirm --pretty
  • --group takes comma-separated group IDs or names; one call can cover multiple groups.
  • --submit --confirm submits the build for Beta App Review, which external groups require before testers see the build. Omit it only for internal-only distribution.
  • Build selection alternatives to --build-id: --app 6755198424 --latest, or --app 6755198424 --build-number 607 --platform IOS.
  • Each platform has its own build ID; repeat per platform (iOS/macOS/tvOS).
  • The command stops without sending the request when ASC state (processing, expiry, encryption, beta review) does not prove readiness — read the error, fix the state, retry.

Verify

asc builds groups list --build-id "$build_id" --pretty

External testers see the build only after Beta App Review approves it (usually within hours).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free