git:20260729.75a847a to git:20260811.66e9440

---

name: content-writer

description: Plan, research, draft, revise, humanize, adapt, and audit editorial content with a writing brief, source and claim ledgers, channel-aware structure, voice preservation, citation checks, and publication-readiness gates. Use for social posts, articles, blogs, newsletters, explainers, tutorials, case studies, thought leadership, and source-grounded rewrites; trigger on social copy, article writing, research writing, outlining, rewriting, naturalizing, de-AI editing, fact-checking, citation review, or pre-publish audit.

---

# Content Writer

Turn a goal, source pack, or draft into defensible, channel-ready content. Keep research, evidence, composition, and editing distinct.

## Route the work

Use the smallest useful sequence. Do not force the user through every mode.

| Mode | Use when | Primary deliverable |

|---|---|---|

| `research` | gather or organize material before writing | source ledger, claim ledger, and gaps |

| `draft` | create a complete article, social post, or section | publication-shaped draft |

| `revise` | improve argument, structure, clarity, or accuracy | revised text and material change notes |

| `humanize` | remove stiff, generic, or model-like prose | voice-matched rewrite and risk notes |

| `audit` | verify claims, citations, links, disclosures, or readiness | prioritized audit with publication decision |

| `adapt` | reshape existing content for another channel or placement | channel-specific version without new unsupported claims |

Use this skill for individual social posts. Do not use it for social calendars, account operation, automatic publishing, campaign analytics, or final professional legal, medical, or financial advice.

## Build the working brief

## Choose the evidence policy

1. Use `supplied-only` for faithful rewriting, confidential material, or no-browse requests. Freeze every source clause carrying a fact, scope, limitation, certainty, citation, or disclosure. A paired boundary such as “supports X; does not support Y” is atomic: retain both halves. Treat “one sentence,” “be concise,” and “do not explain the process” as presentation constraints only; they never authorize dropping frozen content. Put the limitation in the artifact and join it to the supported scope when needed. Before delivery, map every frozen clause to the artifact. A shorter channel may compress wording but may not drop a limitation. Add no externally checkable specifics, implied benefits, generic bridge claims, recommendations, or future-value language unsupported by the supplied material.

2. Use `source-grounded` when provided files/links should anchor the work but limited external verification is allowed.

3. Use `current-research` when recent facts, prices, laws, product capabilities, public figures, links, scientific findings, or competitive claims matter.

4. Use `prose-only` when the task is purely stylistic and contains no claims that need verification.

For `source-grounded`, extended research, or a complex evidence audit, read

[research-and-evidence.md](references/research-and-evidence.md) before

researching or citing. Ordinary bounded `current-research` must use the

self-contained fast path below without loading that long reference. Keep a

source ledger and claim ledger for material claims. Treat search snippets as

discovery only, not evidence.

## Execute the editorial pipeline

### 1. Prewrite

- Convert the request into a one-sentence reader promise and one-sentence controlling thesis.

- Identify the most relevant perspectives, including a credible counterpoint when the format calls for one.

- For research-backed work, do not start full prose until the major claims are supported or marked as gaps.

- For ordinary `current-research`, use the compact research fast path below

instead of building the full outline or evidence matrix before discovery.

### 2. Research

- For source-grounded, extended, or complex evidence work, read

[research-and-evidence.md](references/research-and-evidence.md). For ordinary

bounded `current-research`, do not load it; use this complete compact path.

- Record only the requested scope, exactly one short required evidence-family

label per dimension explicitly requested by the user, and the material claims

each family must support. Never invent an auxiliary family. For salary, job

volume, and policy, use exact labels `salary`, `job-volume`, and `policy`;

copy only those exact strings into source `families`. Query each family once.

For Chinese policy, query `site:gov.cn YYYY 人工智能 就业 招聘 政策` (replace

the year) and fetch a specific official result first; elsewhere use the

issuer's official domain. Defer brief,

outline, matrix, format reference, and prose until collection ends.

- Make one first-and-only batch of at most 3 family-specific `web_search` calls

with `count <= 5`, covering the requested period and latest prior baseline.

Chinese queries include `-百科 -baike -wikipedia`; other queries include

`-wikipedia -encyclopedia`. Search is closed after that batch even when

results are weak or after retry/compaction. Immediately write literal

`RESEARCH_LEDGER.json` with `search_batch_complete: true`, integer

`search_attempts`, integer `fetch_attempts: 0`, `required_families`, and

`sources: []`. Keep both attempt fields as integer counts, never arrays;

increment `fetch_attempts` on errors too. Update the same file after fetches.

A successful `write_file` confirms it: never call

`read_file` merely to verify a same-turn ledger write. Re-read the ledger only

after an actual context compaction, before any later network action.

- Reject encyclopedias, homepages, search/category/tag pages, and generic hubs.

Fetch only verbatim specific URLs from saved successful results, in

family-priority order with `maxChars: 2500`. For the initial collection,

fetch exactly 3 results in batches of 2 then 1. Add each successful relevant

page with exact row shape `{"url":"VERBATIM_URL","families":["salary"],"status":"usable"}`,

substituting its exact family. Update the ledger after the third attempt and run the first gate while

`fetch_attempts >= 3`, before any fourth fetch, prose, or extra analysis.

Stop at 6 fetches or 9 combined search/fetch attempts. Never call a

plan-management tool or `tool_result_search`. Never call `publish_outputs` on this fast path.

```bash

"$ORKAS_NODE" "$ORKAS_PC_DIR/bin/run-skill.cjs" content-writer research_gate -- RESEARCH_LEDGER.json --format json

```

- Draft completed research only on `READY_TO_DRAFT`. On

`CONTINUE_RESEARCH`, read `missing_families` from the gate output. Make one

recovery fetch and a second/final gate only when one unused specific result

can plausibly make that gate `READY_TO_DRAFT`: its title, snippet, and

publisher cover every reported missing family and its one new independent URL

satisfies the remaining `source_deficit`. A merely reputable or related page

is not a recovery candidate. After an initial fetch error, a

title/snippet-matched saved result for that exact missing family qualifies.

If no qualifying candidate exists, do not fetch,

rewrite the ledger, or gate again; immediately deliver dated confirmed

findings, exact missing families, the specific source/data needed next, and

`HOLD`.

- Here `bash` is only for the exact `research_gate` above, never retrieval,

parsing, inspection, conversion, or recovery. After the first gate, the only

permitted shell call is the final gate after one qualifying recovery fetch.

- The gate verifies collection completeness, not truth, freshness, provenance,

source independence beyond URL deduplication, or claim entailment.

### 3. Draft

- Draft section by section from the evidence-backed outline.

- For workplace-productivity posts, include at least two qualitative input-to-output mini-examples (for example, scattered notes to decisions/owners/deadlines; blank brief to audience/questions/outline). Never invent time saved or outcome metrics. Add one copy-ready prompt using `[输入材料]`, `[输出格式]`, `[读者]`, and `[待核验项]`. Make `[输出格式]` a per-scenario placeholder for meetings, writing, or information compression, not fixed meeting fields, so only that value needs editing.

- For short social copy, end the main post with an explicit interaction CTA (comment, save, share, or try), then append a compact block with two alternate headlines, one alternate CTA, and editable hashtags. Localize its heading: `可替换选项` in Chinese; `Replaceable options` in English.

- When no evidence is supplied, exact percentages, amounts, rankings, adoption counts, before/after durations, and quantified performance or outcome claims are unsupported even as hooks. Replace them with qualitative reader situations rather than presenting invented proof.

- In `adapt` mode, change shape/phrasing only. Preserve supplied claim set, citations, and disclosures; add no interpretation, implication, bridge claim, or broader conclusion. A headline is also a claim: restate only an explicit source proposition; add no comparison, surprise, trend, prevalence, urgency, or popularity. Newsletter: make the first line `主题：...`; if `/report` is supplied, make the only CTA `[阅读全文](/report)`.

- For any unfamiliar channel, choose title/lead, order, detail, rhythm, and close around the reader's job; do not stretch it into an article or generic promo.

- Lead each section with its useful point, not meta commentary about what the section will do.

- Place citations next to the sentence or paragraph they support. A sources list alone is not claim support.

- Separate sourced fact, user-provided claim, inference, and opinion in wording.

- Use concrete examples only when real or clearly labeled as hypothetical.

- Never invent facts, statistics, quotes, people, credentials, sources, dates, links, cases, customers, experience, endorsements, outcomes, or approvals.

- When a citation fails to support a stronger claim, state the exact additional evidence needed: population, exposure/intervention, measured outcome, baseline/comparator, time window, and method as applicable.

### 4. Revise, humanize, and audit

- Before `revise` or `humanize`, read

[editorial-quality.md](references/editorial-quality.md). Use distinct

developmental edit, evidence edit, line edit, and copy edit passes.

- Build a voice fingerprint from representative samples when available.

Preserve facts, scope, certainty, citations, disclosures, terminology, and

author-specific choices. Never fabricate experience or certify human

authorship.

- Treat every new transition, implication, recommendation, and forecast as a

claim. Delete unsupported material without replacement; keep a deletion blacklist

so paraphrases do not reappear.

- For contradiction change notes, record `rejected value → accepted value` or

the rejected claim → supported replacement plus its evidence basis.

- For deterministic audit, readiness, decision tokens, handoff, or final audit

formatting, read

[audit-and-delivery.md](references/audit-and-delivery.md). Use only the

canonical `audit_content` Skill Runner commands documented there; otherwise

label findings `MANUAL PREFLIGHT — SCRIPT NOT RUN`.

## Apply format and delivery rules

- Read [content-formats.md](references/content-formats.md) for a social post,

newsletter, tutorial, case study, opinion piece, research explainer,

SEO-oriented article, adaptation, or unfamiliar format.

- For an ordinary time-boxed current-research analysis, use a title, scoped

findings, limitations, and sources without loading the format reference.

- A completed-research artifact requires `READY_TO_DRAFT`. Publication

decisions use exactly one token: `READY`, `READY AFTER FIXES`, or `HOLD`.

## Non-negotiable limits

- Preserve required disclosures, citations, compliance language, and safety warnings unless the user explicitly replaces them with approved language.

- Protect confidential material and personal data; do not expose more source content than the task needs.

- Distinguish source quality from source agreement. Ten pages repeating one press release are not ten independent confirmations.

- Require qualified review for high-stakes legal, medical, financial, regulatory, or safety claims. When an unsupported high-stakes input is plainly unsafe and must be held, do not persist the blocked input as `ARTICLE.md` or another deliverable merely to run preflight. Skip that runner input, label the result `MANUAL PREFLIGHT — SCRIPT NOT RUN`, and return `HOLD`, the risks, a safe replacement, and the qualified-review requirement.

- Do not publish or operate external platforms.