Skills segment-automation

📦

segment-automation

Name: segment-automation
Author: sickn33

Content revision r1 Safe ⚙️ External commands🌐 Network access

Automate Segment Analytics Workflows

Segment tracking work requires precise schemas and identity rules. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows for events, users, groups, pages, aliases, and batches.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "segment-automation" from https://skillstore.io/skills/sickn33-segment-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-segment-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-segment-automation.md Signed manifest GET /api/skills/sickn33-segment-automation/manifest Signed lockfile GET /api/skills/sickn33-segment-automation/lockfile

Test it

Using "segment-automation". Track an Order Completed event for a known user.

Expected outcome:

The skill searches the current Segment schema, confirms required identity and event fields, and prepares a track call with approved properties.

Using "segment-automation". Import a week of signup and page events.

Expected outcome:

The skill recommends a batch workflow, checks each message type, includes historical timestamps, and flags missing identifiers before submission.

Using "segment-automation". Merge anonymous activity after signup.

Expected outcome:

The skill explains the one-way alias step, then suggests identify and track calls using the new user identifier.

Security Audit

Safe

v6 • 7/9/2026 Open versioned report

Most static findings are false positives caused by Markdown backticks around tool names, parameter names, and example fences. I found no actual shell execution, prompt injection, or system reconnaissance instructions. The Rube MCP URL is a low-severity external service dependency because it changes the trust boundary for Segment data.

Files scanned

226

Lines analyzed

Review items

False positives ignored

Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Low

SKILL.md:20

Hardcoded URL

**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API k

The skill asks users to add https://rube.app/mcp as an MCP server, which creates an external service dependency for Segment operations. This is legitimate setup guidance but still changes the trust boundary for customer data.

Risk Factors

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sickn33-segment-automation/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-segment-automation/security.svg)](https://skillstore.io/skills/sickn33-segment-automation?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-segment-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-segment-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-segment-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). segment-automation security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-segment-automation/audits/6

BibTeX citation

@techreport{sickn33-sickn33-segment-automation-2026,
  author = {sickn33},
  title = {segment-automation security audit report (audit version 6)},
  institution = {Skillstore},
  year = {2026},
  number = {6},
  url = {https://skillstore.io/skills/sickn33-segment-automation/audits/6},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "segment-automation security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
  - name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-segment-automation/audits/6"
identifiers:
  - type: other
    value: "skillstore:sickn33-segment-automation:audit:6"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Instrument Product Events

Send consistent track calls for key user actions after confirming the current Segment tool schema.

Maintain User Profiles

Identify users, update traits, and connect users to organizations with clear identity requirements.

Import Historical Activity

Prepare batch calls with timestamps and message types for efficient backfills into Segment.

Try These Prompts

Check Segment Readiness

Confirm Rube MCP is available, search for current Segment tool schemas, and tell me whether my Segment connection is active.

Track One Event

Use the current Segment schema to prepare a track call for a signed-in user event. Include required fields and note any missing values.

Update Identity And Group

Identify this user with approved traits, then associate the user with a group. Validate identifiers before sending either call.

Plan A Batch Backfill

Design a Segment batch operation for historical events, identifies, pages, and aliases. Check schema limits and list validation risks first.

Best Practices

Search current Rube MCP tool schemas before each workflow.
Use stable event names, trait names, and property names across sources.
Review privacy rules before sending traits, context, or identifiers.

Avoid

Do not send Segment calls without a userId or anonymousId.
Do not alias the same identity pair repeatedly.
Do not update source configuration without reviewing collection impact.

Frequently Asked Questions

Does this skill require a Segment connection?

Yes. Rube MCP must be connected, and the Segment toolkit connection must be active.

Can it send batch events?

Yes. It describes Segment batch workflows for track, identify, group, page, and alias messages.

Does it manage downstream destinations?

No. It focuses on Segment calls and source settings, not destination configuration.

How does it handle tool schemas?

It instructs the assistant to search Rube MCP tools first so current schemas are used.

Can it help with identity resolution?

Yes. It explains userId, anonymousId, identify, group, and alias usage patterns.

Should I send personal data through it?

Only send approved data. Confirm consent, destination settings, and company privacy rules first.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/segment-automation

Ref

26421118b848d9f1efc0aa169d8a7a9e7e0a877e

Maintenance freshness

7/18/2026

Usage

8 downloads · 87 views

File structure

📄 SKILL.md