Updated 1d ago
by namedtoaster
The-Last-Mile
Claude Code skills that get your app into the App Store and Google Play. Rejection sweep, release build, store listing, upload. Any stack.
31 GitHub stars (31)
+31 in 12 days
| Period | New stars |
|---|---|
| Oct 22 | +5 |
| Oct 23 | +3 |
- 19 skills (19 skills found in its SKILL.md files)
- 1 forks (1 forks)
- 1d ago last update (Last updated 1d ago)
Install
Skills CLI
npx skills add namedtoaster/The-Last-Mile
Asks which skills and agents to install. Just one: npx skills add namedtoaster/The-Last-Mile --skill connect-tools — add -g for every project.
Claude Code
git clone https://github.com/namedtoaster/The-Last-Milecp -r "The-Last-Mile/skills/connect-tools" ~/.claude/skills/
Copies the connect-tools skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add namedtoaster/The-Last-Mile
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
connect-tools
Connect Claude to the services an app already uses (RevenueCat, PostHog, Sentry, Expo, Supabase, Stripe and others) through each vendor's official MCP server, so it can read real crashes, analytics, subscriptions and builds instead of guessing. Reads the project to see which services it uses, checks what is already connected, adds the missing ones with the right scope, and records them in the rul…
skills/connect-tools/SKILL.md on GitHub (opens in a new tab) -
fact-check
Re-check stated facts about the App Store, Google Play and app tools against the current official pages, update each fact's status and date, fix broken source links, and report what changed. Works on a project's rules file and docs, or on The Last Mile's own traps and facts (one topic or all of them). Use when the user says "check the facts", "is this still true", "re-verify the traps", "store ru…
skills/fact-check/SKILL.md on GitHub (opens in a new tab) -
feature-demo
Build a tap-through demo of a feature so the person can see it before it ships, instead of reading a spec about it. Enumerates the feature's real states, draws them in the app's own colours and fonts, publishes a clickable walkthrough, and annotates each step with the decision behind it. Use when a feature has states nobody can reach by tapping around, when a spec conversation has stalled, when a…
skills/feature-demo/SKILL.md on GitHub (opens in a new tab) -
improve-skill
Fix a Last Mile skill that did the wrong thing, from inside the project where it went wrong. Decides whether the lesson belongs in the project's rules file or in the skill, makes the smallest change to the skill in The Last Mile repo (never the synced copy), keeps every project detail out because the repo is public, runs the checks and opens a pull request. Use when the user says a skill misfired…
skills/improve-skill/SKILL.md on GitHub (opens in a new tab) -
lean-out
Find the structural clutter in an app that is making every new change land wrong, and rank it by what it would have prevented rather than by taste. Produces a measured audit and a list that can be worked through in pieces, never a big bang refactor. Use when the codebase feels heavy, when the same kind of bug keeps coming back in a new place, when a file has grown past anyone's head, or when the…
skills/lean-out/SKILL.md on GitHub (opens in a new tab) -
mine-community
Harvest a founder community (a subreddit, a forum, a newsletter archive) for what is actually working in app marketing, pricing, ASO and growth, then filter it honestly and file the few findings worth keeping. Drops milestone and promotional posts, keeps only claims that either converge with an unrelated source or contradict something the project already believes, and ranks the survivors against…
skills/mine-community/SKILL.md on GitHub (opens in a new tab) -
one-time-surface
Build or check a surface that is meant to appear once and then stop, such as a coach mark, tooltip, tour, primer, upsell card or review ask. Covers the three questions that decide whether it works for real people, not just on your phone, plus the traps that silently take it to zero. Use when adding a hint or one time card, when one is not appearing, when one keeps reappearing, or before shipping…
skills/one-time-surface/SKILL.md on GitHub (opens in a new tab) -
port-feature
Bring a feature you already built in another of your own repos into this project. Reads the source feature end to end (screens, state, data, tests and the source's gotchas), maps it onto this project's architecture and conventions, lists what changes and what stays behind, ports the tests, then proves it works here. Never copies secrets, env values, or the other app's names, copy or branding. Use…
skills/port-feature/SKILL.md on GitHub (opens in a new tab) -
reference-hunt
Find how real, shipped apps solve a given screen or flow, so the design starts from patterns people actually use instead of the AI's average guess. Searches Mobbin when it is connected, otherwise works from the user's own screenshots and App Store listing screenshots. Gives the 3 best patterns in chat, each linked to the real screen and marked seen or unconfirmed, and saves a dated reference card…
skills/reference-hunt/SKILL.md on GitHub (opens in a new tab) -
research
Answer a question by searching the project's own docs and code first, then official sources, and file the dated, sourced answer where it will be read again. Adds to an existing doc before creating a new one, marks anything unverified, and keeps a one line summary with the headline finding in the rules file's Docs index. Gives a short answer in chat first. Use when the user asks to research, look…
skills/research/SKILL.md on GitHub (opens in a new tab) -
screen-atlas
Build a browsable catalogue of every screen in the app, captured from a running build and grouped into the journeys people actually walk, so you can see what each flow does without opening the app. Finds screens nothing navigates to as a side effect. Use when the user says they cannot picture how the app flows, wants a Mobbin for their own app, asks for screenshots of every screen, wants to revie…
skills/screen-atlas/SKILL.md on GitHub (opens in a new tab) -
search-pages
Build the pages that get an app found in search, picking the topics from real search data and a check of who currently ranks rather than from taste. Puts the blog on the app's own domain, ships schema and a sitemap with the first post, and writes the comparison pages that actually pull traffic instead of the explainer pages that do not. Use when the user wants a blog, SEO, organic traffic, conten…
skills/search-pages/SKILL.md on GitHub (opens in a new tab) -
see-it-work
Prove a change to an Expo app works by seeing it, not by trusting a passing test. Picks which layer proves this change (component test, seeded simulator screenshot, smoke case, release build smoke run, browser preview, end to end journey), runs it, and shows the evidence. Use after any UI, navigation, layout, purchase or deep link change, before saying something is fixed or done, and when setting…
skills/see-it-work/SKILL.md on GitHub (opens in a new tab) -
session-end
Wrap up a working session automatically. Runs the project's checks, adds manual test items to the release checklist, records new gotchas and decisions, updates the handoff file and docs, checks progress against the current goal, commits only this session's files and pushes. Use when the user says they are done, wrapping up, or asks to end the session.
skills/session-end/SKILL.md on GitHub (opens in a new tab) -
set-goals
Write or renew the project's 6 week goal in GOALS.md, and close the previous cycle in a few lines drafted from git history. Walks the stages from a working loop on your phone, into the stores, to the first 100 weekly users and beyond, each with a default goal to edit. Use when the user says "set my goal", "new cycle", "what should I focus on", "my goal ended", or when session end has said the cur…
skills/set-goals/SKILL.md on GitHub (opens in a new tab) -
setup
Interview the user one question at a time and write the project's rules file, goals file, handoff file and release checklist. Use when starting a new app, adopting The Last Mile in an existing project, or when the user asks to set up or redo their project rules.
skills/setup/SKILL.md on GitHub (opens in a new tab) -
ship
Take any mobile app, on any stack, from a working build to the App Store and Google Play. Works out the stack, sweeps the code for known rejection traps, fixes what it can, bumps the version, builds and tests the release, writes the store listing and privacy answers, uploads and submits with the user's yes, and handles rejections. Works for Expo, React Native, Flutter, native iOS and Android, Cap…
skills/ship/SKILL.md on GitHub (opens in a new tab) -
store-listing
Write the App Store and Google Play listing from evidence instead of taste. Picks keywords by checking who already owns each phrase and whether a small app can win it, spends the name and subtitle on one lane, writes the descriptions and the first three screenshot captions, finds a screenshot look to copy from real listings, and keeps a dated keyword file so every later change can be measured. Us…
skills/store-listing/SKILL.md on GitHub (opens in a new tab) -
sync
Bring this project's copy of The Last Mile skills up to date, then commit and push it, so the next session on any device has the latest skills. Works from the phone, nothing to run by hand. Use when the user says "sync", "update the skills", "get the latest Last Mile", or a Last Mile change they just made is missing here.
skills/sync/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.