Capacitor

v1.0.0

Comprehensive Capacitor expert skill that consolidates core concepts, CLI usage, app creation, plugin management, framework integration, cross-platform best...

1· 102·0 current·0 all-time
byRobin Genz@robingenz
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (Capacitor expert/reference) aligns with the SKILL.md content: CLI usage, project structure, plugin patterns, framework integration, build and publish workflows. Nothing in the instructions asks for unrelated privileges or resources.
Instruction Scope
SKILL.md contains step-by-step Capacitor guidance and example CLI commands (npm, npx cap, project layout, framework patterns). It does not instruct the agent to read arbitrary system files, exfiltrate data, or access environment variables beyond normal build/publish workflows.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, which reduces filesystem/write risk. Example commands reference commonly used package managers (npm/npx) rather than downloading arbitrary archives.
Credentials
The skill declares no required env vars or credentials. The content does mention Capawesome Cloud and app store publishing, which in real workflows require provider credentials (Apple/Google/Capawesome), but the skill does not request or store those — this is proportionate. Users should avoid pasting secrets into chat.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not request permanent presence or modifications to other skills/configs; this level of privilege is normal for a user-invocable reference skill.
Assessment
This instruction-only Capacitor skill appears coherent and low-risk, but confirm the skill's origin before trusting it (registry metadata listed the source as unknown even though SKILL.md contains a GitHub link). Don't paste Apple/Google/Capawesome API keys or other secrets into chat. If you plan to follow recommended CLI steps, inspect the referenced GitHub docs and run commands in a safe/dev environment (not a production machine). If you need publishing or Capawesome Cloud workflows, obtain and manage those credentials via your normal secure processes (CI secrets, credential stores) rather than providing them to the skill or chat.

Like a lobster shell, security has layers — review code before you run it.

latestvk970vtzpq52k2vdx1q8rrcr5hs83hsxa

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments