Name: funnelcockpit
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

funnelcockpit

FunnelCockpit integration. Manage Organizations. Use when the user wants to interact with FunnelCockpit data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

76%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 copy-paste CLI commands and a clear connection-state workflow, and it is reasonably concise. The main gap is the absence of validation/confirmation safeguards for the destructive delete operations it documents.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive actions (e.g. 'Before running delete-* actions, confirm the target ID with the user and verify the contact exists via the corresponding get/list action').

Trim the marketing-style intro paragraph to a one-line product context, since the bulk of value is in the commands.

Consider moving the popular-actions table into a references file and linking to it from the body to improve progressive disclosure for this longer single-file skill.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with flags, though the introductory marketing-style paragraph ('helps businesses track and optimize their sales funnels...') and a few prose asides could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure/get, action list/run, request proxy) with concrete flag examples and a JSON input example covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence with polling and error checkpoints, but the skill exposes destructive actions (e.g. 'Delete Email Contact', 'Delete CRM Contact') with no validation or confirmation step before running them, capping this dimension at 3.	3 / 5
Progressive Disclosure	Content is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, though the popular-actions table and proxy flag table are inlined in a single 170-line file rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

61%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 includes an explicit 'Use when' trigger and leverages a distinctive brand name, but its capability statement is generic ('Manage Organizations') and lacks concrete actions. It is solid on completeness and distinctiveness while weakest on specificity.

Suggestions

Replace the generic 'Manage Organizations' with concrete actions, e.g. 'Create and update CRM and email contacts, list webinars and webinar viewers, manage FunnelCockpit data.'

Expand trigger terms to include entity-level phrases users would naturally say, such as 'FunnelCockpit contacts, webinars, subscribers, or CRM records'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('FunnelCockpit integration') but the only action verb is the generic 'Manage Organizations', which is minimal rather than listing concrete operations like creating or deleting contacts/webinars.	2 / 5
Completeness	Both a 'what' ('FunnelCockpit integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with FunnelCockpit data.') are present, though the 'what' is vague and the 'when' could be more specific.	4 / 5
Trigger Term Quality	The natural trigger is essentially the brand name 'FunnelCockpit' plus 'Organizations' and 'data'; coverage is relevant but lacks common variations or synonyms beyond the single proper noun.	3 / 5
Distinctiveness Conflict Risk	The unique proper-noun brand 'FunnelCockpit' creates a clear niche with distinct triggers and minimal risk of conflicting with other skills.	5 / 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/funnelcockpit/SKILL.md
Commit: f484c82

Reviewed: 5 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.