sales-copy
Write sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile.
Supply asset profile
Research and knowledge work
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
Maintenance
fresh
2d since push
Risk
Needs review
The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
GitHub quality
28
62/100 Quality · 74/100 Trust
Coverage tags
Review notes
The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse. · Low GitHub adoption signal
Agent adoption scorecard
Trust, audit, and install readiness at a glance
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Human review before install
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
28 GitHub stars
Repo activity
28 stars, 5 forks
Maintenance
2d since push
License
MIT
Install
npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
Install safety
standard package or runtime install path
Permission surface
no high-risk permission surface in public metadata
Agent outcomes
No agent outcome data yet
Docs
Usable metadata, review docs
Risk summary
Review before production
- The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
- Low GitHub adoption signal
- Quality score needs review
- GitHub adoption: 28 GitHub stars
Install readiness
Install path available
- Install path is available
- Repository evidence is available
- License is declared
- No Agent Proven outcome evidence yet
Agent-readable metadata
Machine-readable decision data for this skill.
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
- Content automation workflows
- Claude Code teams
- builders willing to evaluate younger projects
- Summarize source material
Suited agents
Install decision
- Command
- npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
- Policy
- review
- Human review
- yes
Trust and risk
- Trust
- 66/100
- Audit
- 77/100
- Risk level
- Needs review
Outcome loop
- Endpoint
- /api/agent/outcome
- Event ID
- resolve
- Outcomes
- 5
Install command
npx skills add Deupaxx/EveryDay-Writer --skill sales-copyDo not use when
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
- Quality score needs review
Alternative
Last30days Skill
53.5K Stars
npx skills add mvanhorn/last30days-skill -g
Alternative
Academic Research Skills
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Alternative
GPT Researcher
28.0K Stars
npx skills add assafelovic/gpt-researcher
Alternative
DeepResearch
19.8K Stars
npx skills add Alibaba-NLP/DeepResearch
Agent safety v2
57/100 · Review before install
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
medium
Browser automation
Skill may drive a browser or interact with web pages.
medium
Network access
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Filesystem access
Skill may read or write project files, documents, generated artifacts, or local workspace state.
- The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
Install targets
Install this skill in your agent workflow
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
OpenAgentSkill CLI
Resolve policy, run the source installer safely, and report a verified install receipt.
$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install deupaxx-sales-copyAgent resolve plan
Let an agent verify fit before installing.
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20sales-copy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20sales-copy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/deupaxx-sales-copy/install
Agent should check
- Task fit and alternatives from Resolve API.
- Audit score, trust score, and safety policy warnings.
- Install target compatibility for Codex, Claude Code, Cursor, or CLI.
Copy prompt
Task: Use sales-copy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20sales-copy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/deupaxx-sales-copy/install
Install command: npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Give an agent the install path, not another directory page.
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/deupaxx-sales-copy/install
LLM text format
/api/skills/deupaxx-sales-copy/install?format=text
Find alternatives
/api/skills/search?q=sales-copy&limit=3
Agent prompt
Use sales-copy for this task. Review https://www.openagentskill.com/api/skills/deupaxx-sales-copy/install, then install with: npx skills add Deupaxx/EveryDay-Writer --skill sales-copyRegistry metadata
Agent-readable profile for automatic skill selection.
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/deupaxx-sales-copy
LLM text
/api/registry/manifest/deupaxx-sales-copy?format=text
Install alias
/api/registry/install/deupaxx-sales-copy
Recommend
/api/registry/recommend?task=Use%20sales-copy%20in%20an%20agent%20workflow&limit=3
Agent fit
Content automation
Use-case tags
Platforms
Claude Code
Audit report
Needs review · 77/100
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Fallback candidate for Content automation
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Content automation
Trust label
Prototype first
Install path
Command ready
Use when
- Content automation workflows
- Claude Code teams
- builders willing to evaluate younger projects
Evidence
- recent repository activity
- install command or GitHub repo available
- 62/100 quality profile
- 3 OpenAgentSkill engagement events
review first
- Low GitHub adoption signal
- The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
Implementation path
- 1Install it in a sandbox agent and run one Content automation task end to end.
- 2Compare output quality, latency, and failure behavior against at least one alternative.
- 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.
Trust profile
Sandbox only
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
CHECK28 GitHub stars
Stars/forks activity
CHECK28 stars, 5 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2d since push
License clarity
PASSMIT
Good signals
- AI review approved
- Install path is available
- Repository evidence is available
- Recently maintained repository
- Install command has no obvious high-risk pattern
- Outcome loop is ready but needs first real agent run
Review before install
- The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
- Low GitHub adoption signal
- Quality score needs review
- GitHub adoption: 28 GitHub stars
- Stars/forks activity: 28 stars, 5 forks; issue activity unavailable in current metadata
- No real agent outcome reports yet
- Human review required before unattended installation
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Promising candidate for agent workflows
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Use this skill in these scenarios
Publish consistently
Content automation
I need my agent to turn research and product updates into useful content drafts.
Answer users
Customer support
I need my agent to triage support requests and draft useful replies from product knowledge.
Operate web apps
Browser automation
I need my agent to control a browser, fill forms, and verify web app workflows.
Workflow fit
Add it to a complete workflow
Operate and verify web apps
Browser QA agent
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Find, compare, and synthesize
Research report agent
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
RAG knowledge base
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Alternative shortlist
Compare before you install
Similar skills that may fit this task.
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
GPT Researcher
Run autonomous deep research over web and local sources
DeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
Overview
--- name: sales-copy description: | Write sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile. license: MIT metadata: version: "0.3.0" ---
# EW Skill — Sales Copy
**Dependency chain. Read these in order before writing anything:**
1. `core/anti-ai-rules.md` (read fully; Section 0 sets the standard, 0.1 sets precedence, 0.2 forbids fabrication, 9 and 10 stop over-correction) 2. `core/ai_slop_commandments.md` (mechanism reference and diagnostic checklist) 3. `core/voice-profile.md` (this writer's voice fingerprint; if `Completed: No`, stop and run onboarding) 4. Any `.md` files the user has dropped in `references/`
This chain applies on direct invocation (`/ew:sales-copy`) exactly as it does on dispatch through `/ew`. Direct invocation skips routing, not constraints.
---
## WHAT THIS SKILL IS FOR
Sales pages, email sequences, and direct response copy. Writing that exists to produce a measurable outcome: a purchase, a booking, a subscription, an enrollment.
Sales copy is the most honest form of writing because it can't hide its intent. It either converts or it doesn't. The number tells you. The discipline here is writing that moves people toward something they genuinely need — not manipulating them into something they don't.
Manipulation is not this skill's tool. Clarity, specificity, and legitimate persuasion are.
---
## THE STRUCTURAL SPINE: THE CUSTOMER AS PROTAGONIST
The Triad of Craft and the writing commandments converge on one insight for sales copy: the customer is the protagonist, not the product. The product is the key knowledge found at the midpoint of their journey. The copy must tell their story, not yours.
**The sales copy as hero's journey:**
**Ordinary World:** The customer's life before. The problem that exists. The pain that is real. State it more specifically than they've heard it before — this is what creates the "they understand me" moment that earns trust.
**Inciting Incident:** The moment their ordinary world is no longer acceptable. What made them start looking? What made the pain acute enough to act? Naming this is the difference between copy that resonates and copy that gets scrolled past.
**The Woods:** What they've already tried. What failed. Why the usual solutions don't work for this specific problem. This section is often skipped — it shouldn't be. Acknowledging failed attempts proves you understand the problem deeply.
**Key Knowledge:** The mechanism. Why this product/service works where others didn't. Not a feature list — the one insight about the problem that makes the solution make sense.
**New Equilibrium:** Life after. Specific. Grounded. Not "transform your business" — "you stop writing from scratch every time and start from a brief that already has the argument."
---
## THE OPENING
The sole purpose of the first sentence is to get the reader to read the second sentence.
The opening must do one of three things: name the reader's problem so specifically they feel seen, challenge a belief they hold, or present a specific outcome they want. No preamble. No warm-up. The reader made the decision to stay or go in the first three seconds.
**What works:**
**The problem, stated precisely:** "You've bought three copywriting courses. Your conversion rate is the same as when you started."
**The specific outcome:** "A sales page that converts at 8% when your current one converts at 1.2%."
**The challenge:** "Most sales pages fail before the reader reaches the first CTA — and it's not the CTA that's broken."
**What doesn't work:** - "Are you tired of...?" — exhausted opener, signals template - "Imagine a world where..." — futurism invitation, signals AI - "I used to struggle with this too..." — false vulnerability, signals performance - Long story openers that bury the point past the 300-word mark
---
## SPECIFICITY IS THE PROOF
In sales copy, specificity is the mechanism of trust. Every vague claim is a credibility debit. Every specific claim is a credibility credit.
**The specificity upgrade:**
❌ "This program has helped hundreds of businesses grow." ✅ "47 solo consultants used this to book their first $5,000 client within 90 days."
❌ "Our clients see amazing results." ✅ "Amara increased her newsletter conversion rate from 1.8% to 6.3% in 60 days using only the cold traffic sequence in Module 3."
The number, the name, the timeframe, the specific mechanism — these are what make claims land. Without them, you're asking the reader to trust you on faith. Most won't.
**Name the mechanism:** Don't just say the product works — explain briefly *why* it works. The mechanism is what separates a claim from an argument. ❌ "This headline formula gets clicks." ✅ "This headline formula works because it triggers pattern interruption — the reader's brain stops scanning when it encounters something that doesn't fit the template it was expecting."
---
## OBJECTION ARCHITECTURE
Every unconverted reader is a reader with an unaddressed objection. Your copy must find and answer the three to five objections that kill the most conversions — before the reader has to ask.
**The main objections in most sales situations:** 1. "Is this for someone like me?" — Too broad, won't work in my situation 2. "Will this actually work?" — Skepticism about the mechanism or promise 3. "Can I trust you?" — Credibility gap, insufficient proof 4. "Is it worth the cost?" — ROI isn't clear 5. "Is now the right time?" — Urgency isn't real
**Address each with specifics, not reassurance.** Reassurance ("We're confident you'll love it!") doesn't address objections — it papers over them. The reader can feel the difference.
Objection: "I've tried things like this before and they didn't work." Reassurance: "We think you'll be pleasantly surprised!" Address: "Most [category] courses teach the framework without the implementation step. This one starts at implementation. Here's what that looks like on day one:"
---
## PROOF ARCHITECTURE
Proof is not a section at the bottom of the page. It is distributed throughout the copy, placed nearest to the claim it supports.
**Types of proof, in descending order of power:** 1. **Specific named results with numbers and timeframes** — the most trusted form 2. **Named testimonials with specific outcomes** — not "John changed my business," but "John's launch converted at 4.2% where his previous launch was at 0.9%" 3. **Your own demonstrated expertise** — specific, named, verifiable 4. **Mechanism explanation** — showing you understand *why* it works 5. **Social proof (numbers, logos, media)** — useful but weakest without specifics
**Never use:** - Anonymous testimonials - Testimonials with only first name and last initial - Testimonials that only praise the person, not the result - Claims you can't substantiate
---
## EMAIL SEQUENCES
An email sequence is a conversation across time. Each email must earn the right to send the next one.
**The first email's job:** Establish why the reader is here and what they'll get. Not a full pitch — a clear reason to open the next one.
**Middle emails:** Deepen the argument. Each email handles one aspect of the case for action. One idea per email. Every email ends with a forward pointer that makes the next one feel necessary.
**The sales email:** After the relationship and the argument are built. The offer, stated clearly and honestly. The mechanism, the proof, the CTA. One CTA. No hedge. No apology for selling.
**Subject lines:** Write for the opened inbox of someone who doesn't know what's inside. The subject line earns the open; the first line earns the read.
---
## WHAT THIS SKILL DOES NOT DO
This skill does not generate false urgency ("only 3 spots left" when there are unlimited spots), manufacture scarcity, or write copy that misrepresents what the product does. These techniques work once and destroy trust permanently.
If the offer is good, honesty converts. If the offer requires manipulation to convert, the offer is the problem — not the copy.
---
## POST-GENERATION REVIEW
After producing any draft, stop. Re-read `core/anti-ai-rules.md` Sections 1–7 with the draft in front of you. Go line by line through the pre-publish checklist in Section 7. Fix every failure before presenting the output.
Sales copy that reads as AI-generated destroys the trust it needs to convert. The review pass is not quality control — it is the product.
## PRE-LAUNCH CHECKLIST
- [ ] Does the opening name the reader's specific problem or desired outcome in the first 3 sentences? - [ ] Is the customer the protagonist — or is the product? - [ ] Is every claim backed by a specific number, name, or mechanism? - [ ] Are testimonials named and outcome-specific? - [ ] Are the top 5 objections addressed with specifics, not reassurance? - [ ] Is the mechanism explained — not just claimed? - [ ] Is there one clear CTA per section? - [ ] Have you run Sections 1–7 of `core/anti-ai-rules.md`? - [ ] Is all urgency or scarcity real — not manufactured? - [ ] Does the copy end having proved something, or just asserted it?
Technical details
- Version
- 1.0.0
- License
- MIT
- Last updated
- Aug 20, 2026
- Published
- Aug 20, 2026
Decision snapshot
Fallback candidate
recent repository activity
Audit
Install review
Install and adoption review
- Security
- 81/100
- Maintenance
- 100/100
- Install
- 92/100
Agent-proven evidence
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
- Success rate
- —
- Recent failure
- —
- Outcomes
- 0
- Output quality
- —
- Failed
- 0
- Not relevant
- 0
- Installs
- 0
- Risk blocked
- 0
- Setup needed
- 0
- Production
- 0
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Add to agent workflow
Free and open source. Review the report before installing into production agents.
Growth loop
Share kit
Scenario-led draft for sales-copy, ready for a manual X post.
sales-copy: Write sales pages, email sequences, and direct-response copy that converts through clarity an... 28 stars https://www.openagentskill.com/skills/deupaxx-sales-copy?ref=x
Optional reply with install command
Listing + install path for sales-copy: https://www.openagentskill.com/skills/deupaxx-sales-copy?ref=x Install: npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
Listing source
Registry indexed
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
- Creator
- Deupaxx
- Source
- Deupaxx/EveryDay-Writer
- Indexed by
- OpenAgentSkill community index
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
Claim this skill listing
This Registry indexed listing is attributed to Deupaxx but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Add the evidence badges to your README
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/deupaxx-sales-copy)
[](https://www.openagentskill.com/skills/deupaxx-sales-copy)
[](https://www.openagentskill.com/skills/deupaxx-sales-copy/audit)
[](https://www.openagentskill.com/skills/deupaxx-sales-copy)Author
Deupaxx
@deupaxx
Tags
Platform fit
Health signals
- GitHub stars
- 28
- Quality score
- 34/100
- Last GitHub push
- Aug 20, 2026
- Framework hints
- Unknown
- OpenAgentSkill views
- 3
- Install copies
- 0
- Outbound clicks
- 0
Community signal
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Trust & safety
Sandbox only
- GitHub adoption28 GitHub starsCHECK
- Stars/forks activity28 stars, 5 forks; issue activity unavailable in current metadataCHECK
- Recent maintenance2d since pushPASS
- License clarityMITPASS
- README/SKILL.md completenessPublic metadata needs stronger README/SKILL.md contextINFO
- Dependency/runtime riskno major dependency risk hints in public metadataPASS
Related skills
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
53.5K StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsDeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
19.8K Stars