skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
victor-shulga/outbound-engine-skills67 installs

ps-line-generator

Use when asked to write a PS line, add a pattern interrupt to an email, or improve the bottom of a cold email sequence

How do I install this agent skill?

npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill ps-line-generator
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions for an AI to generate personalized email postscripts (P.S. lines). It is entirely descriptive, containing no code, network operations, or sensitive data access.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

PS Line Generator

Write a PS line for a cold email — the most-read part of a long email and the last thing they see in a short one.

What you need

  • Email body (step the PS line will be added to)
  • ICP and persona
  • Signal and hypothesis context
  • What the PS line should achieve (options below)

PS line goals (pick one per email)

Social proof — reference a result, client, or outcome that's relevant to this persona Relevance signal — name something specific about their company that shows you did research Urgency/timing — reference a real reason now is the right moment Curiosity — introduce a second angle that makes them want to reply to find out more De-risk — remove the fear of commitment ("this isn't a pitch, just a question")

Rules

  • PS lines should be 1–2 sentences maximum
  • Never duplicate what's in the body — the PS adds new information or a new angle
  • The PS line should be self-contained — someone who only reads the PS should understand the point
  • No fake urgency ("limited spots", "reaching out to only 5 companies")
  • The best PS lines make the reader think "wait, that's interesting" — not "okay, another sales email"

Process

  1. Read the email body
  2. Identify what goal the PS line should serve for this persona + signal
  3. Draft 3 PS line options, each from a different goal category
  4. Score each: relevant (0–2) + curiosity (0–2) + not salesy (0–2)
  5. Return ranked options with recommendation

Terms and plain-language output

<!-- glossary:start terms=social-proof mode=copy -->

Rules for every text a reader will see (post, email, message, page copy):

  1. No internal codes or letter scales (A/B/C, D L T E, scores without words, framework codes). Write the meaning.
  2. Use the plain form from the table below. English stays only for tool names and for copy that ships in English. A term the reader may not know gets explained in the same sentence or replaced.
  3. Any review, audit or report this skill produces for the team or the client follows the document rules: open it with «Словник цього документа» (terms used, at most 10), do not score what depends on unfinished work, and open each section with one concrete action.
Internal term (this skill)Write for the readerWhat it means
social proofдокази від іншихЦифри клієнтів, відгуки, логотипи чи кейси, які підтверджують, що вам можна вірити.
<!-- glossary:end -->

Output format

PS lines for: [step] — [hypothesis]
Email summary: [one line on what the email argues]

OPTION 1 — [goal]
P.S. [text]
Score: [n/6] | [why it works]

OPTION 2 — [goal]
P.S. [text]
Score: [n/6] | [why it works]

OPTION 3 — [goal]
P.S. [text]
Score: [n/6] | [why it works]

Recommended: Option [n] — [one-line reason]

Notes

  • PS lines are read before the body by a significant portion of recipients — write them as if they're the first thing read
  • Social proof PS lines work best when the proof is specific and role-relevant: "P.S. We ran this for a HubSpot agency similar to yours — they booked 14 meetings in the first 6 weeks."
  • Curiosity PS lines work best on Step 2 or 3 — by then you need a new hook
  • If the PS line is the strongest line in the email, the email body needs a rewrite

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/ps-line-generator">View ps-line-generator on skillZs</a>