brand
無料Apply this site's visual identity — colours, type, logo files and fixed brand strings. Use for any page, component, social asset or document that should look like the site.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a page or the whole yoursite site (or a new site) for indexing readiness — cache headers, sitemap, robots, canonical, JSON-LD, internal links — and check the publish pipeline (Cloudflare purge/warm, IndexNow, GSC, Bing). Use before/after publishing content or launching a site.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read docs/SEO_PLAYBOOK.md first; it holds the automation matrix and checklists. This skill is the
procedure. Report findings; do not post to third-party sites and do not click "Request Indexing".
curl -s https://www.example.com/robots.txt and /sitemap.xml: robots allows crawling,
sitemap lists every published page, every <loc> returns 200 (loop with curl -o /dev/null -w "%{http_code}").content-type: text/html, cache-control has s-maxage and no
no-store, cf-cache-status is HIT or MISS (not BYPASS/DYNAMIC on public pages).curl -s): exactly one <h1>, <title> ≤60, meta description ≤160, rel="canonical",
JSON-LD parses as JSON, body text is present in the raw HTML.href="/..." from the homepage and blog index; any sitemap URL not linked
from anywhere is an orphan. Report orphans.urlInspection via /admin/analytics/seo): list URLs "Discovered
curl -sI <url>: 200, cacheable, HIT within a minute of publish (warm step ran)./sitemap.xml and /llms.txt.[indexnow]), GSC sitemap resubmitted.Follow section 5 of the playbook. Needs a human for: GSC/Bing verification, Cloudflare token, Request Indexing.
Produce drafts only (syndication copy with canonical URL, Reddit/Quora answer outlines, directory listing text). List where each should go; the human posts them.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Apply this site's visual identity — colours, type, logo files and fixed brand strings. Use for any page, component, social asset or document that should look like the site.
日本語の概要は準備中です。原文の説明を表示しています。
Use FIRST when someone asks for a new feature or a change to an existing one — before any schema, code or test. Works out what is actually being asked for, whether to build it or integrate a third party (Trustpilot, Stripe, Calendly and the like), where the data lives, who may do what, and what happens when the vendor is down. Produces a decision, then hands to feature-schema.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a new feature needs a table, column or capability — evolving the schema so the new thing joins the permission, audit and RLS contract instead of sitting outside it. Covers the DDL/DML split, the resource/capability wiring, and the self-verifying migration.
日本語の概要は準備中です。原文の説明を表示しています。
Use after building a feature — explore it in a real browser to find what nobody predicted, then turn each finding into a deterministic test that guards it forever. Covers the agentic pass, what to generate vs hand-write, and how to skip honestly when a capability is missing.
日本語の概要は準備中です。原文の説明を表示しています。
Publishing content or deploying site-os — what caches exist, what refreshes them, and how to prove a change is actually live. Use when publishing a post or product, launching a page, deploying, or when someone says a change "isn't showing".
日本語の概要は準備中です。原文の説明を表示しています。
Handling secrets, keys and credentials for site-os — reading vigyan-secrets.md safely, moving keys into app_secrets, rotating, and responding to an exposure. Use whenever a task touches a key, token, password, .env file, app_secrets, encryption, or the secrets document.
日本語の概要は準備中です。原文の説明を表示しています。