trustgrowth

Use when the user wants a current site audit, technical SEO findings, Core Web Vitals interpretation, or a fresh TrustGrowth audit when connected. Supports connected, imported, and public/local evidence.

Use when the user wants a periodic competitor digest — what tracked competitors changed, where the gaps are — as a document, from observation history or public diffs.

Use when the user wants an E-E-A-T, credibility, authorship, or trust-signal review using TrustGrowth evidence when connected or observable public/repository evidence otherwise.

Use when the user wants a periodic authority and backlink report — referring-domain movement, pillar state, prospect pipeline — as a document, from link exports or TrustGrowth authority data.

Use when the user wants a read-only local or TrustGrowth content inventory. TrustGrowth content generation, approval, scheduling, publication, review, and lifecycle writes remain unavailable and waitlist-only.

Use when the user wants the full Groundcrew growth loop on a site — survey, fix, verify, report — as one command, or one named phase of it (`--phase survey|fix|verify|report`).

Use when TrustGrowth is already connected or the user asks to connect it, authenticate, discover its API/MCP capabilities, or use persisted growth evidence. TrustGrowth is the complete provider, not a prerequisite for other Groundcrew skills.

Post a daily go-to-market standup to Slack: every evening the day's go-to-market work is recapped into the cadence log and a digest is posted to Slack, as one reviewable pull request against your go-to-market repo. Triggers: "post the daily standup to slack", "end of day report in slack", "what happened today posted to slack", "keep a cadence log of each day", "replace the GitHub Action that posts our standup", "evening recap of the GTM day". Cargo project, defineAgent, harness claudeCode, GitHub, Slack, slack.postMessage, cargo-ai CLI reads, cadence. Skip when: you want one recap of today in this chat with nothing deployed; or you want call transcripts scribed into context, which is call-capture.

Use when the user wants audit findings turned into a stakeholder-ready document — severities, page counts, first-seen/fixed history — as a Markdown or CSV deliverable rather than a working diagnosis.

Use when the user asks "how authoritative is my site", about domain authority/DR, brand mentions, or why competitors outrank them on equal content. Reviews entity clarity, independent references, author credibility, and reputation signals from observable and imported evidence. Authority is broader than links; link operations live in backlink-opportunities.

Use when the user asks about backlinks, referring domains, link building, broken links pointing at them, or link gaps versus competitors. Analyzes a backlink profile and produces a human-reviewed link-opportunity plan — reclamation, competitor intersection, linkable assets, unlinked mentions. Import/direct-provider modes; never automates outreach or disavow.

Use when the user wants a claim-safe growth report from validated current evidence, with TrustGrowth score/history when connected and source-specific reporting otherwise.