seo-project-setup
Technical SEOevery-app/open-seoskills.sh ↗
Installs
3,588
deduplicated, at the last sync
Since we started
+15%
35 readings, about 2 hours apart. Not a live curve.
Our category
Technical SEO
ours
Last read
Sep 3, 2026
from the directory
Our brief
oursThis skill guides the user through setting up and populating a project's shared SEO context within OpenSEO. It collects essential information about a website or SEO project, including its scope, business goals, market positioning, key competitors, and important pages. The gathered data is stored in the project's central context for use by other agents and skills.
- Updated project context (scope, goals, etc.)
- Recommended next SEO workflow
- OpenSEO MCP access
- Project ID
not detected
The evidence states that the two project-context MCP tools used for writing are free and spend no credits.
not detected
The evidence does not mention any registration requirements for using this skill.
The skill cannot perform a full SEO audit or live research unless the user asks for it. It also cannot assume facts; all information must be confirmed with the user before being saved to the project context.
Evidence.agents/skills/seo-project-setup/SKILL.md:1-196
---
name: seo-project-setup
description: Populate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake.
---
# OpenSEO SEO Project Setup
## Goal
Interview the user once about one website or SEO project, and store the answers in that project's shared context in OpenSEO with `update_project_context`. That context is read by every other skill, by SAM in the app, and by the user on the project's Context settings page — so it survives new sessions, new machines, and new agents. This is a context setup workflow, not a full audit.
## Tone
Be friendly, practical, and structured. Ask questions in small batches. Explain why each item matters only when useful. Do not overwhelm a beginner with jargon.
## Where the answers go
Two project-context MCP tools do all the writing. Both are free — they spend no credits.
- `get_project_context(projectId)`: everything already known about the project, plus a `missingSections` list.
- `update_project_context(projectId, updates)`: a list of patch ops. The ones this skill uses:
- `{ section: "business_overview" | "current_goal" | "positioning" | "wriRead 1 of 1 text files in the skill.
Installfrom the directory
npx skills add https://github.com/every-app/open-seoInstalling happens there, not here. We are an index with an opinion, not a mirror.
What is inside itfrom the directory
1 files — names only. The directory does not report sizes.
What the auditors foundfrom the directory
A skill is instructions your agent will follow and scripts it may run, so who checked it matters as much as how many people installed it.
Installs, reading by readingours
Axis starts at 3.1k, not zero — the range is 3.1k to 3.6k.
Asked out loudspoken, not typed
The same skill in the words people use speaking to an assistant rather than typing into a box. Each one carries the situation it came from, and each answer says only what the skill's own files support.
The evidence indicates that the project context tools used by this skill are free and do not spend credits. However, it does not provide information on any potential costs associated with connecting services or running research.
The skill collects details like the site's scope, business goals, market positioning, key competitors, and important pages. This data is stored in a central project context for later use.
No, the skill is designed to read what is already known about the project and confirm or correct existing entries rather than re-asking questions that have been answered.