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

Blog Docs Log in Get started

ongage

Ongage integration. Manage Accounts. Use when the user wants to interact with Ongage 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ongage/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 executable commands and a solid connection-readiness workflow, weakened mainly by background explanation of what Ongage is and slightly inconsistent step numbering. Trimming the intro and fixing the numbering would lift conciseness and workflow clarity.

Suggestions

Cut or condense the opening paragraph describing what Ongage is, since Claude already knows this; keep only integration-relevant context.

Fix the step numbering in the connection workflow so the referenced "Step 2" and "1b" map to a coherent 1→2→3 sequence.

Consider moving the proxy request flags table and detailed clientAction handling into a reference file to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening paragraph explaining what Ongage is ("Ongage is an email marketing platform designed for businesses to manage and automate their email campaigns…") and phrases like "so you can focus on the integration logic rather than auth plumbing" add unnecessary explanation.	3 / 5
Actionability	Copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table provide fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search→run sequence exists with state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and error-handling feedback, but step numbering is inconsistent ("1b" and a referenced "Step 2" without a clear 1/2/3).	4 / 5
Progressive Disclosure	With no bundle files, the single SKILL.md is well-organized into clearly headed sections, but at over 50 lines it does not qualify for the simple-skill 5 and could split reference material (e.g., the proxy flags table) into a separate file.	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 is third-person and explicitly includes a "Use when…" trigger tied to a specific product, but its capability statement is thin and generic. Strengthening the action list would lift specificity and completeness.

Suggestions

Replace the generic "Manage Accounts" with several concrete actions (e.g., manage lists, campaigns, templates, segments, contacts) to improve specificity.

Add natural trigger synonyms and file/term variations users might say (e.g., email lists, campaigns, segmentation) to broaden trigger coverage.

Tighten the "what" clause so the capability set is comprehensive, pushing completeness toward a 5.

Dimension	Reasoning	Score
Specificity	"Manage Accounts" is a single generic action paired with the domain name "Ongage integration", matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" ("Ongage integration. Manage Accounts.") and an explicit "when" ("Use when the user wants to interact with Ongage data.") are present; the trigger guidance is explicit but the "what" is thin, so it does not reach 5.	4 / 5
Trigger Term Quality	Relevant keywords like "Ongage", "Accounts", and "interact with Ongage data" appear, but common variations or synonyms are missing, landing between the generic and comprehensive anchors.	3 / 5
Distinctiveness Conflict Risk	"Ongage" is a specific product with a distinct trigger ("interact with Ongage data"), making it mostly distinct with only minor overlap risk against related marketing-integration skills.	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/ongage/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.