Name: segment
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

segment

Segment integration. Manage Workspaces. Use when the user wants to interact with Segment data.

Quality

70%

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/segment/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 content is highly actionable with executable commands, clear state-driven connection flow, and good section structure. Its main weaknesses are a redundant introductory paragraph explaining what Segment is and broken cross-references in the connection workflow.

Suggestions

Cut or condense the opening paragraph explaining what Segment is and who uses it; Claude already knows the Segment product, so the context budget is better spent on integration specifics.

Fix the broken step cross-references: either label the steps consistently (Step 1 / Step 2, and '1a' before '1b') or reword 'skip to Step 2' to point at the actual section ('Searching for actions').

Consider moving the full 'Popular actions' table into a one-level-deep reference file (e.g., ACTIONS.md) and keeping only a representative subset inline, to tighten the main SKILL.md and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Segment is a customer data platform that helps businesses collect, clean, and control their customer data...") explains a concept Claude already knows, and phrases like "so you can focus on the integration logic rather than auth plumbing" pad otherwise efficient material, fitting the 'mostly efficient but includes some unnecessary explanation' anchor; it is not a 4 because the redundant intro is a clear trimming opportunity.	3 / 5
Actionability	The body gives copy-paste-ready commands (membrane connection ensure, action list/run, request) with real flags and a concrete actions table, matching the 'fully executable; copy-paste ready; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), but cross-references are broken ('skip to Step 2' with no labeled Step 2, '1b' with no '1a'), matching the 'clear sequence with most checkpoints present; minor gaps' anchor rather than 5.	4 / 5
Progressive Disclosure	With no bundle files present, the ~160-line body is well-organized into clear sections and stays self-contained, but everything (including the 20-row actions table) is inlined with no split into one-level-deep reference files, matching the 'good structure; most content appropriately placed; minor organization gaps' anchor rather than 5.	4 / 5
	Total	16 / 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 niche and distinct triggers, but the 'what' names only one action and the trigger language is generic. Tightening it to list concrete Segment objects (sources, destinations, tracking plans) would lift specificity and completeness.

Suggestions

Expand the 'what' beyond 'Manage Workspaces' to mention the core objects the skill handles (e.g., sources, destinations, tracking plans, warehouses) so capability coverage reads as comprehensive.

Make the 'when' trigger more concrete by naming Segment-specific terms a user would naturally say, e.g., 'Use when managing Segment sources, destinations, tracking plans, or warehouses.'

Add a natural synonym or file/URL signal (e.g., 'segment.com data') to broaden trigger-term coverage beyond the single product name.

Dimension	Reasoning	Score
Specificity	"Manage Workspaces" names the domain (Segment) plus one concrete action, matching the '1-2 concrete actions but not comprehensive' anchor; it is not a 4 because only a single action is named rather than several.	3 / 5
Completeness	It states both a 'what' ("Segment integration. Manage Workspaces.") and a 'when' ("Use when the user wants to interact with Segment data"), matching the 'has both what and when; when could be more explicit' anchor; it falls short of 5 because the trigger phrase is generic rather than listing concrete Segment-specific triggers.	4 / 5
Trigger Term Quality	"Segment", "Segment data", and "Workspaces" are relevant keywords a user might say, but common variations or synonyms are missing, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of a 4.	3 / 5
Distinctiveness Conflict Risk	"Segment integration" and "interact with Segment data" target a clear niche (a named CDP product) with distinct triggers and minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	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/segment/SKILL.md
Commit: f484c82

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