CtrlK
BlogDocsLog inGet started
Tessl Logo

segment-automation

Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.

78

1.16x
Quality

68%

Does it follow best practices?

Impact

98%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/segment-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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-organized, actionable MCP skill body whose main weaknesses are redundant pitfall repetition and missing validation/feedback loops for batch and irreversible alias operations. Tightening duplication and adding error-recovery steps would move it up a band.

Suggestions

Consolidate the repeated userId/anonymousId requirement and the "Known Pitfalls" section into one identity/data-quality reference to remove duplication.

Add a validation and retry loop for batch operations (e.g., on individual message errors: log failed indices, fix payloads, resend only failures).

Add a pre-flight check before the irreversible ALIAS call (verify previousId and userId are correct and the merge is intended) since it cannot be undone.

DimensionReasoningScore

Conciseness

The structure is mostly efficient, but the userId/anonymousId requirement is repeated across five workflow sections and the "Known Pitfalls" section restates identity, timestamp, rate-limit, and response-parsing pitfalls already covered per workflow.

3 / 5

Actionability

Concrete tool sequences with exact slugs (SEGMENT_TRACK, SEGMENT_BATCH), named parameters, format examples ('2024-01-15T10:30:00Z'), and a quick-reference table make guidance mostly executable; only example call payloads are missing.

4 / 5

Workflow Clarity

Setup has a validation checkpoint ("Confirm connection status shows ACTIVE"), but batch workflows and the irreversible ALIAS operation lack validation and error-recovery loops — the rubric caps batch/destructive skills without validation at 3.

3 / 5

Progressive Disclosure

Good structure with clear section headers, a quick-reference table, an external toolkit-docs link, and dynamic schema discovery delegated to RUBE_SEARCH_TOOLS; minor gaps in that per-workflow detail could be split into reference files.

4 / 5

Total

14

/

20

Passed

Description

75%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 specific, well-scoped description with comprehensive concrete actions and strong distinctiveness, held back by a missing explicit 'when to use' trigger clause and a few absent natural synonyms. Adding a 'Use when...' clause would lift it to the top band.

Suggestions

Append an explicit trigger clause, e.g., "Use when the user mentions Segment, event tracking, identifying users, or sending analytics/customer data to Segment."

Add natural synonyms users might say, such as "Segment.com", "CDP", "traits", or "user profiles", to broaden trigger coverage.

Drop or shorten the procedural "Always search tools first" sentence — it belongs in the body's workflow steps, not the description.

DimensionReasoningScore

Specificity

Enumerates six concrete actions ("track events, identify users, manage groups, page views, aliases, batch operations") covering the Segment domain comprehensively, matching the score-5 anchor's multi-action coverage.

5 / 5

Completeness

The 'what' is explicit and concrete, but there is no 'Use when...' clause or equivalent trigger guidance — the closing sentence about searching tools is procedural, not a usage trigger, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would say ("track events", "identify users", "groups", "aliases", "batch") but misses common variations such as "Segment.com", "CDP", "traits", or "event tracking".

4 / 5

Distinctiveness Conflict Risk

Names a specific product and integration ("Segment", "Rube MCP (Composio)") with distinct action terms, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
Reviewed

Table of Contents

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.