27 skills (repositories by every-app) · sorted by popularity
Turn completed SEO research into a single HTML report saved in OpenSEO. Organize conclusions, evidence, and recommended actions in a format that supports phone reading and printing to PDF, with optional project templates.
Record recurring setup and workflow problems that a repository can fix, so future contributors can avoid the same friction. Also review existing entries, remove duplicates, prioritize useful fixes, and preserve a history of resolved problems.
Write and review OpenSEO website copy, including blog posts, guides, feature pages, and FAQs. Shape content around the reader's task, preserve an existing author's voice, remove promotional filler, and verify product claims against the code.
Audit how a brand appears in AI answers by examining mentions, website citations, competitors, and cited pages. Receive one to three evidence-based priorities, such as improving a page, seeking inclusion in a relevant source, or fixing access barriers.
Turn topics, products, or audience problems into a prioritized keyword list. Compare search volume, ranking difficulty, search intent, and search results to recommend target terms and pages, with optional saving and tagging after confirmation.
Turn rough bug reports, feature requests, support notes, or pull requests into concise issues. Explain the current problem and desired behavior in plain language, preserving useful evidence without prescribing how developers should implement a solution.
List and capture every interface state added or changed by a pull request, a proposed code change. Include error states, toggles, buttons, forms, and edited pages so reviewers can inspect their appearance.
Group keywords by what searchers want and assign each group to an existing or proposed page. Produce a page map, priorities, and content briefs, while checking whether multiple pages compete for the same searches.
Investigate OpenSEO production errors in Cloudflare Workers Observability. Count worker invocations accurately, compare periods and deployment versions, and filter previously investigated noise to focus analysis on errors that need attention.
Prepare an OpenSEO release by updating the version, selecting user-visible changes from commits, and writing concise release notes. Review agents check the draft against the code before a pull request is opened for the release.
Audit a website’s search visibility, content, and search demand to identify one to three priority improvements. Produce a concise, evidence-backed report focused on unpaid search visits from likely customers, with clear actions and limits.
Prepare a development branch for final maintainer review by checking security, unnecessary complexity, and billing abuse risks. Fix confirmed issues, run local checks and tests, then push changes and create or update the pull request.
Evaluate Vitest tests by the observable behavior and realistic regressions they protect. Guide new test authoring and review existing suites for duplication, dependence on implementation details, and code used only by tests, with evidence for retention or removal.
Audit a Google Business Profile and compare it with nearby competitors. Review listing details, customer reviews, and Maps rankings at points around the business to identify visibility gaps and prioritize fixes.
Research questions about a market, examine recorded ChatGPT answers and cited websites, and identify themes where a brand appears or is missing. Receive ranked prompt groups and suggested questions for future tracking.
Set up shared SEO project information in OpenSEO through a guided interview. Save website scope, goals, positioning, competitors, key pages, and writing preferences, then check connections and prepare Google Search Console data for later workflows.
Create or update skills using OpenSEO's repository conventions. Keep one canonical source, distinguish internal and public workflows, maintain Claude Code links, and register public skills in documentation, the in-app agent, and plugin bundles.
Edit blog posts, documentation, marketing copy, and PR descriptions to remove formulaic AI writing patterns. Replace filler, vague claims, and staged emphasis with plain statements while preserving concrete details and the writer's voice.
Get practical SEO guidance based on a site's goals and existing data. Understand OpenSEO workflows, choose a next step, and learn when to use search performance data, web search, or page content extraction.
Find relevant sites, pages, and authors that might link to a resource or product. Use search results and competitor backlink signals to prioritize prospects, locate public contact paths, and draft outreach messages tailored to each opportunity.
Analyze a named competitor's unpaid search traffic, ranking keywords, content themes, and links from other websites. Identify strengths, weaknesses, and relevant opportunities, with an optional comparison to your own site and a report of recommended actions.
Compare several competitors to see which sites lead a search market, what content earns rankings, and where opportunities remain. The report covers keyword reach, links from other sites, and practical next steps.
Evaluate changes to OpenSEO skills by running fresh Codex sessions against a local backend. Compare saved reports using weighted criteria, then inspect tool logs to understand failures and check whether revised instructions improve output.
Set up OpenSEO in an AI agent through its plugin or MCP connection, a way to access external tools. The workflow checks skills, guides sign-in, verifies access, and explains any manual steps needed.