Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Safe content workflow (drafts/reviewed/revised/approved/posted) with human-in-the-loop approval, plus CLI to list/move/review and post to LinkedIn/X. Use when setting up a content pipeline, drafting content, managing review threads, or posting approved content.
Safe content workflow (drafts/reviewed/revised/approved/posted) with human-in-the-loop approval, plus CLI to list/move/review and post to LinkedIn/X. Use when setting up a content pipeline, drafting content, managing review threads, or posting approved content.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Safe content automation with human-in-the-loop approval. Draft β Review β Approve β Post.
npm install -g agent-content-pipeline content init . # Creates folders + global config (in current directory) For cryptographic approval signatures (password-protected): content init . --secure This creates: drafts/ β work in progress (one post per file) reviewed/ β human reviewed, awaiting your revision revised/ β you revised, ready for another look approved/ β human-approved, ready to post posted/ β archive after posting templates/ β review and customize before use .content-pipeline/threads/ β feedback thread logs (not posted)
β Can do: Write to drafts/ Read all content directories Revise drafts based on feedback Move revised files to revised/ Run content list to see pending content β Cannot do: Move files to approved/ (only the human can approve) Post content Set status: approved
One post per file. Each suggestion or draft should be a single post, not a collection. File naming: YYYY-MM-DD-<platform>-<slug>.md Use frontmatter: --- platform: linkedin # linkedin | x | reddit (experimental) title: Optional Title status: draft subreddit: programming # Required for Reddit --- Your content here. Tell the human: "Draft ready for review: content review <filename>"
drafts/ β reviewed/ β revised/ β approved/ β posted/ β β ββββββββββββ more feedback You write draft to drafts/ Human runs content review <file>: With feedback β file moves to reviewed/, you get notified No feedback β human is asked "Approve?" β moves to approved/ If feedback: you revise and move to revised/ Human reviews from revised/: More feedback β back to reviewed/ Approve β moves to approved/ Posting happens manually via content post
When you get review feedback: Read the file from reviewed/ Apply the feedback Move the file to revised/ Confirm what you changed (Optional) Add a note: content thread <file> --from agent
Professional but human Idiomatic language (Dutch for NL audiences, don't be stiff) 1-3 paragraphs ideal End with question or CTA 3-5 hashtags at end
280 chars per tweet (unless paid account) Punchy, direct 1-2 hashtags max Use threads sparingly If Firefox auth fails, you can paste auth_token and ct0 manually Manual cookie steps: Open x.com and log in Open DevTools β Application/Storage β Cookies β https://x.com Copy auth_token and ct0
Treat as experimental; API and subreddit rules can change Requires subreddit: in frontmatter Title comes from frontmatter title: (or first line if missing) Match each subreddit's rules and tone
content list # Show drafts and approved content review <file> # Review: feedback OR approve content mv <dest> <file> # Move file to drafts/reviewed/revised/approved/posted content edit <file> # Open in editor ($EDITOR or code) content post <file> # Post (prompts for confirmation) content post <file> --dry-run # Preview without posting content thread <file> # Add a note to the feedback thread
The security model separates drafting (AI) from approval/posting (human): β Agent drafts content β Agent revises based on feedback β Agent cannot approve (human approves via content review) β Agent cannot post Posting is handled manually via CLI β never by the agent directly.
PlatformAuth StorageEncrypted?Password Required?LinkedInBrowser profileβ Yesβ YesX/TwitterFirefox tokensβ Yesβ Yes Both platforms require password to post. Tokens are extracted from Firefox and encrypted locally.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.