CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is highly actionable and well sequenced with executable code and a built-in verification feedback loop, so conciseness, actionability, and workflow clarity are strong. Progressive disclosure is the weak spot: the implementation-guide.md bundle file is orphaned (not referenced from the body) and duplicates the body rather than extending it one level deep.

Suggestions

Link references/implementation-guide.md from the body (e.g., a "## Advanced setup" section pointing to it) so the bundle file is clearly signaled and discoverable.

De-duplicate: keep the body as a concise overview (install + both clients + verify) and move the extended Python/Journeys-track examples and alternate setup into implementation-guide.md rather than repeating material.

Collapse the duplicated region-selection logic (getRegion() in Step 3 vs. inline ternary in Step 4) into one shared helper to tighten the body.

DimensionReasoningScore

Conciseness

The body is lean and focused — concrete install/env/client code, comparison tables, and an error table with no padding about general concepts Claude already knows; the only minor redundancy (region logic restated in Steps 3 and 4) does not rise to verbosity.

3 / 3

Actionability

Fully executable, copy-paste-ready guidance: `npm install customerio-node`, env-var blocks, complete TrackClient/APIClient TypeScript singletons, and a verify script with its run command `npx tsx scripts/verify-customerio.ts`.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced and Step 5 is an explicit validation checkpoint whose try/catch exits non-zero on failure, with the Error Handling table providing a fix-and-retry feedback loop.

3 / 3

Progressive Disclosure

Sections are well organized, but the bundled references/implementation-guide.md is never linked or signaled from the body and largely duplicates the body content, fitting the level-2 anchor of a reference present but not clearly signaled with content that should be split.

2 / 3

Total

11

/

12

Passed

Description

100%

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 strong description: it names concrete install/configure actions, gives an explicit Use-when clause plus a dedicated trigger list, and occupies a clear niche. The "Use when ..." phrasing follows the accepted third-person imperative pattern shown in the good examples, so no voice penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Install and configure Customer.io SDK/CLI authentication", "setting up a new Customer.io integration", "configuring API keys", "initializing Customer.io in your project" — matching the level-3 anchor of multiple specific actions.

3 / 3

Completeness

Clearly states what ("Install and configure Customer.io SDK/CLI authentication") and when ("Use when setting up a new Customer.io integration, configuring API keys, or initializing Customer.io in your project") with explicit triggers, satisfying both halves.

3 / 3

Trigger Term Quality

An explicit Trigger clause gives natural phrasings a user would say — "install customer.io", "setup customer.io", "customer.io auth", "configure customer.io API key", "customer.io credentials" — with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Customer.io install/auth is a narrow niche with distinct, product-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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