菜单
Run an SEO audit on a service in Payload CMS and store the score. Use when asked to "SEO check service", "audit service SEO", "score service ProtonMail".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Research multiple services in parallel using subagents. Each service gets the full research pass — vendor site, pricing, privacy/GDPR, Reddit sentiment, and recent news — written to both existing research fields and the newer structured fields (userSentiment, redditMentions, recentNews). Use when asked to "research all services", "bulk research", "research these services", or need to populate Research tabs for many services at once.
Post-publish SEO audit on a live page. Pulls GSC performance data, Jina Search for competitor SERP + content, current page content from Payload, and (optionally) Unlighthouse scores. Writes a prioritised rewrite plan to the pageAudits collection. Use when asked to "audit this page", "seo audit", "what's wrong with this page's SEO", "analyze ranking performance".
Surgically edit Payload CMS rich-text fields via the Payload MCP. Swap link URLs across all rich-text fields of a doc (including per-step `content` for guides), with optional visible-text rewriting. Pure MCP — no scripts, no file paths. Use when fixing broken outbound links from an SEO crawl, retargeting a vendor's canonical URL, or otherwise rewriting URLs inside published content.
Produce a ranked backlog of content ideas grounded in real signals. Mode A mines GSC for queries we don't rank for; Mode B mines Reddit and Jina SERP for services and categories we don't cover. Writes ranked findings to the contentOpportunities collection. Use when asked to "find opportunities", "what should we write next", "seo backlog", "content gaps".
Research a digital service and store structured findings in Payload CMS. Gathers company basics, pricing, privacy posture, Reddit sentiment, and recent news via Jina Reader/Search and the Reddit MCP. Use when asked to research a service, investigate a company, gather pricing/privacy/compliance data, or populate the Research tab on a service. Trigger phrases include "research this service", "investigate", "gather data on", "fill in research for".
ALWAYS use when writing code importing "unlighthouse". Consult for debugging, best practices, or modifying unlighthouse.
| name | seo-check-service |
| description | Run an SEO audit on a service in Payload CMS and store the score. Use when asked to "SEO check service", "audit service SEO", "score service ProtonMail". |
| argument-hint | '<service name>' |
Audit a service listing against a 10-point SEO checklist. Store score and notes via MCP.
Before starting, read: .claude/skills/_shared/seo-checklist.md for the scoring system and note format.
Item 5 — Content Length:
description 50-200 chars AND content body 300+ wordsItem 6 — Internal Context:
category set, features has 3+ items, tags has 2+ itemsItem 8 — Image:
screenshot or logo presentUse mcp__Payload__findServices:
{"where": "{\"name\": {\"contains\": \"SERVICE_NAME\"}}", "limit": 1}
Get all fields including SEO tab fields (metaTitle, metaDescription, keywords, ogTitle, ogDescription).
Apply the checklist from _shared/seo-checklist.md with the thresholds defined above for items 5, 6, and 8.
Pricing subpage (if pricingTiers or pricingDetails exist):
startingPrice is setfreeOption is set correctlypricingTiers has structured dataSecurity subpage (if security data exists):
gdprCompliance is set (not "unknown")certifications has entriesdataStorageLocations has entriesComparison subpages (from guides):
sourceService and targetServiceInclude subpage issues in seoNotes under a "Subpages" section. These don't affect the main score.
Use mcp__Payload__updateServices:
seoScore: the number (0-100)seoNotes: formatted summary (see _shared/seo-checklist.md)lastSeoReviewAt: today's date in ISO formatmetaTitle or metaDescription are empty, populate with suggestionsShow the user: score and rating, table of all 10 checks, subpage audit results, top 3 priority fixes.