CtrlK
BlogDocsLog inGet started
Tessl Logo

open-seo

github.com/every-app/open-seo

SkillAddedReview
observability-triage

.agents/skills/observability-triage/SKILL.md

Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, a known-noise filter list applied automatically, and the on-demand CPU/heap profiling recipe. Use when asked to review Cloudflare logs/observability, count OOMs or worker errors, compare error rates between periods, investigate a prod error spike, or find where a worker spends CPU or memory (profiles, flamegraphs).

75

openseo-release-notes

.agents/skills/openseo-release-notes/SKILL.md

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.

75

openseo-review-web-content

.agents/skills/openseo-review-web-content/SKILL.md

Write and review content for the OpenSEO website (web/), including 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.

72

papercuts

.agents/skills/papercuts/SKILL.md

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.

71

review-brief

.agents/skills/review-brief/SKILL.md

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.

72

review-simplify

.agents/skills/review-simplify/SKILL.md

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

65

review-ui-states

.agents/skills/review-ui-states/SKILL.md

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.

64

seo-audit

.agents/skills/seo-audit/SKILL.md

Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.

67

seo-audit

plugins/openseo/skills/seo-audit/SKILL.md

Audit a website, investigate its real search opportunities, and deliver a short data-backed report on the few changes most likely to grow organic traffic that converts.

61

seo-coach

.agents/skills/seo-coach/SKILL.md

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

63

seo-coach

plugins/openseo/skills/seo-coach/SKILL.md

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

59

seo-project-setup

.agents/skills/seo-project-setup/SKILL.md

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

63

seo-project-setup

plugins/openseo/skills/seo-project-setup/SKILL.md

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

65

seo-report

.agents/skills/seo-report/SKILL.md

Write and save an OpenSEO report as one self-contained HTML page. Use when a skill has finished its research, and whenever the user asks for a report, check-in, or summary, or names a report template.

65

seo-report

plugins/openseo/skills/seo-report/SKILL.md

Write and save an OpenSEO report as one self-contained HTML page. Use when a skill has finished its research, and whenever the user asks for a report, check-in, or summary, or names a report template.

68

setup-openseo

.agents/skills/setup-openseo/SKILL.md

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.

69

simple-issue-description

.agents/skills/simple-issue-description/SKILL.md

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.

71

takeover

.agents/skills/takeover/SKILL.md

Take over a public (every-app/open-seo) PR, or a branch or agent thread, and finish it in the private repo while keeping the original contributors' credit in the merged commit. Use when the user asks to take over, finish, adopt, or land someone else's PR, or when triage decides a contributor's PR should ship.

76

test-audit

.agents/skills/test-audit/SKILL.md

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.

75

verify-local-mcp

.agents/skills/verify-local-mcp/SKILL.md

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

—

—