segment-cdp

Client-side tracking with Analytics.js. Include track, identify, page, and group calls. Anonymous ID persists until identify merges with user.

Quality

38%

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/segment-cdp/SKILL.md

Quality

Content

18%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a skeleton or template with no actionable content. It lists topics (Analytics.js, server-side tracking, tracking plans) and anti-patterns without providing any concrete code, commands, or implementation details. The Sharp Edges table is entirely placeholder content with generic 'Issue' entries and unhelpful 'See docs' solutions.

Suggestions

Add executable code examples for each pattern (e.g., analytics.track(), analytics.identify() calls with realistic properties)

Replace the placeholder Sharp Edges table with actual issues, specific severity levels, and concrete solutions or code fixes

Add concrete anti-pattern examples showing the wrong code alongside the correct approach

Include a workflow for implementing Segment tracking (e.g., install snippet → identify user → track events → verify in debugger)

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes placeholder/template content (the Sharp Edges table with generic 'Issue' and 'See docs' entries, and the boilerplate 'When to Use' section) that adds no value. The patterns section is concise but lacks substance.	3 / 5
Actionability	There is no concrete code, no executable examples, no specific commands, and no actual implementation guidance. The content only describes what things are at a high level without showing how to do anything.	1 / 5
Workflow Clarity	There are no steps, no sequences, no validation checkpoints, and no workflow of any kind. The content is purely descriptive headers and placeholder tables with no process guidance.	1 / 5
Progressive Disclosure	The content has section headers providing some structure, but there are no references to external files, no links to detailed documentation, and no bundle files to support deeper exploration. The Sharp Edges table references 'See docs' without any actual links.	2 / 5
	Total	7 / 20 Passed

Description

58%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 does a reasonable job listing specific Analytics.js capabilities (track, identify, page, group calls) and includes a useful behavioral detail about anonymous ID merging. However, it lacks an explicit 'Use when...' clause, which is critical for skill selection, and misses common synonyms like 'Segment' that users would naturally use.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about client-side event tracking, Segment Analytics.js integration, or implementing track/identify/page/group calls.'

Include common synonyms and related terms like 'Segment', 'event tracking', 'user identification', 'JavaScript analytics', and 'client-side analytics' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific actions (track, identify, page, group calls) and mentions a concrete behavior (anonymous ID persistence until identify merges). Minor gaps in coverage—doesn't mention initialization, configuration, or other Analytics.js features.	4 / 5
Completeness	The 'what' is reasonably clear—client-side tracking with specific API calls. However, there is no explicit 'when' clause (e.g., 'Use when...'). The absence of a 'when' clause caps this at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Includes relevant terms like 'Analytics.js', 'track', 'identify', 'page', 'group calls', and 'Anonymous ID', but misses common user phrases like 'Segment', 'event tracking', 'user analytics', 'client-side analytics', or 'JavaScript tracking'. Users might say 'Segment tracking' rather than 'Analytics.js'.	3 / 5
Distinctiveness Conflict Risk	Specifying 'Analytics.js' and the specific call types (track, identify, page, group) makes it fairly distinct from generic analytics or server-side tracking skills. Minor overlap risk with broader analytics or Segment-related skills.	4 / 5
	Total	14 / 20 Passed

Validation

90%

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 — 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

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/segment-cdp/SKILL.md
Commit: 57c135b

Reviewed: 1 day 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.