CtrlK
BlogDocsLog inGet started
Tessl Logo

instantly-core-workflow-a

Build and launch an Instantly.ai cold email campaign end-to-end. Use when creating campaigns, adding leads, configuring sequences, and launching outreach via the Instantly API v2. Trigger with phrases like "instantly campaign", "launch instantly campaign", "create instantly outreach", "instantly cold email", "instantly send campaign".

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/instantly-pack/skills/instantly-core-workflow-a/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

Highly actionable and well-sequenced, but held back by verbosity, missing pre-launch validation for a batch/destructive operation, and a monolithic structure with no progressive disclosure to separate reference files.

Suggestions

Add explicit validation checkpoints before launch (verify leads imported, verify at least one warmed-up account assigned, confirm campaign is not already active) with a fix-and-retry loop, raising workflow_clarity past the batch-operation cap.

Move the endpoint and error-handling tables plus the full multi-variant sequence template into a references/ file (e.g. ENDPOINTS.md), keeping SKILL.md a concise overview with one-level-deep links.

Trim the full email subject/body copy variants and console.log lines to minimal representative examples to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is mostly executable code with useful inline comments, but full multi-variant email subject/body copy blocks and console.log lines add padding that doesn't teach Claude anything new.

3 / 5

Actionability

Fully executable, copy-paste-ready TypeScript across all four steps with concrete payloads, a main() pipeline, sample lead data, and an endpoint reference table covering the common cases.

5 / 5

Workflow Clarity

The four-step sequence is clear and orchestrated in main(), but for a batch cold-email/lead-import operation there is no validate-before-launch checkpoint or fix-retry feedback loop, which caps this dimension at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the full endpoint table, error table, and large code blocks are all inlined in one monolithic SKILL.md; section headers provide some structure, but content that should be split into a reference file is inline.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

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, well-targeted description that clearly states capability, use-conditions, and concrete trigger phrases with low conflict risk. Minor improvement possible by broadening trigger-term synonyms.

DimensionReasoningScore

Specificity

"Build and launch an Instantly.ai cold email campaign end-to-end" plus "creating campaigns, adding leads, configuring sequences, and launching outreach" lists several concrete actions with only minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ("Build and launch an Instantly.ai cold email campaign end-to-end") and when ("Use when creating campaigns..."), reinforced by explicit "Trigger with phrases like..." guidance.

5 / 5

Trigger Term Quality

Trigger phrases like "instantly campaign", "instantly cold email", and "create instantly outreach" give good natural keyword coverage, though a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

The Instantly.ai cold-email niche with product-prefixed triggers ("instantly campaign", "launch instantly campaign") keeps conflict risk with other skills minimal.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

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.