customerio-install-auth

Install and configure Customer.io SDK/CLI authentication. Use when setting up a new Customer.io integration, configuring API keys, or initializing Customer.io in your project. Trigger: "install customer.io", "setup customer.io", "customer.io auth", "configure customer.io API key", "customer.io credentials".

Quality

91%

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

Quality

Content

92%Weight 40%Scale 1-3

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

The content is a strong, actionable install/auth guide with executable code, a clear sequenced workflow, and a validation step plus error-recovery table. The main weakness is progressive disclosure: a references bundle file exists but is orphaned (unlinked) and duplicates the body rather than extending it.

Suggestions

Either link references/implementation-guide.md from the body for advanced/multi-language setup, or remove it if the body is meant to be self-contained — currently it is an unreferenced duplicate.

If keeping the guide, move the Node-vs-Python and @customerio/track variant details (which the guide contains) into it and have SKILL.md point there, giving the overview a genuine one-level-deep reference.

Add a one-line pointer near the top (e.g. 'For Python or Journeys Track SDK variants, see implementation-guide.md') so the bundle file is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean technical instruction with no padding explaining concepts Claude already knows; every section (prerequisites, clients table, code, error table, security) earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands and TypeScript (npm install, env vars, singleton clients, a runnable verify script) with specific details like region constants and base URLs.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with an explicit validation checkpoint (Step 5: Verify Connection) and an error-handling table that supplies feedback for recovery on 401, region mismatch, ENOTFOUND, etc.	3 / 3
Progressive Disclosure	The body is well-sectioned but the provided bundle file references/implementation-guide.md is never linked or signaled from the body and largely duplicates the inline content, so the deeper material is neither navigated to nor usefully separated.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 is well-constructed: it pairs a clear capability statement with an explicit 'Use when' clause and a list of natural trigger phrases scoped to a distinct niche. The only minor weakness is specificity, which states two actions rather than enumerating several concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ("Customer.io SDK/CLI authentication") and two actions ("Install and configure"), but does not enumerate multiple distinct concrete actions like the level-3 anchor does.	2 / 3
Completeness	Clearly answers both what ("Install and configure Customer.io SDK/CLI authentication") and when ("Use when setting up a new Customer.io integration, configuring API keys..."), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Explicit Trigger list ("install customer.io", "setup customer.io", "customer.io auth", "configure customer.io API key", "customer.io credentials") covers natural phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to a specific SaaS (Customer.io) with distinct install/auth triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/customerio-pack/skills/customerio-install-auth/SKILL.md
Commit: 4c47e33

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