スキルを探す

Discover keyword opportunities, evaluate metrics and SERPs, and save/tag promising terms.

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

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

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

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".

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

Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.

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

Verify the OpenSEO MCP server end-to-end on a local dev server — protocol-level correctness against real DataForSEO, then a headless-agent consumer probe that tests tool ergonomics (descriptions, schemas, output size, errors, async flows) without the maintainer manually driving an MCP client. Use after adding or changing MCP tools, or when asked to check that the MCP "works" or "is ergonomic".

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

Review a PR for code that can be deleted or simplified. Use when asked to review for simplicity or unnecessary edge-case overengineering.

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

Get a branch ready for the maintainer's final review: review it for security, simplicity, and billing abuse, fix what's real, get checks passing, and open or update the PR. Use whenever the user says a feature, fix, or branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").

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

Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically. Use when asked to review Cloudflare logs/observability, count OOMs or worker errors, compare error rates between periods, or investigate a prod error spike.

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

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.

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

Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

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

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. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.

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

Audit a Google Business Profile, compare it to local competitors, and map Maps visibility around a location.

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

Populate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake.

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

Set up OpenSEO in the current AI agent. Use when a user pastes the OpenSEO installation prompt or asks to connect its plugin, MCP, and skills.

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

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.

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

Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff. Use when the user asks "how do I review this", "summarize the changes", "what should I look at", or wants to understand a PR in under two minutes.

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

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

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

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.

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

Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save. Use when editing a product skill (seo-audit, keyword-research, ...) and you need evidence that the new instructions produce better output, not just a cleaner file.

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

Enumerate and screenshot every UI state a PR adds or changes. Use when asked to show, capture, or screenshot the UI states of a PR or branch.

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

Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.

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

Cluster keywords by intent and map them to existing or proposed pages.

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

Invoke whenever writing, changing, reviewing, or sweeping Vitest tests in this repo. Authoring gate for new or changed tests, plus an audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they keep alive. Use when asked to add tests, review tests, clean up tests, or when a PR touches *.test.ts.

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

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 will cost the next contributor time. Also use to review, deduplicate, and resolve existing entries. Gate hard before logging: only friction the repository itself can fix counts. Never log the agent's own sandbox/permission errors, shell-scripting mistakes, transient flakiness, or third-party tool quirks the repo can't change.

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