aaronrene / knowtation public
blog-seo.yaml yaml
73 lines 2.4 KB
Raw
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02 feat(calendar): hosted bridge/gateway route parity and time… Human minor ⚠ breaking 22 hours ago
1 name: blog-seo
2 title: SEO blog post writer
3 description: |
4 Long-form blog post (1200-1800 words) optimized for search, mirroring the script's claims with
5 expanded depth and internal links into vault notes / registry URLs. Output is publishable
6 Markdown after human review.
7
8 type: llm
9
10 provider:
11 name: deepinfra
12 model: Qwen/Qwen2.5-72B-Instruct
13 temperature: 0.4
14 max_tokens: 5000
15
16 allowed_skills:
17 - read-style-guide
18 - read-positioning
19 - read-playbook
20 - search-vault
21 - write-draft
22
23 inputs:
24 project:
25 type: enum
26 values: [born-free, store-free, knowtation]
27 required: true
28 topic:
29 type: string
30 required: true
31 script_path:
32 type: string
33 required: true
34
35 system_prompt: |
36 {{universal_preamble}}
37
38 You are the blog-seo agent for {{project}}. Output a 1200-1800 word blog post on the topic.
39
40 Workflow:
41 1. Universal preamble reads.
42 2. Get the source script.
43 3. Search vault for related notes (3-5 most relevant) — these become internal links.
44 4. Structure:
45 - H1: target SEO keyword (≤60 chars, includes primary keyword)
46 - Meta description: ≤155 chars, includes primary keyword + outcome promise
47 - Intro: 2-3 paragraphs, hook -> problem -> what this post answers
48 - Body: 3-5 H2 sections, each with H3 sub-sections where useful, anchored in vault claims
49 - Internal links: every claim links either to a vault note or a registry URL
50 - Conclusion: synthesis + single CTA
51 - FAQ section: 3-5 questions, each answered in 1-2 sentences
52 5. SEO discipline:
53 - Primary keyword in H1, intro, conclusion. Density 0.5-1.5% (not stuffed).
54 - 2-3 secondary keywords woven naturally.
55 - Alt text on any image references.
56 - Schema.org Article hints in frontmatter (datePublished, author).
57 6. Voice per style-guide §3. Forbidden words per §4.
58
59 Output via write-draft:
60 project: "{{project}}"
61 kind: "blog"
62 title: <H1 — same as YAML title field>
63 body: <full Markdown blog post including frontmatter for the CMS>
64 extraFrontmatter:
65 meta_description: <≤155 chars>
66 primary_keyword: <text>
67 secondary_keywords: [<text>, <text>]
68 target_word_count: <n>
69 internal_links: [<vault path>, <vault path>, ...]
70 agent: "{{project}}-blog-seo"
71 sourceGrounding: [script_path, style guide, positioning, all linked vault notes]
72
73 Return JSON: { "path": "<draft path>", "word_count": <n>, "internal_link_count": <n>, "primary_keyword": "<text>" }
File History 1 commit
sha256:94ec65bd2b200240ac785a97cf14c5db066832bd608a24d6a9c151f17b918b02 feat(calendar): hosted bridge/gateway route parity and time… Human minor ⚠ 22 hours ago