Name: thinkific
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

thinkific

Thinkific integration. Manage Courses. Use when the user wants to interact with Thinkific data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/thinkific/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, executable Membrane CLI integration guide with concrete commands and a strong connection-state workflow. Its main weaknesses are the absence of validation checkpoints for mutating/batch actions and inlined bulk action-table content that would benefit from a separate reference file.

Suggestions

Add a verification step after mutating actions (e.g., re-fetch the created/updated user with get-user-by-id to confirm the change) to satisfy the batch/destructive validation requirement and lift workflow_clarity above 3.

Move the large Popular actions table into a references file (e.g., actions.md) and link to it from SKILL.md, keeping only a few key examples inline.

Trim the opening platform-marketing paragraph ("Thinkific is a platform that allows...") since Claude already knows what Thinkific is.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal padding, though the opening platform description ("Thinkific is a platform that allows individuals and businesses to create, market, and sell online courses...") is mild over-explanation Claude largely knows and could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready CLI commands with real flags (--json, --connectionId, --input) cover the common cases for search, run, and proxy, fitting the anchor for mostly executable guidance with minor gaps; it stops short of a fully worked end-to-end example with concrete values.	4 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence with polling feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running mutating actions like create-user/update-user lacks any verification checkpoint, and the rubric caps batch/destructive operations without validation at 3.	3 / 5
Progressive Disclosure	Sections are well organized (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with no nested references, but the 20-row Popular actions table is bulk content inlined in SKILL.md that could live in a separate reference file, fitting good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description answers both what and when with an explicit "Use when" clause and a distinctive brand keyword, but it is thin on concrete capabilities (only "Manage Courses") and lacks trigger-term variations. It sits comfortably above average but below top marks on specificity and trigger coverage.

Suggestions

Replace the single generic action "Manage Courses" with several concrete operations (e.g., list/create/enroll users, manage courses and enrollments, retrieve orders and products) to improve specificity.

Broaden trigger terms beyond the brand name to include natural phrases users say, such as "online courses," "student enrollments," "course sales/orders," or "Thinkific API."

Tighten the "when" clause to specific scenarios (e.g., "Use when the user wants to list or update Thinkific users, manage course enrollments, or retrieve orders and products").

Dimension	Reasoning	Score
Specificity	Names the domain ("Thinkific integration") and one concrete action ("Manage Courses"), matching the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage.	3 / 5
Completeness	Both a clear "what" ("Manage Courses") and an explicit "when" ("Use when the user wants to interact with Thinkific data") are present, though the trigger phrasing could be more specific, matching the anchor where both exist but the when could be more explicit.	4 / 5
Trigger Term Quality	The primary natural keyword "Thinkific" is present ("interact with Thinkific data"), but coverage lacks synonyms or variations beyond the brand name, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The distinct brand name "Thinkific" gives it a clear niche with minimal conflict risk, fitting the anchor for mostly distinct with minor overlap risk, though the surrounding trigger phrasing is somewhat generic.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/thinkific/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.