本文へ移動
cccskills
無料GitHub で公開

openseo-review-web-content

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Find the questions people ask about a market, how ChatGPT answers them, and which sites get cited in the answers. Use when the user asks what people ask AI about their niche, wants prompt ideas, or wants to know where their brand is missing before choosing prompts to track. Research only; it never saves tracking or starts answer collection.

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

Audit how a brand shows up in AI answers about its market and deliver a short report on the few changes most likely to get it mentioned or cited, such as a third-party page to get onto, an owned page to improve, or an access problem to fix. Use when the user asks for an AI visibility audit, a GEO or AEO audit, why AI recommends competitors instead of them, or how to show up in ChatGPT, Gemini or Google AI answers.

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

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 product skills. Use whenever adding a new skill, converting a workflow into a skill, or when .claude/skills and .agents/skills look out of sync.

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

deslop

無料

Remove AI writing patterns from prose so it reads like a person wrote it. Use when writing, editing, or reviewing user-facing text (blog posts, docs, marketing copy, PR descriptions), or when asked to "deslop", "de-AI", or "make it sound human".

日本語の概要は準備中です。原文の説明を表示しています。

every-app/open-seo2.3万2026年10月9日 更新

every-app のスキルをすべて見る

このスキルの問題を報告する