customerio-cost-tuning

Optimize Customer.io costs and usage efficiency. Use when reducing profile count, cleaning inactive users, deduplicating events, or right-sizing your plan. Trigger: "customer.io cost", "reduce customer.io spend", "customer.io billing", "customer.io pricing", "customer.io cleanup".

Quality

82%

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

65%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 body is actionable and well-organized with concrete code, but it is somewhat verbose, omits validation checkpoints around the destructive batch delete, and fails to link its existing reference bundle files.

Suggestions

Add an explicit validation checkpoint before the destructive suppress+delete in Step 2 (e.g., require a non-dry-run confirmation flag and verify profile count dropped afterward) to lift workflow clarity.

Reference the existing references/implementation-guide.md and references/implementation.md from the body, or move the inline scripts into those files and link to them, so the bundle is one level deep and discoverable.

Trim restating comments and consider shortening the inline script blocks to only the essential, executable portions to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Five full inline TypeScript scripts (~200 lines) are mostly efficient, but explanatory comments like "Audit your Customer.io integration for cost optimization opportunities" restate what the code shows and the volume could be tightened.	2 / 3
Actionability	Provides concrete, mostly executable TypeScript using real customerionode calls with env config, rate limiting, and dry-run; examples are close to copy-paste ready despite a commented-out SQL target stub in Step 2.	3 / 3
Workflow Clarity	Steps are clearly sequenced with dry-run and error counting, but the destructive batch suppress+delete in Step 2 lacks an explicit validate-before-execute checkpoint or post-run verification, which caps batch/destructive workflows at 2.	2 / 3
Progressive Disclosure	The body is well-sectioned but the two bundle files in references/ (implementation-guide.md, implementation.md) are never referenced or signaled from the body, leaving orphaned references and inline content that could be split out.	2 / 3
	Total	9 / 12 Passed

Description

100%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 concise, concrete, and answers both what the skill does and when to use it with natural trigger phrases. It is a strong, low-conflict trigger description.

Dimension	Reasoning	Score
Specificity	Names four concrete actions — "reducing profile count, cleaning inactive users, deduplicating events, or right-sizing your plan" — matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states both what (optimize costs via named actions) and when ("Use when..." clause plus a Trigger list), satisfying the full what-and-when anchor.	3 / 3
Trigger Term Quality	Provides five natural trigger phrases ("customer.io cost", "reduce customer.io spend", "customer.io billing", "customer.io pricing", "customer.io cleanup") that users would realistically say.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Customer.io cost tuning with niche-specific triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	12 / 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: 3 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/customerio-pack/skills/customerio-cost-tuning/SKILL.md
Commit: 0540a62

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.