Execute Instantly primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "instantly main workflow", "primary task with instantly".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill instantly-core-workflow-a68
Quality
29%
Does it follow best practices?
Impact
95%
1.58xAverage score across 6 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/instantly-pack/skills/instantly-core-workflow-a/SKILL.mdThree-step workflow and npm-only tooling
Initialize phase present
0%
100%
Execute phase present
0%
100%
Finalize phase present
0%
100%
Correct phase order
0%
100%
TypeScript implementation
100%
100%
npm package.json present
100%
100%
npm start script
100%
100%
No non-npm bash invocations
100%
100%
Instantly API referenced
100%
100%
Phase documentation in README
0%
100%
Without context: $0.4264 · 2m 4s · 20 turns · 27 in / 7,569 out tokens
With context: $0.5278 · 2m 36s · 26 turns · 65 in / 7,650 out tokens
Output format and error handling structure
Workflow execution in result
100%
100%
Instantly API data in result
100%
100%
Success confirmation in result
100%
100%
Error details in result
100%
100%
Error table in errors.md
0%
50%
Multiple error rows
0%
100%
TypeScript with type annotations
100%
100%
Result written to file
100%
100%
Both success and error paths
100%
100%
npm-only shell commands
100%
100%
Without context: $0.3113 · 1m 54s · 15 turns · 63 in / 6,575 out tokens
With context: $0.5662 · 2m 31s · 25 turns · 33 in / 9,183 out tokens
Prerequisite verification and resource guidance
instantly-install-auth mentioned
0%
100%
Prerequisites section present
100%
100%
API credentials requirement
100%
100%
Three-phase workflow described
50%
100%
Instantly Documentation URL
0%
100%
Instantly API Reference URL
50%
100%
Checklist is actionable
100%
100%
Next workflow mentioned
0%
100%
Workflow section in ONBOARDING
100%
100%
Step-by-step setup instructions
100%
100%
Without context: $0.6461 · 2m 42s · 26 turns · 305 in / 7,693 out tokens
With context: $0.3027 · 1m 21s · 16 turns · 22 in / 4,009 out tokens
TypeScript types and npm module structure
TypeScript main file
100%
100%
Separate types file
100%
100%
Initialize phase in module
80%
100%
Execute phase in module
30%
100%
Finalize phase in module
0%
80%
Instantly API shape typed
100%
100%
npm package.json present
100%
100%
No non-npm package managers
100%
100%
Phases ordered correctly
37%
100%
Typed function parameters
100%
100%
Instantly API referenced
100%
100%
Without context: $0.4793 · 2m 13s · 23 turns · 78 in / 8,495 out tokens
With context: $0.5070 · 2m 6s · 23 turns · 28 in / 7,915 out tokens
npm-only execution and workflow output structure
Three-phase runner structure
30%
100%
Workflow execution field in output
100%
100%
Instantly API results field in output
100%
77%
Success/error confirmation in output
100%
55%
Error table in error-log
0%
75%
Multiple error rows
0%
100%
npm start script
100%
100%
No non-npm shell invocations
100%
100%
Output written to file
100%
100%
TypeScript implementation
100%
100%
Instantly API referenced
100%
100%
Without context: $0.4399 · 2m 1s · 22 turns · 29 in / 7,496 out tokens
With context: $0.5018 · 2m 23s · 26 turns · 301 in / 7,196 out tokens
Resource references and next-workflow handoff
Instantly Documentation URL
0%
100%
Instantly API Reference URL
22%
100%
instantly-install-auth prerequisite
0%
100%
API credentials requirement
100%
100%
Three-phase workflow described
0%
100%
instantly-core-workflow-b next step
0%
100%
Checklist items actionable
100%
100%
Prerequisites section in OVERVIEW
100%
100%
Resources section in OVERVIEW
0%
0%
Primary workflow context
0%
100%
Instantly concepts explained
28%
100%
Without context: $0.5463 · 2m 59s · 33 turns · 132 in / 8,541 out tokens
With context: $0.4794 · 2m 4s · 25 turns · 31 in / 6,517 out tokens
Table of Contents
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.