Claude Code itself runs on a desktop — that's where ~/.claude/skills/ lives and where you actually use a skill in your editor. But the catalog has 74,000+ entries, and that's far too many to browse during your work day, on your work machine, in the middle of an actual task.
The ClaudSkills web app is the discovery surface. Add this site to your phone's home screen and it runs full-screen like a native app — with offline catalog browsing, a daily push reminder, and the same brand experience on every device. Find something interesting? One tap opens the same URL on the desktop. Install happens there, in 2 seconds.
The two surfaces close a loop the website alone never could: discover on mobile, install on desktop, use in Claude Code.
The discovery → install loop
SKILL.md to ~/.claude/skills/<slug>/. No copy-paste, no edits.Phone install — Android only
ClaudSkills is a Progressive Web App. On Android it installs in two taps and behaves like a native app: home-screen icon, full-screen mode, offline catalog browsing, and a daily push reminder for the Skill of the Day. On iOS the install flow technically exists but is so deeply buried in Safari's Share sheet that we no longer recommend it as a user channel — iOS users get the responsive website experience instead, which is good enough for browsing the catalog.
claudskills.com in any modern Android browser.Push notifications work natively on Android. Visit /sotd/ twice and you'll see an opt-in card for the daily Skill of the Day reminder.
claudskills.com in Safari. That's it — the responsive layout works fine on iPhone.Honest read: we tried positioning iOS PWA install as a feature; even savvy users couldn't reliably find the install button. We stopped pretending it's a normal path. The desktop client + the responsive website cover the iOS experience.
Where each surface earns its keep
quality_pro ≥ 80). Deterministic per-device — same skill recurs once every ~18 years on a single device. Habit loop.SKILL.md to ~/.claude/skills/<slug>/ and the skill is live in your next Claude session. Mobile sends you here.https://claudskills.com/skills/<slug>/ URL opens directly in the app on iOS and Android — share cards from a friend, links in your team's Slack, X mentions. iOS AASA + Android assetlinks.json restrict interception to /skills/* only.Frequently asked
No — Claude Code itself runs on macOS, Linux, or Windows, and skills install at ~/.claude/skills/ on that machine. The mobile app is a discovery surface: browse the full registry on your phone, share interesting skills with teammates, then open the same URL on your desktop to run the one-click install. The "Open on claudskills.com" button on every skill in the app routes to the install instructions on the web.
Three native-only features: a daily push notification at 9am with a curated Skill of the Day from the top 12% of the catalog; a local streak counter that rewards daily visits with milestone share cards; and a one-tap share-card generator that exports a 1080×1920 branded image with QR code to X, Threads, Instagram Stories, or LinkedIn. The website has none of these — they only make sense on a device you carry.
Completely free. No in-app purchases, no ads, no third-party tracking, no analytics SDKs. The app collects zero personal data — see the mobile privacy policy. Pro features (the multi-signal Quality Score and one-click install) live in the desktop app and the website; mobile is purely a discovery surface that funnels users back to the website for purchase, never the other direction.
Yes — iOS Universal Links and Android App Links are wired for paths under /skills/. Once the app is installed, tapping any https://claudskills.com/skills/<slug>/ URL (from a friend's share card, an X post, a Slack link, etc.) opens directly in the app on the recipient's device. The website still serves the same page in the browser for users who don't have the app, so neither side is broken for either audience.
App Store discoverability is overrated for a free reader app, and Apple's 3.1.1 stance has tightened to where any funnel from a free app to web checkout triggers rejection even without direct CTAs. PWA gives us native-feeling install + offline + push on Android with none of the gate-keeping costs: no 30% revenue cut, no 14-day store-review queue, no version-drift between web and mobile, instant updates with every site deploy. For Android the math is heavily in PWA's favor. iOS is a separate story — see the next question.
Technically yes; practically not really. iOS Safari supports PWA install via Share → Add to Home Screen, but Apple buries this option behind multiple share-sheet pages and (in many configurations) requires you to opt the action back in via the share sheet's Edit Actions menu first. We tried documenting it as a normal install path; even savvy users tried hard and couldn't find the button. So we stopped pretending. On iOS, ClaudSkills is a responsive website you bookmark in Safari — the service worker still caches catalog pages offline, you just don't get a home-screen icon or push notifications. If Apple ever surfaces PWA install properly, we'll re-add the path.
The PWA shares the same Plausible analytics the website uses — privacy-friendly, no cookies, no fingerprinting, GDPR/CCPA/PECR-compliant, no consent banner needed. We see aggregate pageview counts and outbound-click counts; we do NOT see who visited what skill page or correlate visits to identity. If you opt in to push notifications, your push-subscription endpoint is stored on our Supabase so we can send the daily SOTD reminder — tap "unsubscribe" in your notification or revoke notifications in your phone's settings to remove the subscription completely.
Yes — with a caveat. The service worker caches every skill page you visit, plus /data/skills.json (the full catalog metadata) on first load. So even with no signal you can re-open any catalog page you've visited and the homepage. Pages you've NEVER visited can't load offline because the SW has nothing cached for them — those show the offline fallback shell with a "Try again" button. Catalog refreshes itself in the background whenever you're back online.
Not on iOS. The React Native scaffold for the Android build sits in the mobile/ directory of the public repo — if there's ever a strong product reason to ship Android-via-Play-Store (e.g., a feature the PWA can't deliver), we can finish the EAS Build + Play closed-testing flow then. For now, the PWA does the job. iOS is permanently a PWA-only platform for ClaudSkills.