Name: ontraport
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

ontraport

Ontraport integration. Manage Persons, Organizations, Deals, Projects, Activities, Notes and more. Use when the user wants to interact with Ontraport 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/ontraport/SKILL.md

Quality

Content

67%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 highly actionable with concrete CLI commands and a clear connection workflow including polling/error handling, but spends tokens explaining Ontraport at a conceptual level and could tighten the redundant overview sections.

Suggestions

Cut the introductory "Ontraport is a CRM..." paragraph and the redundant "Ontraport Overview" bullet list; assume Claude knows the product and let the popular-actions table carry the entity coverage.

Add a worked example that runs a real action end-to-end (e.g., list-contacts with a sample --input) and an explicit validation note for destructive actions like delete-contact.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Ontraport is ("a CRM and marketing automation platform... used by entrepreneurs and small businesses") and the "Ontraport Overview" bullet list restates entities already in the description; the bulk is efficient but these sections could be tightened.	3 / 5
Actionability	Concrete, copy-paste bash commands appear throughout (install, login, connection ensure, action list/run, request) plus a popular-actions table with real keys; minor gaps remain because run examples rely on placeholders like <actionId> and CONNECTION_ID rather than a worked end-to-end example.	4 / 5
Workflow Clarity	A clear install -> authenticate -> connect -> search -> run sequence is present, and the connection step has an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll loop and error handling; validation checkpoints for action results and destructive deletes are only implicit, leaving a minor gap.	4 / 5
Progressive Disclosure	The body is a single well-organized file with clearly headed sections and no nested references, which is appropriate for this CLI integration; the large inlined popular-actions table is reasonable but keeps it just shy of an ideal split.	4 / 5
	Total	15 / 20 Passed

Description

66%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 a clear, brand-specific niche and third-person voice, but leans on the single generic verb "Manage" and lacks trigger-term variety beyond the Ontraport brand name.

Suggestions

Replace the generic "Manage" with two or three concrete verbs (e.g., "Search, create, update, and delete contacts, deals, and tasks") to lift specificity.

Add natural trigger synonyms such as "CRM contacts," "sales pipeline," or "Ontraport API" so the skill surfaces for a wider range of phrasings users actually say.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Projects, Activities, Notes and more" lists many concrete entity types, but the only action verb is the generic "Manage", so coverage of concrete actions is limited rather than comprehensive.	3 / 5
Completeness	Both "what" ("Manage Persons, Organizations, Deals...") and "when" ("Use when the user wants to interact with Ontraport data") are present; the "when" clause is explicit but somewhat generic, so it falls short of the most concrete anchor.	4 / 5
Trigger Term Quality	"Ontraport" is the natural brand keyword a user would say, and "interact with Ontraport data" is a relevant trigger, but there are no synonyms or file/extension variations to broaden keyword coverage.	3 / 5
Distinctiveness Conflict Risk	"Ontraport integration" names a specific third-party CRM platform with a distinct brand trigger, giving it a clear niche with minimal risk of conflicting with other skills.	5 / 5
	Total	15 / 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/ontraport/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.