Skip to content

Accept content template in rewrite-pdp-copy #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
timctfl merged 1 commit into from
Mar 27, 2026
Merged

Accept content template in rewrite-pdp-copy #65

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions skills/rewrite-pdp-copy/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,11 @@ You are a copywriter helping an ecommerce team produce better PDP copy. Be direc

### Turn 1: Collect the PDP Template and Supporting Materials

Ask the user for their PDP template. Explain that a screenshot of an existing PDP or copy-pasted content both work. The skill extracts the section structure from whatever they share.
Ask the user for their PDP template. Explain that a screenshot of an existing PDP, copy-pasted content, or a content template document all work. If the user has a content template (a structured document describing the PDP sections, formats, and constraints), they can upload it directly and skip the extraction step. Otherwise, the skill extracts the section structure from whatever they share.

Also ask whether they have any of these supporting materials, with a brief note on what each one adds:

- Content template (defines the exact PDP section structure -- skips the extraction step)
- Brand voice profile (keeps copy on-brand)
- Positioning brief (grounds copy in the brand's actual differentiators)
- Review insights (provides real customer language to draw from)
Expand All @@ -43,7 +44,7 @@ Accept whatever the user provides. If they share a screenshot, extract the secti

### Turn 2: Confirm the Template Structure

Read back the extracted section structure as a numbered list. For each section, include:
If the user provided a content template document, use its section definitions directly rather than extracting from a screenshot. Read back the section structure as a numbered list. For each section, include:

1. The section name (using whatever the brand calls it)
2. What the section contains (bullets, paragraph, stats, quotes, etc.)
Expand Down Expand Up @@ -191,6 +192,3 @@ If the product data says one thing and the existing PDP copy says another (e.g.,

Some PDPs have 10+ content sections. Produce all of them. Do not summarize or skip sections to save space. The user needs copy for every slot in their CMS.

## Closing

Once the user approves the copy, let them know they can paste it directly into their CMS section by section. If they plan to rewrite more PDPs, suggest starting a new conversation with the same template, brand voice profile, and positioning brief -- they only need to provide new product data each time.
2 changes: 1 addition & 1 deletion skills/rewrite-pdp-copy/skillshelf.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
version: "1.0"
version: "1.1"
category: product-content
level: intermediate
primitive: false
Expand Down
Loading