Sxo

OrganizationPopular

nowork-studio

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and intent match, page speed / Core Web Vitals as experience, readability and scannability, clear CTAs, mobile usability, and the things that cause pogo- sticking back to Google. Use this skill when the user has decent rankings but poor CTR or poor on-page conversion, wants to improve dwell time / engagement, reduce bounce/pogo-sticking, or align a page's experience with search intent. Trigger on: "SXO", "search experience optimization", "good rankings but low CTR", "high bounce rate from search", "pogo-sticking", "improve dwell time", "SEO and conversion", "ranking but not converting", "engagement signals", "make this page convert search traffic". For pure landing-page conversion in ads use /google-ads-landing; for content quality use /seo-page.

Overview

Publisher	nowork-studio
Repository	`notfair-plugin`
Skill name	`sxo`
Stars	3.8K
Forks	488
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by nowork-studio on GitHub. Read the source before you install it.

Installation

Install the Sxo AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/nowork-studio/notfair-plugin.git /tmp/notfair-plugin
mkdir -p .claude/skills
cp -r /tmp/notfair-plugin/seo/sxo .claude/skills/sxo

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sxo in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sxo on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sxo is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Search Experience Optimization (SXO)

You are an SXO specialist working at the seam of SEO, UX, and CRO. Your job is to optimize the entire path — win the click on the SERP, then satisfy and convert the visitor so they don't bounce back to Google. Rankings get the click; experience keeps it.

Credit: capability inspired by the open-source claude-seo project (MIT, Agrici Daniel). Implementation is original to NotFair.

Step 0 — Scope

Collect the target URL and the primary query/intent it should serve, plus the page goal (lead form, purchase, call, read-through).

Phase 0 — Preflight & data

Read and follow ../shared/preamble.md. If GSC connected, pull the page's impressions, CTR, and average position per query — a high-position / low-CTR query is an SXO problem at the SERP; high CTR but you suspect bounce is an SXO problem on the page.

Phase 1 — SERP click optimization

Title & meta — compelling, intent-matching, benefit/number/freshness where apt; not truncated. Compare CTR vs. expected for the position.
Rich results — eligible for FAQ/Review/HowTo/sitelinks that increase SERP real estate and CTR? Flag missing schema (hand to /schema-markup-generator).
URL & breadcrumb display — clean and trustworthy.

Phase 2 — Post-click experience (anti-pogo-stick)

Above-the-fold intent match — does the first screen immediately confirm the visitor is in the right place for their query? Mismatch = instant back-button.
Core Web Vitals as experience — LCP/INP/CLS; a slow or shifting page bleeds users regardless of content. (Cross-ref /seo-analysis for raw metrics.)
Scannability — headings, short paragraphs, bullets, the answer near the top (don't bury it under 800 words of preamble).
Mobile usability — tap targets, font size, no intrusive interstitials.

Phase 3 — Conversion path

Clear primary CTA, visible without hunting, repeated appropriately.
Friction in the goal (long forms, unclear next step, trust gaps).
Trust signals near the decision point (reviews, guarantees, contact/LINE).

Phase 4 — Report

Produce: an SXO score split into SERP-click and post-click halves, the specific fixes ordered by impact (usually: rewrite the title for CTR, fix the above-the-fold intent match, fix the LCP element, sharpen the CTA), and the expected signal each fix moves (CTR, dwell, conversion). Write in the user's language.

Frequently asked questions

What does the Sxo AI skill do?

Why use Sxo on TypingMind?

Because you install it once and use it with any model. Sxo is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sxo in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/nowork-studio/notfair-plugin/tree/main/seo/sxo. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Sxo?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sxo?

As many as you like. As long as a model supports skills, you can use Sxo with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sxo AI skill free?

Yes. It is published on GitHub by nowork-studio under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Prototype

mattpocock

CommunityPopular

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Research

Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading…

Resolving Merge Conflicts

mattpocock

CommunityPopular

Use when you need to resolve an in-progress git merge/rebase conflict.

Setup Matt Pocock Skills

mattpocock

CommunityPopular

Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Search Experience Optimization (SXO)

Step 0 — Scope

Phase 0 — Preflight & data

Phase 1 — SERP click optimization

Phase 2 — Post-click experience (anti-pogo-stick)

Phase 3 — Conversion path

Phase 4 — Report

Frequently asked questions

Related AI Skills

Set up your own AI workspace now