every-app

17 skills

keyword-researchevery-app5.4KDiscover keyword opportunities, evaluate metrics and SERPs, and save/tag promising terms.competitor-analysisevery-app5.2KAnalyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps.keyword-clusteringevery-app5.2KCluster keywords by intent and map them to existing or proposed pages.seo-coachevery-app5.2KEnter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.seo-project-setupevery-app5.2KPopulate a project's shared OpenSEO context — site scope, goals, positioning, competitors, key pages, and preferences — plus MCP checks and Search Console intake.competitive-landscapeevery-app5.2KMap SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.link-prospectingevery-app5.2KFind link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.seo-auditevery-app3.8KAudit 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.local-seoevery-app2.9KAudit a Google Business Profile, compare it to local competitors, and map Maps visibility around a location.simple-issue-descriptionevery-app2.9KTurn 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.merge-readyevery-app2.3KTake a branch from "code exists (or is about to)" to "ready for the maintainer's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/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").openseo-release-notesevery-app2KCut 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.maintain-greptile-rulesevery-app2KEvaluate verified findings from merge-ready, Greptile, pull-request, CI, security, billing, and other code reviews, then promote durable review gaps into the version-controlled .greptile configuration. Use when a review uncovers a recurring or high-risk repository invariant that Greptile does not capture, when Greptile repeatedly produces a false positive, or when asked to audit or update OpenSEO's Greptile rules and context.papercutsevery-app1.6KLog 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 quir deslopevery-app1.5KRemove AI writing patterns from prose. Use this skill when writing, drafting, editing, reviewing, or revising any text to eliminate predictable AI tells, slop, and formulaic patterns. Trigger this skill whenever the user asks to "deslop", "de-AI", "make it sound human," "remove AI patterns," "remove AI tropes," "clean up AI writing," fix "slop," "deslop" text, or review prose for authenticity. Also use when the user asks you to write or draft anything and wants it to sound natural rather than AI openseo-review-web-contentevery-app1.5KWrite and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.seo-reportevery-appWrite 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.