Thinkific
v1.0.2Thinkific integration. Manage Courses. Use when the user wants to interact with Thinkific data.
⭐ 0· 83·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the runtime instructions: the skill consistently tells the agent to use Membrane to manage Thinkific resources. Required credentials/env vars are absent because Membrane is used to handle auth server-side, which is reasonable for this purpose.
Instruction Scope
SKILL.md instructs installing and using the Membrane CLI, logging in, creating connections, listing actions, running actions, and proxying API requests. These steps are within the expected scope for a third-party integration, but the instructions do instruct the user/agent to authenticate with Membrane (which will grant Membrane access to Thinkific resources).
Install Mechanism
No platform install spec was provided, but the README tells the user to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal way to obtain the CLI but does download and run third‑party code from the npm registry — a moderate-risk action that requires trusting the package and its publisher.
Credentials
The skill declares no required env vars or credentials. That is proportional because Membrane is intended to manage credentials. However, using the skill requires creating a Membrane account and granting it access to your Thinkific site, so consider the trust boundary with Membrane (data and credential handling) before proceeding.
Persistence & Privilege
The skill is instruction-only, has no install-time hooks or 'always:true' setting, and does not request system-level privileges. Autonomous invocation is enabled by default but that is the platform norm and not, by itself, a red flag here.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Thinkific. Before installing/use: (1) Verify you trust Membrane/@membranehq/cli (check npm page, GitHub, and reviews) because installing the CLI runs third‑party code on your machine; (2) Understand that creating a Membrane connection grants Membrane access to your Thinkific data — review Membrane's privacy/security practices and scope of access; (3) Prefer using a least-privilege Thinkific account or sandbox for initial testing; (4) If you cannot install global npm packages or do not want external networked tooling, do not enable this skill. If you want more assurance, provide the CLI package URL or checksums and the exact connector details so you can independently audit them.Like a lobster shell, security has layers — review code before you run it.
latestvk97976dx6gfb00mv1pd261eh19843ave
License
MIT-0
Free to use, modify, and redistribute. No attribution required.