AC cold-outbound-optimizer
Design, analyze, and optimize cold outbound email campaigns for Instantly. Handles end-to-end ICP definition, expert panel scoring (recursive to 90+), sequence copywriting, infrastructure audit, capacity planning, and implementation docs. Use when asked to build cold outbound sequences, optimize cold email, analyze outbound campaigns, build sales sequences, build Instantly sequences, create cold outbound strategies, or design email campaigns. Supports both "start from scratch" and "optimize existing" modes.
Design, analyze, and optimize cold outbound email campaigns for Instantly.
As a process C 51/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvREADME.md:60Reads a .env file (documentation of a security skill)cp .env.example .env
security skill
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (cold-outbound-optimizer) differs from the folder (outbound-engine)
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 85Steps. 46 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1576 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 512: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 46 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 99.