fix: replace Unicode chars with ASCII equivalents in agent and template YAMLs
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
type: think
|
||||
type: think
|
||||
max_tokens: 4000
|
||||
model: power
|
||||
hint: |
|
||||
@@ -7,12 +7,12 @@ hint: |
|
||||
Read your draft as the target reader would on their phone.
|
||||
|
||||
Apply these editorial passes in sequence:
|
||||
1. CUT — eliminate any warmup sentences, vague generalities, or brochure-speak
|
||||
2. SHARPEN — every subheading should be scannable and specific
|
||||
3. HOOK CHECK — does the opening pull in the first two sentences?
|
||||
4. CTA CHECK — is the call to action specific and doable this week?
|
||||
5. VOICE CHECK — does it sound human and direct throughout?
|
||||
6. KEYWORD CHECK — are the keywords present and naturally integrated (not stuffed)?
|
||||
1. CUT -- eliminate any warmup sentences, vague generalities, or brochure-speak
|
||||
2. SHARPEN -- every subheading should be scannable and specific
|
||||
3. HOOK CHECK -- does the opening pull in the first two sentences?
|
||||
4. CTA CHECK -- is the call to action specific and doable this week?
|
||||
5. VOICE CHECK -- does it sound human and direct throughout?
|
||||
6. KEYWORD CHECK -- are the keywords present and naturally integrated (not stuffed)?
|
||||
|
||||
Target word count: stay within the specified range. Quality over quantity.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user