Sitebulb Cloud

sitebulb-dev-handoff

Turn Sitebulb audit findings into dev-ready tickets in the connected PM tool (Jira, Linear, Asana, Monday, or ClickUp): one ticket per selected issue — what's wrong, why it matters, the true affected-URL count with labelled sample URLs and a pointer to the full export in the Sitebulb app, a suggested fix with its knowledge-base link, acceptance criteria, severity-mapped priority, and an effort estimate (size and duration) — every draft previewed in chat before anything is created, falling back to markdown ticket bodies when no PM tool is connected. Use when the user wants to raise, create, push, or log tickets/tasks/issues from crawl or audit findings — "send these to Jira", "ticket the quick wins", "hand the 404s to the devs", "make Linear issues for these" — not for triggering crawls, since it reads Sitebulb read-only.

sitebulb-release-check

Run the user's configured post-release watch-list check on a Sitebulb project: compare the latest finished audit against the previous one, evaluate each watched item against the thresholds in this file's settings block (project, watch-list, thresholds and alert channel live there — the first run asks setup once and hands the filled block back to paste in), treat changes the user names as deliberate as confirmations rather than breaches, then post a breach alert via a connected messaging or project tool — in chat when none is connected — or give a two-to-four-sentence all-clear. Strictly user-invoked; it cannot schedule itself or trigger crawls. Use for "run my Tuesday check", "release check", "run my watch-list", "run my release check on [project name]", or the user's own named check ritual. Not for open-ended "what changed" or "did the release break anything" change-story conversations — that is the sitebulb-what-changed skill; this is the configured ritual with thresholds and alerts.

sitebulb-technical-seo-audit

Produce the client-facing technical SEO audit document from a Sitebulb project's latest finished audit: a focused Word working draft of 5–10 issues — never encyclopaedic — selected and ordered by why the audit was commissioned (traffic decline, redesign/migration, onboarding, due diligence), written for the stated reader, each issue carrying its true affected count, labelled sample URLs, a Sitebulb-app export pointer, a knowledge-base link, and a recommendation with owner and indicative effort. Ships seeded with consultant-facing review comments marking where human judgment is needed. Use whenever the user asks for a 'technical SEO audit', 'client audit', 'audit document', or 'audit deliverable', says 'write up the audit for [client]' or 'run the audit on [project]', or hands off from a prioritised read ('need this as a client document'). Not for conversational what-to-fix triage (sitebulb-what-to-fix-first), change-over-time stories (sitebulb-what-changed), or dev tickets (sitebulb-dev-handoff).

sitebulb-what-changed

Tell the change story between a Sitebulb project's two most recent audits — wins first, then regressions, then a watch-list, each with what it means and whether it needs action — reframed for the business's situation, with a Google Analytics/Search Console overlay where connected, evidence cards showing per-hint deltas, and an optional self-contained HTML dashboard. Use for "what changed since last crawl", "monthly check", "progress since last month", "did we get better or worse", "did the release/deploy break anything", "did the migration cause this", or prepping a client update — including a "client meeting in 20 minutes" short version. Not for full-site triage (sitebulb-what-to-fix-first), raising dev tickets (sitebulb-dev-handoff), client audit documents (sitebulb-technical-seo-audit), or configured watch-list/threshold alerting (sitebulb-release-check).

sitebulb-what-to-fix-first

Produce a prioritised read of a Sitebulb audit — the 3–5 issue clusters most worth fixing for this business in this situation — by interviewing for business context, sweeping triggered hints, and scoring impact (severity × section tier × effective coverage × traffic linkage) against effort (fix archetype, S–XL, owner, indicative duration), with context reframing what leads but never the scores. Use for "what should I fix first", "what's wrong with this site", "where do I start", "prioritise this crawl/audit", "quick wins", "what's worth my attention", or any effort-vs-impact triage of Sitebulb findings. Not for raising dev tickets (sitebulb-dev-handoff), change-over-time stories (sitebulb-what-changed), or client documents (sitebulb-technical-seo-audit).