Content Writer Agent Skill
Write SEO-optimized blog posts, landing pages, and content improvements following Google's E-E-A-T and Helpful Content guidelines.
- Context cost
- —no SKILL.md at its top, so a client loads nothing
- Bundle
- 3 files · 33.6 kBtext throughout, nothing executable
- Licence
- MITthe author’s own terms
- Last change
- —no release on file
- Servers it uses
- Noneruns standalone
What it does
Write SEO-optimized blog posts, landing pages, and content improvements following Google's E-E-A-T and Helpful Content guidelines. Handles new content creation from a keyword or topic, and improving existing pages. Use when asked to "write a blog post", "create a landing page", "improve this page", "write content about X", "content for keyword X", "draft an article", "blog post about", "landing page for", "service page", "product page copy", "rewrite this page", "make this page rank better", "content brief", "how-to guide", "listicle", or any content creation or improvement task for a website.
Installed, it changes the agent in these ways.
What this skill changes about the agent has not been set out here as a list. Its SKILL.md has not been published here, so the description above is all that is on file.
And these are the jobs people reach for it for.
The skill itself
A client finds a skill by the SKILL.md at the top of its folder, and this folder has none — so there is no instruction file to show here, and nothing a client would load.
The folder behind this listing has no SKILL.md at its top, and that is the file a client loads a skill from. What is here comes from the catalogue record and the file listing further down.
Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.
What it costs in context
Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.
This folder has no SKILL.md at its top. A client loads a skill from that file — its front matter every session, its body when it triggers — so from this folder it loads nothing, and there is no context cost to measure.
A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.
Before and after
The same question, put to the same model twice: once as it comes, and once with these instructions loaded.
No worked example has been published for this skill yet.
The procedure it runs
The procedure has not been published here. It is in the skill’s own SKILL.md, which has not been published to the marketplace yet.
These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.
Servers it uses
None. This skill calls no MCP servers at all.
Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.
Its SKILL.md is not published here, so nothing on this page says which tools it asks the agent for — read the instructions before you install it.
This skill’s SKILL.md is not published here, so neither can be read off it. A skill grants no permissions of its own — it can only ask for tools your client already has.
What it will not do
Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.
What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.
What is in the bundle
3 files, 33.6 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.
- WORKFLOW.md13.9 kB
- evals/evals.json3.5 kB
- references/content-writing.md16.2 kB
No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 3 files with no SKILL.md at its top: a client loads nothing from it, and there is nothing to install.
Install
Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.
This folder has no SKILL.md at its top, and a client only loads a skill from that file — so there is nothing here to install.Which clients pick it up on their own
A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.
Versions
Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.
Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.
Reviews
Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.
A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.
Sign inAnybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.