Capacitor Plugins

When you're building a Capacitor app and need native functionality, this is your routing layer. It steers you to official Capacitor packages first (camera, geolocation, preferences) and escalates to Capgo or community plugins when you need something the official set doesn't cover, like background geolocation, in-app purchases, or live OTA updates. The plugin directory is organized by category (authentication, media, sensors, payments) and includes specific package names and one-line descriptions. The decision tree is simple: use official unless it's missing or too limited, then move to the ecosystem. Honest and practical if you're tired of hunting through npm or outdated forum threads.

skills.sh installs: 309
GitHub stars: 43
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capacitor-skills --skill capacitor-plugins --agent claude-code

Installs into .claude/skills of the current project.

Files

Capacitor Plugins

Choose the right plugin, install it correctly, and prove it is linked natively.

When to Use

TRIGGER when:

User asks "which plugin should I use for X?" or compares plugin options.
User needs a native capability (camera, files, location, biometrics, payments, auth, sensors, storage, media, calendar, contacts, health, on-device LLM).
A plugin call fails after install: "X" plugin is not implemented on ios|android|web, UNIMPLEMENTED, unable to find plugin, or an OS-PLUG-* code.
User needs the right Info.plist / AndroidManifest.xml / variables.gradle entries for a plugin.