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
|
||||
hint: |
|
||||
BLOG POST DRAFT
|
||||
@@ -22,15 +22,15 @@ hint: |
|
||||
Write the full blog post:
|
||||
- # Title as H1 (make it specific and curiosity-driven, not generic)
|
||||
- Optional subhead in italics
|
||||
- Opening hook: first 2–3 sentences pull the reader in immediately
|
||||
- Body: 3–5 sections with bold subheadings, short readable paragraphs
|
||||
- Opening hook: first 2-3 sentences pull the reader in immediately
|
||||
- Body: 3-5 sections with bold subheadings, short readable paragraphs
|
||||
- At least one concrete example, number, or real scenario per section
|
||||
- "Try This Week" or equivalent action section before the closing
|
||||
- Memorable closing line that reinforces the promise
|
||||
|
||||
Tone rules (apply the voice above):
|
||||
- Peer-to-peer. Write like a knowledgeable friend, not a corporate brochure.
|
||||
- Use "you" and "your" — not "one" or "the reader."
|
||||
- Use "you" and "your" -- not "one" or "the reader."
|
||||
- Short sentences preferred. No filler paragraphs.
|
||||
- No listicles of 10+ items without grouping them into themes.
|
||||
- Work the keywords in naturally — never stuff them.
|
||||
- Work the keywords in naturally -- never stuff them.
|
||||
|
||||
Reference in New Issue
Block a user