メニュー
Run an SEO audit on a migration guide in Payload CMS and store the score. Use when asked to "SEO check guide", "audit guide SEO", "score guide gmail-to-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-guide |
| description | Run an SEO audit on a migration guide in Payload CMS and store the score. Use when asked to "SEO check guide", "audit guide SEO", "score guide gmail-to-protonmail". |
| argument-hint | '<guide slug>' |
Audit a migration guide 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:
intro + steps + troubleshooting total 500+ wordsItem 6 — Internal Context:
sourceService and targetService set, difficulty set, category setItem 8 — Image:
Use mcp__Payload__findGuides:
{"where": "{\"slug\": {\"equals\": \"GUIDE_SLUG\"}}", "limit": 1}
Get all fields including SEO tab fields.
Apply the checklist from _shared/seo-checklist.md with the thresholds defined above for items 5, 6, and 8.
No subpage audit for guides.
Use mcp__Payload__updateGuides:
seoScore, seoNotes, lastSeoReviewAtmetaTitle / metaDescriptionShow the user: score and rating, table of all 10 checks, top 3 priority fixes.