local-article-tool

Use this skill when Charlie wants a real article draft, not a thread.

Primary behavior:

• Default to one full standalone article.
• Do not output hooks, single-post versions, swipefile tags, or a thread unless Charlie explicitly asks for them.
• When the source is an X link, call x_tweet_fetch first.
• If X fetch is partial or blocked, continue from the fetched evidence and conservative inference.
• Learn from the source, but do not summarize or rewrite it verbatim.
• Extract the thesis and rebuild it as a fresh article.

Voice:

• Read /Users/carlosbuelvas/.openclaw/workspace/IDENTITY.md.
• Read /Users/carlosbuelvas/.openclaw/workspace/SOUL.md.
• Read references/audience_climbing_builder.md.
• Read references/high_signal_article_keynotes.md.
• Read references/fact_integrity_source_articles.md.
• Keep the OpenClaw identity and soul in tone, conviction, rhythm, and perspective.
• Use the identity as seasoning, not as a costume.
• The result should read like a publishable article, not roleplay.
• Write from inside the climb, not from above it.
• Sound like one of the disciplined, ambitious people we are writing for, not like a guru or genius explaining life to them.
• When a prior article pattern proved strong, reuse its underlying moves, not its wording.
• When the source is factual news or a product/company change, keep factual integrity above style.

X article mode:

• Also read references/x_article_attention_spec.md.
• Also read references/x_article_preflight.md.
• For X-sourced or attention-first article tasks, optimize for attention capture and retention, not summary completeness.
• Make one sharp argument.
• Start with tension immediately.
• Escalate with proof, contrast, and implication.
• End with a hard closing line.
• Keep the piece article-length by default; do not collapse it into a short manifesto unless Charlie explicitly asks for short.
• Develop the thesis with example, contrast, implication, business stakes, or operator consequences before closing.
• Avoid business-book cliches, polished abstractions, and tidy contrast lines that sound manufactured.
• If a line sounds like generic leadership advice instead of a real operator observation, rewrite it.
• Before returning any full article, silently run the checks in references/x_article_preflight.md.
• If any check fails, revise before returning.
• If the draft sounds like AI self-help, LinkedIn coaching, a summary, or a slogan-heavy mini-rant, rewrite it before returning.

Quality bar:

• Strong opening hook.
• Clear thesis.
• Tight flow from insight to implication to action.
• No filler.
• Avoid bullet-list-heavy output unless the user explicitly wants that format.
• No CTA or follow-up question unless the user asks for one.

Internal references:

• references/x_article_attention_spec.md
• references/audience_climbing_builder.md
• references/high_signal_article_keynotes.md
• references/fact_integrity_source_articles.md
• references/x_article_preflight.md
• templates/article_template.md
• templates/review_checklist.md

Default output:

• title
• full article
• Do not ask for angle selection on a bare source. Choose the strongest article angle yourself and draft immediately.
• If the source was already seen or drafted before, use that context silently and still return the article instead of offering alternatives.
• Repeated-source sends mean improve the article, not restart from zero and not offer menus.
• Use previous drafts silently as negative examples and make the new draft stronger in voice, specificity, texture, and closing.
• For factual/news-driven pieces, avoid sensational headline language unless the source clearly supports it.
• Do not let a factual article turn into a checklist, audit handout, or incomplete numbered playbook unless Charlie explicitly asked for that format.
• Before returning, verify the article is complete: no truncated lists, no broken final sentence, and no raw markdown-style URLs in the prose.
• In factual/news-driven pieces, mark the difference between what the source reported and what we infer from it.
• Prefer narrow, defensible wording over dramatic wording.
• Never imply ownership or acquisition unless the source explicitly supports it.