setup-outreach-campaign-smartlead

Set up a complete outbound email campaign in Smartlead. Asks the user for campaign goal, audience, messaging, schedule, and mailbox allocation. Creates the campaign, adds leads, saves email sequences, sets schedule, and assigns available mailboxes. Use when a user wants to launch email outreach via Smartlead.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

77%

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 concrete API calls and well-sequenced validation checkpoints, but it carries some redundancy (a duplicate endpoint table) and keeps a sizable reference section inline rather than splitting it out.

Suggestions

Move the 'Smartlead API Reference' endpoint table into a separate references file (e.g., references/api-reference.md) since the procedure already demonstrates each call inline, reducing duplication.

Trim or drop the 'Example Prompts' section, which adds tokens without improving actionability beyond the description's trigger clause.

Consider extracting the lead field-mapping rules (4a) into a reference doc so the main procedure stays lean while retaining the detail.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the inline 'Smartlead API Reference' table duplicates the endpoint calls already shown in the procedure and the 'Example Prompts' section is light padding.	2 / 3
Actionability	Provides concrete HTTP methods, full URLs, JSON request/response bodies, field mappings, batching limits, and defaults — copy-paste ready throughout.	3 / 3
Workflow Clarity	A clear 7-step sequence with explicit validation checkpoints (lead dedup/report in 4b, sequence approval in Step 5, confirm-before-start in Step 7) covering the batch lead-upload operation.	3 / 3
Progressive Disclosure	Single ~380-line file with no bundle files; sections are well-organized but the large inline API reference table is content that could live in a separate reference file rather than 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.

The description is specific, uses natural trigger language, and explicitly covers both capability and use-when guidance in third person. It is a strong, well-distinguished skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Creates the campaign, adds leads, saves email sequences, sets schedule, and assigns available mailboxes' — plus the inputs it collects, matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what (full campaign setup with enumerated actions) and when via the 'Use when a user wants to launch email outreach via Smartlead' trigger clause.	3 / 3
Trigger Term Quality	Uses natural terms a user would say — 'outbound email campaign', 'email outreach', 'launch email outreach via Smartlead' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to Smartlead outbound email campaigns with a distinct trigger; unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/outreach/capabilities/setup-outreach-campaign-smartlead/SKILL.md
Commit: 8866b2a

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.