// Write founder build-in-public log entries from daily work notes, source notes, and accomplishments. Use for weekly build summaries and founder update posts destined for /build-log. Triggers on build-in-public content, founder updates, or weekly build summaries.
Post AI news to Discord channel via webhook. Triggers on /discord-post-news command.
Summarize AI industry news, tool launches, and market signals into concise, opinionated summaries for the website /news section and social channels. Use when processing AI news links or writing news commentary. Triggers on AI industry news, tool announcements, or market signal content.
Evaluate content against the 4-level approval policy and determine whether to auto-approve, score-gate, send to review, or block. Use when the approval engine needs to make a decision on pending content. Triggers on any content approval evaluation request.
JSON-based approval queue for the CMO pipeline. Use when managing content approval workflows.
Generate audience-specific angles and hooks for content. Takes a topic and produces multiple angles tailored to different audience segments. Use when adapting content for different audiences or brainstorming hooks. Triggers on angle generation, hook brainstorming, or audience targeting requests.
Build automation scripts for repetitive tasks like file processing, data transformation, scheduling, API calls, and workflow automation. Use when the user needs a script to automate something, process files in batch, schedule tasks, or connect tools. Triggers on "automate this", "write a script for", "batch process", "schedule this", "connect these tools", or any automation request.
| name | build-log-writer |
| description | Write founder build-in-public log entries from daily work notes, source notes, and accomplishments. Use for weekly build summaries and founder update posts destined for /build-log. Triggers on build-in-public content, founder updates, or weekly build summaries. |
HONEST CLASSIFICATION: This is a prompt template, not an executable plugin. OpenClaw injects this as context to guide LLM behavior. It does NOT enforce rules at runtime. Real enforcement requires the shell scripts in
OpenClawData/scripts/.
Write authentic build-in-public log entries that share the journey of building.
qwen3:8b
MarketingToolData/build-logs/OpenClawData/queues/website/pending/---
title: "<build log title — week of YYYY-MM-DD or specific topic>"
date: "YYYY-MM-DD"
section: "build-log"
type: "founder-update"
tags: [<relevant tags>]
approval_level: "L1"
source_file: "<path to source notes>"
status: "pending"
---
# <Title>
## What I Built This Week
<3-5 bullet points of concrete accomplishments>
## What I Learned
<1-2 key lessons, insights, or realizations>
## What's Next
<2-3 things planned for next week>
## Honest Note
<Optional: 1-2 sentences on challenges, doubts, or real feelings about the work>
build-log-YYYY-MM-DD.md