Name: overloop
Rating: 66.4 (1 reviews)
Author: membranedev

overloop

Overloop integration. Manage Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Overloop data.

Quality

80%

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

Quality

Content

82%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.

A well-structured, highly actionable CLI integration guide with strong executable coverage and a real connection-state feedback loop. Its main weaknesses are minor redundancy and an inconsistent step-numbering scheme that references a missing Step 2.

Suggestions

Remove the duplicated `membrane action list` example in "Popular actions" or fold it into "Searching for actions" to cut redundancy.

Fix the step numbering: label Step 1 / Step 2 explicitly or rewrite the "skip to Step 2" references to point at a real heading (e.g., "Running actions").

Trim the Overloop marketing paragraph to one line so the body opens with task-relevant content.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-and-flag reference material, but the Overloop marketing intro ("sales engagement platform designed to help sales teams...") and the repeated `membrane action list --intent=QUERY` command in "Popular actions" are minor trims that keep it from a 5.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure/get, action list, action run with --input, request proxy) plus a full flag table and documented output fields, fully executable guidance.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence exists with a state-machine feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but the dangling "skip to Step 2" references an unlabeled Step 2 and numbering ("1b") is inconsistent, a minor gap.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references and all content appropriately inline for a self-contained single-file skill; minor organization gaps (the "Popular actions" section overlaps "Searching for actions", and the stray "Use action names and parameters as needed." line) keep it from a 5.	4 / 5
	Total	17 / 20 Passed

Description

78%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.

A clear, third-person description that states both what it does and when to use it, scoped to a distinct app niche. It is held back from a top score by a single generic verb and slightly thin trigger-term variety.

Suggestions

Vary the action verbs beyond the single "Manage" (e.g., "Create and update Pipelines, invite Users, track Goals, apply Filters") to lift specificity.

Align the resource list with the body's actual entities (Contacts, Sequences, Deals) or add them, so the description reflects the skill's true coverage.

Make the "when" clause more concrete with trigger phrases such as "Use when the user wants to manage Overloop contacts, sequences, or deals."

Dimension	Reasoning	Score
Specificity	Names the Overloop domain and lists several concrete manageables ("Manage Organizations, Pipelines, Users, Goals, Filters"), giving specific coverage, though the single generic verb "Manage" leaves a minor gap in action specificity versus a 5.	4 / 5
Completeness	Both halves are present: "what" (Overloop integration; manage the listed resources) and "when" ("Use when the user wants to interact with Overloop data"), but the "when" could be more specific with concrete triggering situations.	4 / 5
Trigger Term Quality	Good keyword coverage with natural domain terms (Overloop, Organizations, Pipelines, Users, Goals, Filters) a user would say, but a few natural terms seen in the body (contacts, deals, sequences) are missing and there are no synonyms.	4 / 5
Distinctiveness Conflict Risk	"Overloop integration" with Overloop-specific resource names carves a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/overloop/SKILL.md
Commit: f484c82

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