clay-incident-runbook

Execute Clay incident response procedures for enrichment failures, credit exhaustion, and data flow outages. Use when Clay enrichments stop working, webhook delivery fails, or CRM sync breaks in production. Trigger with phrases like "clay incident", "clay outage", "clay down", "clay emergency", "clay broken", "clay enrichment stopped".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A highly actionable, well-sequenced incident runbook with executable diagnostics, but it is somewhat verbose and fails to surface its own reference bundle, leaving template and remediation detail inline rather than one level deep.

Suggestions

Link references/implementation-guide.md from the body (e.g., under a 'Deeper remediation' section) and move the communication/postmortem templates there so the SKILL.md stays an overview.

Remove or merge the Error Handling table into Step 3 resolutions to eliminate the overlap and reduce tokens.

Tighten the opening overview sentence ('Clay is a hosted SaaS platform...') which restates context Claude can infer, and trim the postmortem template to essential fields.

Dimension	Reasoning	Score
Conciseness	Mostly efficient actionable tables and scripts, but the body is padded with overlapping material (an Error Handling table restates Step 3 resolutions) and verbose communication/postmortem templates that could be tightened.	2 / 3
Actionability	Provides a fully executable bash triage script with real curl probes and specific Clay UI paths ('Settings > Plans & Billing > Credit balance', 'Table > + Add > Webhooks') — copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced Step 1–5 process with a decision tree, severity-tiered response times, and explicit verify/test checkpoints ('Verify: Send test payload to new webhook URL').	3 / 3
Progressive Disclosure	Sections are well organized, but a bundle file (references/implementation-guide.md) exists and is never linked or signaled from the body, and template content that could live in that reference is kept inline.	2 / 3
	Total	10 / 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 well-crafted description: third-person voice, explicit 'Use when' guidance, concrete incident scenarios, and a strong set of natural trigger phrases scoped to a distinct Clay-incident niche.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Execute Clay incident response procedures') tied to specific scenarios — 'enrichment failures, credit exhaustion, and data flow outages' — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what (execute incident response procedures) and when via an explicit 'Use when Clay enrichments stop working, webhook delivery fails, or CRM sync breaks' clause.	3 / 3
Trigger Term Quality	Lists natural phrases a user would actually say ('clay incident', 'clay outage', 'clay down', 'clay broken', 'clay enrichment stopped') with good variation coverage.	3 / 3
Distinctiveness Conflict Risk	A clear Clay-incident niche with distinctive triggers ('clay outage', 'clay down') unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

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