Blog Write
AgriciDaniel/claude-blog
Write new blog articles from scratch optimized for Google rankings and AI citations.
Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs.
Install Openseo Review Web Content
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install every-app/open-seo openseo-review-web-content --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .claude/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .claude/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-contentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install every-app/open-seo openseo-review-web-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .agents/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .agents/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install every-app/open-seo openseo-review-web-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .cursor/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .cursor/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/every-app/open-seo.git --path .agents/skills/openseo-review-web-content--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install every-app/open-seo openseo-review-web-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .gemini/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .gemini/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install every-app/open-seo openseo-review-web-contentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .github/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .github/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add every-app/open-seo --skill openseo-review-web-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install every-app/open-seo openseo-review-web-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/every-app/open-seo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/openseo-review-web-content .opencode/skills/openseo-review-web-content && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openseo-review-web-content" agent skill from https://github.com/every-app/open-seo/tree/main/.agents/skills/openseo-review-web-content into .opencode/skills/openseo-review-web-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openseo-review-web-content", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openseo-review-web-content- GitHub stars
- 23k
- Token cost
- ~495 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs.
- Editing user-facing prose in web/content
- SKILL.md covers Write for the reader, Cut what isn't for them, Don't make things up and Voice
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Blog and article writing
What it does
Openseo Review Web Content is an agent skill from every-app/open-seo. Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs. Makes sure each page delivers real value to its target reader. Use whenever adding or editing user-facing prose in web/content or web/src.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Blog and article writing and Help center and FAQ content. The repository describes itself as: Open source alternative to Semrush and Ahrefs. The licence is MIT.
When your agent uses it
- Editing user-facing prose in web/content
- Tasks that involve Blog and article writing
- Tasks that involve Help center and FAQ content
Example prompts
- “/openseo-review-web-content”
What it can do on your machine
Read from SKILL.md and the folder at commit 89e5a00. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openseo Review Web Content loads about 495 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 272 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from every-app/open-seo at commit 89e5a00, republished under its MIT licence (© every-app). 272 words, ~495 tokens.
Download SKILL.mdSave it as
.claude/skills/openseo-review-web-content/SKILL.md (or your agent's skills folder).- name
- openseo-review-web-content
- description
- Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs. Makes sure each page delivers real value to its target reader. Use whenever adding or editing user-facing prose in web/content or web/src.
- metadata
- internal: true
OpenSEO Web Content
Every page is for a specific reader. A blog post should leave them better at SEO. A product page should help them decide whether OpenSEO solves their problem. Judge every edit by one question: is this better for that reader? We are not writing to pass a review.
Write for the reader
- Say up front what the reader will get, in their terms.
- Organize around their job, not the source material. Interviews become a plan, not a roundup of quotes.
- Carry one real example through, with real numbers.
- Use lists instead of dense paragraphs: bullet points for things the reader needs to do or check, and numbered lists for steps in order.
- Give practical advice, even when it's messier than the official rules.
- Answer straight. "No" and "it costs money" are complete answers.
Cut what isn't for them
- Notes for whoever checks the draft: method footers, "verbatim" assurances, tool or API names, "re-checked on" dates.
- Hedges that protect the writer, and links or asides that interrupt.
- Anything that reads like an ad. A company used as an example is there to teach.
Don't make things up
That's the whole accuracy bar. Product capabilities, prices, quotes, and data must be real, so check product claims against the code. Framing, figures of speech, and opinions are the writer's call. Don't ask for disclosures or a source for every number. Never call OpenSEO simply "free."
Voice
Use the deslop skill for AI tells. When editing someone else's post, keep their voice and examples. In the playbook library, an approach is a "strategy," never a "play."
Run prettier on the files you touch.
© every-app, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/openseo-review-web-content of every-app/open-seo.
Open the folder on GitHubat commit 89e5a00
Compare with similar skills
Openseo Review Web Content next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openseo Review Web Content this skillevery-app/open-seo | 23k | — | ~495 | Automated safety check: Pass | MIT | |
| Blog WriteAgriciDaniel/claude-blog | 2.3k | 1 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Blog WriteAgriciDaniel/claude-blog | 2.3k | — | ~5.6k | Automated safety check: Pass | MIT | |
| Writerflaqai/backlink_skills | 756 | — | ~5.8k | Automated safety check: Pass | MIT | |
| Article Writingericrisco/rsc-harness | 180 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Prompt Gap To Publishamplitude/builder-skills | 159 | — | ~2.8k | Automated safety check: Pass | None |
Similar skills
Blog Write
AgriciDaniel/claude-blog
Write new blog articles from scratch optimized for Google rankings and AI citations.
Writer
flaqai/backlink_skills
SEO-friendly article writing, audit, and humanization workflow for Markdown content.
Article Writing
ericrisco/rsc-harness
A skill your agent uses 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…
Prompt Gap To Publish
amplitude/builder-skills
A skill your agent uses whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low…
SEO Aeo Blog Writer
henryalouf/ruflow
Writes long-form blog posts with TL;DR block, definition sentence, comparison table, and 5-question FAQ for SEO ranking and AEO citation.
More from every-app/open-seo
All 19 skills in this repoEvaluate Skill
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
Create Repo Skill
every-app/open-seo
Create or update a skill in this repository the right way — canonical home in .agents/skills, internal-vs-public marking, symlink mirroring into .claude/skills, and public docs registration for…
Deslop
every-app/open-seo
Remove AI writing patterns from prose so it reads like a person wrote it.
Observability Triage
every-app/open-seo
Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.
Papercuts
every-app/open-seo
Log genuine, recurring repository friction to .agents/PAPERCUTS.md — confusing setup, a flaky repo command or script, a misleading in-repo error, stale generated files, or a non-obvious gotcha that…
Simple Issue Description
every-app/open-seo
Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.
Related
Categories
Questions about Openseo Review Web Content
What does Openseo Review Web Content do?
Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs. Openseo Review Web Content is an agent skill from every-app/open-seo. Write and review content for the OpenSEO website (web/): blog posts, guides, feature pages, FAQs.
When should I use Openseo Review Web Content?
Openseo Review Web Content fits situations like: editing user-facing prose in web/content; tasks that involve Blog and article writing; tasks that involve Help center and FAQ content.
How do I install Openseo Review Web Content in Claude Code?
Run `npx skills add every-app/open-seo --skill openseo-review-web-content -a claude-code`. Or copy the skill folder (.agents/skills/openseo-review-web-content in every-app/open-seo) into .claude/skills/openseo-review-web-content in your project. Claude Code loads it when a task matches its description.
How do I install Openseo Review Web Content in Codex?
Run `npx skills add every-app/open-seo --skill openseo-review-web-content -a codex`. Or copy the skill folder (.agents/skills/openseo-review-web-content in every-app/open-seo) into .agents/skills/openseo-review-web-content in your project. Codex loads it when a task matches its description.
Can I use Openseo Review Web Content in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add every-app/open-seo --skill openseo-review-web-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openseo-review-web-content, .gemini/skills/openseo-review-web-content, .github/skills/openseo-review-web-content and .opencode/skills/openseo-review-web-content in your project.
What does Openseo Review Web Content need to run?
SKILL.md names no scripts, command-line tools or credentials: Openseo Review Web Content is instructions for the agent only.
Does Openseo Review Web Content access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Openseo Review Web Content safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openseo Review Web Content use?
Openseo Review Web Content is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openseo Review Web Content use?
About 495 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openseo Review Web Content?
Skills that share tags, products or a category with Openseo Review Web Content: Blog Write (AgriciDaniel/claude-blog, 2.3k stars), Blog Write (AgriciDaniel/claude-blog, 2.3k stars), Writer (flaqai/backlink_skills, 756 stars) and Article Writing (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openseo Review Web Content?
every-app (a GitHub organization) maintains it in every-app/open-seo, which has 22,922 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.
Source: every-app/open-seo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.