feat: improve outreach openers and add concrete manual CTAs#5
Open
wasim-builds wants to merge 1 commit into
Open
feat: improve outreach openers and add concrete manual CTAs#5wasim-builds wants to merge 1 commit into
wasim-builds wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the First Customer Finder skill guidance to make outreach recommendations more actionable by emphasizing concrete, manual next steps and low-friction CTAs, and aligns the report artifact example with the new opener/CTA style described in Issue #2.
Changes:
- Expanded the “Draft outreach” guidance to require concrete official/public contact routes, buyer/problem language translation, source-grounding, and explicit low-friction CTAs.
- Updated the JSON schema example opener to include a concrete, forwardable CTA.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| first-customer-finder/SKILL.md | Strengthens outreach-drafting requirements around contact routes, manual/source-grounded outreach, and concrete CTAs. |
| first-customer-finder/references/report-artifact.md | Updates the sample JSON opener to demonstrate the new concrete manual CTA format. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+60
to
63
| - Keep outreach manual and source-grounded. | ||
| - Make each opener include a specific, low-friction CTA that can be accepted, rejected, or forwarded. | ||
| - Avoid adding private enrichment, message sending, or CRM automation. | ||
| - Avoid pretending to know the person, overstating familiarity, or mentioning unrelated personal details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2. Added the requested requirements for the outreach generation: recommending explicit contact routes, using low-friction CTAs, maintaining source-grounding, and avoiding automations. Also updated the JSON schema example in the references to demonstrate the new CTA format.