Name: segmetrics
Rating: 64 (1 reviews)
Author: membranedev

segmetrics

SegMetrics integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with SegMetrics data.

Quality

76%

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/segmetrics/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.

A highly actionable CLI integration skill with executable commands and a solid connection-state workflow, weakened mainly by marketing-style padding in the intro and a bare overview outline that add tokens without guidance.

Suggestions

Remove the marketing-style intro ("helps businesses track and analyze their marketing campaigns... used by marketers and data analysts...") — Claude needs operational steps, not SegMetrics' value proposition.

Cut or flesh out the bare "SegMetrics Overview" bullet outline (Contacts/Tags/Reports/Account/Integrations), which currently adds structure without any actionable content.

Replace the dangling "Step 2" reference with an explicit numbered sequence (connect → wait for READY → search actions → run) so the end-to-end flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean, executable CLI reference, but the opening marketing paragraph ("helps businesses track and analyze their marketing campaigns... used by marketers and data analysts to understand customer behavior") and the bare "SegMetrics Overview" bullet outline explain value/context Claude does not need, so it is mostly efficient with some unnecessary padding.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands across install, login (including headless), connection ensure, polling, action list/run with JSON input, and proxy requests, plus a complete proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-then-re-poll feedback loop, but the dangling "Step 2" reference and un-numbered section flow leave a minor gap versus an explicit step list.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections with no nested references and no bundle files to navigate, appropriate for a single-file CLI integration skill; only minor organization gaps (e.g. the inline clientAction breakdown) keep it from a 5.	4 / 5
	Total	16 / 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 strong, third-person description that names the platform and a broad set of entity types to manage, with an explicit Use-when trigger. Its main limitation is the generic single verb "Manage" and a fairly broad when-clause that lack concrete trigger phrases.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" lists several concrete entity-level actions, but the single generic verb "Manage" leaves minor coverage gaps versus a 5-anchor that would enumerate distinct operations per entity.	4 / 5
Completeness	It answers both what ("Manage Persons, Organizations, Deals, Leads, Projects, Activities and more") and when ("Use when the user wants to interact with SegMetrics data"), but the when-clause is somewhat generic rather than listing concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Natural terms like "SegMetrics data", "Leads", and "Deals" appear and would be said by users, but common synonyms and surface variations (e.g. "contacts", "reporting", file/record types) are not covered, stopping short of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"SegMetrics integration" names a specific platform with distinct triggers ("interact with SegMetrics data"), giving it a clear niche with 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/segmetrics/SKILL.md
Commit: f484c82

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