- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ericrisco/rsc-harness --skill article-writing -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ericrisco/rsc-harness --skill article-writing -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ericrisco/rsc-harness --skill article-writing -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add ericrisco/rsc-harness --skill article-writing -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/ericrisco/rsc-harness/tree/HEAD/skills/article-writingFrom the publisher
Draft one long-form article end to end: the prose and the on-page surface that ships with it — answer-first lede, question-shaped headings, title tag, meta description, slug, FAQ block, and the JSON-LD that makes the piece machine-readable.
You own a single finished article. You do not pick the topic, build the calendar, or define the house voice — those are siblings below.
Rule: if the deliverable is not one publishable article, you are in the wrong skill.
Before you write a sentence, read the top of the SERP for the target query. Name two things: the dominant intent (informational, transactional, comparison, navigational) and the winning format Google already rewards (listicle, step guide, definition + table, comparison). Match that format — fighting the shape Google already chose loses.
Then set depth from intent, not from a number you were handed. The first-page Google average is ~1,447 words across 11.8M results (Backlinko) — a descriptive average, never a target. Thoroughness and intent satisfaction rank, not length.
Why: padding a 600-word answer to 2,000 to "look thorough" dilutes it and reads as filler. Cutting a guide to 800 words leaves the query half-answered. Length follows the question.
The first ~200 words must directly and completely answer the primary query. Lead with the answer (TL;DR-first / inverted pyramid), then expand. This is the structure that wins featured snippets and AI Overview citations — and with zero-click hitting ~60% of searches (2024) and AI Overviews appearing in ~13% of queries (May 2025), being the extracted answer matters more than the click.
## Should you compost in an apartment?
Composting has become increasingly popular in recent years as more people
look for sustainable lifestyle choices. Many city dwellers assume they can't
participate because of limited space. But is that really true? Let's explore
the fascinating world of urban composting and find out together.
## Can you compost in an apartment?
Yes — a sealed countertop bokashi bin or a small worm bin (vermicomposting)
lets you compost food scraps in a flat with no yard and no smell. Bokashi
ferments scraps in ~2 weeks; a worm bin yields finished compost in 3–6 months.
Here is how to choose between them and set one up in a 60×40 cm footprint.
If the query is a question, the H1 or first H2 should be that question and the next sentence should answer it. Worked lede examples are in references/on-page-seo.md.
Build the skeleton from real subtopics, not from what you feel like writing.
## How much does a standing desk cost? not ## The Price Question.Why question-shaped headings: only ~38% of pages cited in AI Overviews rank top-10, so clean, extractable, question→answer structure can win citations without traditional authority. Make every section answerable on its own.
Google does not penalize AI-assisted content as such. It penalizes scaled content abuse — high-volume, no-editorial-review, thin, no-first-hand-experience pages. The March 2026 core update named scaled content abuse a primary target; offending sites saw 50–80% traffic drops. The defense is not avoiding AI; it is genuine value, depth, and human review.
So every draft earns its keep with E-E-A-T (Experience, Expertise, Authoritativeness, Trust — Trust is the load-bearing member):
Run a human-review pass before ship. If nothing in the draft could only have been written by someone who actually knows the topic, it is thin — add experience or do not publish.
Every article ships with these. Keep them in the file's front-matter or a clearly labelled block so scripts/verify.sh can lint them.
/compost-in-apartment not /how-to-start-composting-in-your-apartment-today.Full pixel/char tables, slug rules, and copy-ready Article/BlogPosting + FAQPage JSON-LD (JSON-LD only — never microdata) live in references/on-page-seo.md. The JSON-LD must describe what is actually on the page; schema that does not match visible content is a quality flag, not a win.
Place 3–5 contextual internal links in the body of a standard article (more only for a long-form pillar). Rules:
worm bin setup guide, never click here or a bare URL.You insert the link slots and anchors that fit this article. Deciding the cluster structure — which pillar owns which clusters across the site — is ../content-engine/SKILL.md's job, not yours.
Do one ruthless pass: delete every sentence that adds no fact. If a sentence could sit in any article on any topic, it is filler.
Banned on sight (short sample): "In today's fast-paced world", "It's important to note that", "When it comes to", "Let's dive in", "the world of X", "navigating the landscape of", "unlock the power of", "in conclusion". The full banlist with Bad→Good rewrites and the depth self-review is in references/ai-tell-banlist.md — and that file is the single source verify.sh greps against.
In today's fast-paced world, it's important to note that choosing the right
standing desk can really make a difference when it comes to your health.
A standing desk adjustable from 70–120 cm fits users 1.5–2.0 m tall and cuts
the lower-back load reported across sit-all-day workdays.
Restating the gates verify.sh enforces, for the human review:
@type Article/BlogPosting; FAQPage too if an FAQ section existsRun scripts/verify.sh path/to/article.md. It is a lint of structure and banned phrasing — it does not judge whether the content is good. That is the capability eval's job, and yours.
Use when writing one long-form article end to end — answer-first lede, question-shaped headings, plus its on-page surface (title, meta, slug, FAQ, Article/FAQPage JSON-LD) — or fixing a draft that bur
---name: article-writingdescription: Use when writing one long-form article end to end — answer-first lede, question-shaped headings, plus its…---# skills/article-writing/SKILL.mdOverview
Use when writing one long-form article end to end — answer-first lede, question-shaped headings, plus its on-page surface (title, meta, slug, FAQ, Article/FAQPage JSON-LD) — or fixing a draft that buries the answer or reads AI-padded. NOT keyword research or topic selection (that is `seo-geo`), NOT the editorial calendar (that is `content-engine`).
FAQ
Download skills/article-writing/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/ericrisco/rsc-harness.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.