action-creator

Creates user-specific one-click action templates that execute email operations when clicked in the chat interface. Use when user wants reusable actions for their specific workflows (send payment reminder to ACME Corp, forward bugs to engineering, archive old newsletters from specific sources).

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

65%

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 with complete, executable TypeScript examples and a clear API surface, but it is held back by redundant sections, missing validation checkpoints for batch/destructive email operations, and a largely monolithic structure with broken or absent bundle references.

Suggestions

Merge the duplicate "Creating an Action Template" and "Creating the File" sections, and fold "Parameter Schema Guidelines" into the single template example to remove redundancy.

Add explicit validation/preview checkpoints before destructive or batch operations (e.g., show the user a count and sample of matched emails before bulk archive, and preview the composed email before sending).

Move the large "Available Context Methods" API reference into a separate reference file linked from SKILL.md, and either ship the referenced template files under a bundle directory or remove the links to non-existent paths.

Dimension	Reasoning	Score
Conciseness	Most content is domain-specific and useful, but there is notable redundancy: "Creating an Action Template" and "Creating the File" cover the same steps, and the parameter schema appears both in the main template and again in a separate "Parameter Schema Guidelines" section. Not a 3 because it could be tightened; not a 1 because it avoids explaining basic concepts Claude already knows.	2 / 3
Actionability	It provides a full, copy-paste-ready TypeScript template, concrete ActionContext method signatures, and several complete worked patterns (send, bulk archive, AI analysis, forward-and-label), all executable rather than pseudocode.	3 / 3
Workflow Clarity	A sequenced creation process exists ("Creating an Action Template" steps 1-4), but for destructive/batch email operations (bulk archive, sending emails) there are no explicit validation or preview/confirmation checkpoints before execution, capping this at 2 per the batch-operations guideline.	2 / 3
Progressive Disclosure	Sectioning is present and a couple of references are signaled (template links, ACTIONS_SPEC.md), but the large inline "Available Context Methods" API reference and duplicated guidance are content that could live in a separate reference file, and the referenced template files do not exist in any bundle directory.	2 / 3
	Total	9 / 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.

The description is concise, third-person, and answers both what and when with concrete, natural-language examples. It is clearly scoped to a distinct niche with minimal conflict risk.

Dimension	Reasoning	Score
Specificity	"Creates user-specific one-click action templates that execute email operations" names a concrete capability, and the parenthetical lists multiple specific actions ("send payment reminder to ACME Corp", "forward bugs to engineering", "archive old newsletters"), matching the multiple-concrete-actions anchor.	3 / 3
Completeness	It states what the skill does ("Creates user-specific one-click action templates that execute email operations when clicked in the chat interface") and gives an explicit when via "Use when user wants reusable actions...", satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	"Use when user wants reusable actions for their specific workflows (send payment reminder to ACME Corp, forward bugs to engineering, archive old newsletters from specific sources)" uses natural phrasings a user would actually say, giving good coverage of trigger terms.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply scoped to user-specific one-click chat email actions, with example triggers tied to particular vendors/sources, making it 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
relative_links	Relative link issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: anthropics/claude-agent-sdk-demos
Path: email-agent/agent/.claude/skills/action-creator/SKILL.md
Commit: 826b268

Reviewed: about 17 hours 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.