SEO content brief

1nika: v12workflow:3  id: seo-content-brief4  description: "Competitor sitemap → top page → gap analysis → typed brief"5​6# A NON-thinking local model, deliberately: a thinking model can spend the7# whole `max_tokens` budget in its think block and return before the JSON8# (engine#428). Schema showcases pick a model that answers directly.9model: ollama/llama3.2:3b10​11inputs:12  topic:13    type: string14    # Slug-shaped on purpose: this value lands in a FILENAME below, and a15    # caller-supplied string that reaches a path is the tainted-value case the16    # checker polices (NIKA-AUTH-008). Keep it to one path segment — `*` in17    # the write bound never crosses `/`, so `a/b` is refused, by design.18    default: "rust-async-runtimes"19    description: "The keyword/topic you want to rank for (one path segment)"20const:21  competitor_sitemap: "https://competitor.example.com/sitemap.xml"22⛨permits:23  ⛨tools: ["nika:fetch", "nika:write"]24  ⛨fs:25    # One brief per topic, written DIRECTLY in out/briefs/. `*` matches a26    # single path segment and never crosses `/`, so a topic carrying a slash27    # is refused instead of steering the write into a subtree — which is28    # exactly why this is `out/briefs/*.json` and not `out/briefs/**`.29    ⛨write: ["out/briefs/*.json"]30  ⛨net:31    # Both fetches stay on the competitor's own host: the sitemap, then a URL32    # that same sitemap listed. Net entries are exact host names, never globs —33    # add YOUR competitor's host here when you point the const at it, or the34    # fetch is refused at run and the recover path quietly takes over.35    ⛨http: ["competitor.example.com"]36​37tasks:38  map:39    ◆invoke:40      tool: "nika:fetch"41      args:42        url: "${{ const.competitor_sitemap }}"43        mode: sitemap44    output:45      top: ".[:5] | map(.loc)"46    on_error:47      # The recovery stands in for the RAW response, so it has the shape a48      # sitemap fetch returns — a root array of {loc, …} — and the `output:`49      # jq above slices it exactly as it would slice the live one. Recover the50      # BINDING's shape instead and the jq runs against the wrong thing and51      # throws NIKA-VAR-004.52      recover:53        - { loc: "https://competitor.example.com/blog/async-runtimes-compared" }54        - { loc: "https://competitor.example.com/blog/tokio-vs-smol" }55        - { loc: "https://competitor.example.com/blog/choosing-an-executor" }56​57  top_page:58    with:59      map_top: ${{ tasks.map.top[0] }}60    ◆invoke:61      tool: "nika:fetch"62      args:63        url: "${{ with.map_top }}"64        mode: article65    on_error:66      recover: |67        Async runtimes compared — we benchmarked four executors on the same68        workload. Tokio wins on ecosystem breadth; smol wins on binary size.69        We did not cover structured concurrency, cancellation safety, or how70        any of this behaves under a blocking call, which is where most teams71        actually get hurt.72​73  brief:74    with:75      map_top: ${{ tasks.map.top }}76      top_page: ${{ tasks.top_page.output }}77    ◇infer:78      max_tokens: 120079      prompt: |80        Topic to rank for · ${{ inputs.topic }}81        Competitor's top URLs · ${{ with.map_top }}82        Their best page on it ·83        ${{ with.top_page }}84​85        Write a content brief that BEATS this page · find the gaps they86        missed · angle for search intent.87      schema:88        type: object89        additionalProperties: false90        required: [title, angle, outline, keywords]91        properties:92          title: { type: string }93          angle: { type: string }94          outline: { type: array, items: { type: string } }95          keywords: { type: array, items: { type: string } }96​97  save:98    with:99      brief: ${{ tasks.brief.output }}100    ◆invoke:101      tool: "nika:write"102      args:103        # `.json` content is ONE interpolated value — the engine serializes it.104        path: "out/briefs/${{ inputs.topic }}.json"105        content: "${{ with.brief }}"106        create_dirs: true107​108outputs:109  brief:110    value: ${{ tasks.brief.output }}111    description: "The typed content brief"112​