Name: clickfunnels-classic
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

clickfunnels-classic

ClickFunnels integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickFunnels data.

Quality

66%

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/clickfunnels-classic/SKILL.md

Quality

Content

75%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 body is highly actionable with concrete, copy-paste-ready CLI commands and a well-structured connection state machine, but it carries some conceptual/marketing padding and a broken "Step 2" cross-reference that slightly undercut conciseness and workflow clarity.

Suggestions

Trim the opening paragraph and marketing phrasing (e.g. "so you can focus on the integration logic rather than auth plumbing") to assume Claude's competence and save tokens.

Fix or remove the dangling "skip to Step 2" references, since no Step 2 section exists in the document.

Consider moving the clientAction state-machine details and the proxy flags table into a referenced reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening "ClickFunnels Classic is a platform that helps users build sales funnels..." concept explainer and marketing-style lines like "so you can focus on the integration logic rather than auth plumbing", fitting anchor 3.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a concrete flags table, covering the common cases fully as in anchor 5.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but the dangling "skip to Step 2" reference with no corresponding Step 2 section and absent post-run validation leave minor gaps, fitting anchor 4 rather than 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers covering install, auth, connection, actions, proxy, and best practices, but at ~140 lines some content (the flags table, clientAction state machine) could be split into referenced files, matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

57%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 correctly pairs a clear what with an explicit use-when clause and is anchored by a distinctive brand name, but its capabilities are generic and it omits the natural trigger terms (funnels, contacts, landing pages) users would actually say.

Suggestions

Replace generic verbs with concrete ClickFunnels actions, e.g. "Manage funnels, steps, pages, and contacts; run and search actions via the Membrane CLI."

Expand the trigger clause to natural user phrasing: "Use when the user wants to manage ClickFunnels funnels, pages, contacts, or automate sales workflows."

Add file/extension or entity terms (funnels, landing pages, contacts) to broaden trigger-term coverage beyond the brand name alone.

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the ClickFunnels domain but the actions are minimal and generic rather than concrete platform-specific operations, matching anchor 2 more than the concrete-action anchor 3.	2 / 5
Completeness	It states both the what ("ClickFunnels integration. Manage data, records, and automate workflows.") and an explicit when ("Use when the user wants to interact with ClickFunnels data"), but the when is generic and could be more specific, matching anchor 4 rather than the concrete-trigger anchor 5.	4 / 5
Trigger Term Quality	"ClickFunnels" is the natural brand term a user would say and "interact with ClickFunnels data" gives a relevant trigger, but common variations like "funnels", "sales funnels", "landing pages", or "contacts" are missing, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The ClickFunnels brand name gives it a clear niche with minimal conflict risk, but the generic "Manage data, records, and automate workflows" phrasing leaves minor overlap with other integration skills, fitting anchor 4 rather than a fully distinct anchor 5.	4 / 5
	Total	13 / 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/clickfunnels-classic/SKILL.md
Commit: f484c82

Reviewed: ~9 hours 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.