Playbooks your agent follows, not improvises
Each skill tells your agent exactly which tools to call, in what order, and what not to conclude. Connect a source, ask the question, and the matching playbook is picked up automatically.
SEO
30 skillsSEO: audit, diagnose and improve organic search
Start hereStart here for any SEO or organic search question, including vague ones: something feels off with our Google numbers, how is our site doing in search, audit our SEO, give me an honest summary of SEO for leadership, why did traffic or rankings drop, what should we fix or write next. Covers Search Console and GA4 organic data, keywords and rankings, CTR, cannibalization, content decay, competitors and backlinks, keyword gaps, indexing and sitemaps, technical audits, redirects, metadata, internal links, AI crawlers, llms.txt and AI search visibility, and which organic pages convert or earn revenue. Connects the right accounts, routes to the focused playbook, and sets the evidence rules every SEO answer follows.
Analyze high-ranking landing pages
See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.
Audit internal links to important pages
Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.
Audit or draft an llms.txt
Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.
Audit redirect chains and loops
Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.
Audit referring domain quality
Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.
Audit titles and meta descriptions
Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.
Backlink profile health check
See who links to the site and whether the backlink profile is healthy: referring domains, authority distribution, anchor text mix, dofollow share and concentration risk from Ahrefs, optionally compared against a competitor.
Check AI crawler access
Check whether ChatGPT, Claude, Perplexity, Gemini and other AI assistants can crawl and read the site or docs, and whether anything needs to be done so they pick it up: parse robots.txt and meta robots for GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended and Bingbot, so allowing or blocking them is a deliberate decision rather than an accident.
Check sitemap health
Check that the site's XML sitemaps are submitted, fresh, error-free and complete: compare submitted vs indexed counts in Search Console, find sitemap URLs that redirect or return errors, and find pages with search traffic that the sitemap does not list.
Check whether organic traffic converts
Find which pages get search traffic but few signups, orders or purchases: join Search Console pages to GA4 landing-page engagement and conversions to see which organic pages, product pages and category pages actually convert, which attract visits that bounce, and where the gap between ranking and outcome is widest.
Competitor keyword gap analysis
Compare what competitors rank for against your own coverage to find high-value keywords you're missing entirely.
Content decay audit
Identify pages whose search traffic is declining over time so refreshes go to the content that's actually slipping.
Debug why a page is not indexed
Find out why a specific page is missing from Google, or used to show up in search and has now disappeared: inspect its index status and coverage state, the canonical Google chose, robots.txt and noindex blocks, fetch errors and sitemap membership, then check the live page, and end with the one fix that applies.
Find a competitor's new backlinks and turn them into prospects
Find the new backlinks a competitor has earned recently, where they came from and how they got them, then turn the pattern into a prospect list: which sites are linking to competitors in your space right now, which competitor pages attract links, and which of those sites already link to a rival but not to you.
Find new and lost search queries
Find the new keywords the site started ranking for this month and the search queries it stopped appearing for, by comparing two periods, so you can see which new content is winning and where visibility quietly disappeared.
Find page-one rankings with weak CTR
Find the queries and pages that already rank on Google's first page but get fewer clicks than their position should earn, so the fastest wins come from rewriting titles and descriptions instead of building new content.
Find queries that fell off page one
List the search queries that recently dropped out of Google's top ten results between two periods, with the pages that lost them, so ranking losses are caught while they are still cheap to recover.
Find striking-distance keywords
Find the keywords the site almost ranks on page one for: queries sitting at positions 8 to 20 with real impressions, where a small push produces the biggest traffic gain for the least work.
Find where paid search overlaps organic
Compare the pages the site already ranks for organically against the landing pages receiving paid search clicks in GA4, to find where ads are buying visits organic would deliver anyway, and where paid traffic reveals demand organic has not captured.
Investigate an organic traffic drop
Find out why organic clicks or traffic fell, exactly when it started, and whether the cause is a ranking loss, a demand change, a technical problem, a Google update or a tracking gap, using Search Console and GA4 evidence instead of guesswork.
Keyword cannibalization check
Find out whether two or more of your own pages or blog posts cover the same ground and compete for the same keyword, cannibalizing each other and splitting clicks, and whether to merge them, differentiate them or leave them alone.
Measure traffic from AI assistants
Measure how many sessions ChatGPT, Perplexity, Claude, Gemini, Copilot and other AI assistants send to the site in GA4, which pages they land on, whether those visitors convert, and how the trend compares with Google organic.
Recover lost backlinks
Find the backlinks a site recently lost, work out why each one disappeared (the linked page was removed, the link was edited out, a redirect broke), and build a prioritised list of links worth recovering with a fix on your side or a short outreach.
Review index coverage of important pages
Estimate how well the pages that matter are indexed when the Coverage report is not available through the API: combine Search Console page data with the sitemap and URL inspection of a prioritised sample to find pages Google has dropped, pages with the wrong canonical, and sitemap URLs that never earn an impression.
Run a technical SEO audit
Check the pages that matter for status codes, canonicals, noindex tags, titles, headings and sitemap coverage, prioritised by the Search Console traffic each page earns, so technical fixes go where they protect the most visits.
Split brand vs non-brand search traffic
Separate branded searches from non-brand organic traffic to see whether SEO is actually growing, how dependent the site is on people already searching for the brand, and which trend the headline Search Console numbers are hiding.
Tear down a competitor's top pages
See which of a competitor's pages earn the most organic traffic, what each one ranks for, which formats and topics keep winning for them, and which of those the site has no answer to yet.
Trace organic search to revenue and pipeline
Find which keywords and pages bring in paying customers: follow organic search all the way to purchases in GA4 or contacts and closed deals in HubSpot, so SEO is measured in revenue and pipeline instead of clicks.
Turn search demand into a content plan
Find content gaps and plan what to write next from Search Console data: group the queries the site already gets impressions for into topic clusters, map each cluster to the page that serves it, and surface clusters with real demand but no dedicated page.
Marketing
2 skillsAcquisition channel performance
Compare traffic sources and marketing channels on volume, engagement and conversion rate to decide where to spend more and where to cut: which channel gives the best return, whether to shift budget between paid, organic, referral and email, and how each is trending.
Lead source to revenue attribution
Measure marketing ROI by source: trace channels and campaigns through to closed revenue by joining CRM deals with payment records, so revenue per lead and return on spend are known instead of stopping at lead counts.
Sequel CLI
Install Sequel skills into your agent
One command connects your agent to Sequel and installs the Sequel skill, so it knows these playbooks exist and reads the right one when a question matches. The CLI signs you in, provisions a scoped API key and writes the config for you.
Already have an MCP client?
https://api.sequel.sh/mcp
Point it at this URL and sign in when prompted, or send an API key from Settings as a Bearer token. Skills come with it; nothing else to install. Manual setup per client
- 1
Install the Sequel CLI
One line installs the latest CLI with whatever package manager you have.
curl -fsSL https://sequel.sh/install | sh - 2
Sign in
Authenticate in your browser and pick an organization.
sequel login - 3
Install into your agent
Writes the MCP config and installs the Sequel skill file for agents that support skills. Pick an agent from the list, or target one directly by its slug.
sequel install- Claude Code
sequel install claude-code - Claude
sequel install claude - Cursor
sequel install cursor - VS Code
sequel install vscode - Windsurf
sequel install windsurf - Zed
sequel install zed - Codex
sequel install codex - OpenClaw
sequel install openclaw - Hermes
sequel install hermes
FAQ
Questions about skills
- What is a Sequel skill?
- A playbook for one specific job: which connected tools to call, in what order, with what parameters, and the gotchas that produce a confidently wrong answer. Your agent reads it and follows it instead of designing its own approach from scratch.
- How does my agent find the right skill?
- You ask a question. Sequel's search returns the skills that match it alongside your data sources, and the agent reads the best fit. Broad questions land on an entry skill that routes to the focused playbook. Nothing to configure.
- Which agents can use them?
- Any agent that speaks MCP: Claude Code, Claude Desktop, Cursor, VS Code, Codex, Windsurf, Zed and more. Run sequel install and the CLI writes the MCP config and installs the Sequel skill for you.
- Do I need every connector a skill lists?
- No. The apps on a skill are advisory. If one is not connected, the agent runs the steps the connected sources support and tells you which it skipped. If a required source is missing, it offers to connect it in one click.
- Can I request a skill or customise an existing one?
- The catalogue is open: file an issue or PR in the public repository if a playbook is missing a step or you want a new one. The skills ship as code, so any change reaches every agent that reads them on the next deploy.
Give your agent the playbook
Connect a source, ask a question, and watch the agent follow the skill step by step. Free to start.