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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill segment-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description effectively communicates specific Segment-related capabilities with good distinctiveness due to product-specific terminology. However, it lacks explicit trigger guidance ('Use when...') and could benefit from additional natural language terms users might employ when needing Segment functionality.
Suggestions
Add a 'Use when...' clause with trigger terms like 'when the user mentions Segment, analytics tracking, customer data, or CDP'
Include common variations users might say: 'analytics', 'user tracking', 'customer data platform', 'CDP', 'event tracking'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'track events, identify users, manage groups, page views, aliases, batch operations'. These are clear, actionable capabilities within the Segment domain. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions, but lacks an explicit 'Use when...' clause. The instruction 'Always search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Segment', 'track events', 'identify users', but missing common variations users might say like 'analytics', 'user tracking', 'customer data platform', or 'CDP'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Segment', 'Rube MCP (Composio)' as unique identifiers. The specific Segment terminology (track events, identify users, aliases) creates a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of Segment operations with clear workflow structures and good organization. However, it suffers from verbosity through repeated pitfall information across sections and lacks concrete executable examples with actual JSON payloads. The content would benefit from consolidation of common pitfalls and addition of copy-paste ready API call examples.
Suggestions
Add concrete JSON payload examples for at least SEGMENT_TRACK and SEGMENT_BATCH calls instead of pseudocode descriptions
Consolidate repeated pitfalls (e.g., 'userId or anonymousId required') into a single 'Common Requirements' section to reduce redundancy
Move detailed pitfalls and naming conventions to a separate SEGMENT_REFERENCE.md file, keeping only critical warnings inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations. The pitfalls sections repeat similar information across workflows (e.g., 'userId or anonymousId required' appears multiple times), and some context like explaining what Segment is for could be trimmed since Claude knows this. | 2 / 3 |
Actionability | Provides clear tool names and parameter lists, but lacks executable code examples. The 'User Lifecycle' and 'Batch Optimization' patterns use pseudocode-style descriptions rather than actual API call examples with concrete payloads that could be copy-pasted. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with explicit steps. The Setup section has a clear 4-step verification process, and the User Lifecycle pattern shows a logical progression. The 'When to use' and 'Tool sequence' structure makes multi-step processes easy to follow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a quick reference table, but the document is quite long (200+ lines) with detailed pitfalls that could be split into a separate reference file. The external toolkit docs link is good, but more content could be offloaded. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.