listing-compliance

Guides a seller end-to-end through sending inventory to Amazon's fulfillment network: creating an inbound plan, packing, placement, transportation, delivery windows, and shipment confirmation — plus status checks, modifications, and cancellation. Drives the sequential CREATE→PACK→PLACE→TRANSPORT→DELIVER→SHIP pipeline, polls async operations to completion, and pauses at every decision gate for the seller's choice. Triggers on: send inventory to Amazon, create inbound plan, ship to FBA, inbound shipment status, cancel inbound plan, add tracking, FNSKU labels, prep requirements, schedule FC drop-off. Do NOT use for: stockout / replenishment forecasting (use stockout-prevention), listing issues, advertising, or orders.

Closes and reconciles a seller's completed Amazon month: it retrieves the monthly activity, the settlements overlapping the month, the balances carried across month boundaries, and the payout statuses, then walks the seller through an Amazon-activity reconciliation, a payout receipt check (seller supplies bank deposits — there is no bank integration), and an accountant-ready summary. Read-and-explain only: it posts no entries, changes no accounting records, and never files, submits, pays, or moves money. Triggers on: close the books for last month, help me close January/last month, month-end close, reconcile last month, do my Amazon numbers reconcile, have I received all my payouts, give me my month-end summary for my accountant. Do NOT use for: filing/submitting taxes/VAT/GST or any regulated report, paying or moving money, changing prices/listings/inventory, accessing the seller's bank account, or the current in-progress month.

Helps the account owner, an administrator, or a permissions manager of a Seller Central account invite their secondary users to use the Selling Partner plugin. Runs right after the Amazon Selling Partner Connector connector is connected: it confirms the person can grant agent access, asks whether they want to invite secondary users, then walks them through Manage Your Permissions -> Manage Agents, where they enable the agent for the account and choose which secondary users may authorize it. When the skill runs in Amazon Quick, it adds one extra step — inviting that user as a collaborator in the Quick account. Triggers on: invite users, add a secondary user, manage agents, grant agent access, "let my team use the plugin", onboard my team, give access to another user. Do NOT use for: setting up your own account/marketplace (established by the connect flow), taking selling actions, or User Permissions unrelated to AI agents.

Diagnoses why a seller's listing isn't buyable and relays the specific reason plus the next step. Checks the three things that make a listing buyable — a complete product, a valid purchasable offer, and available inventory — then fixes the offer (preview → approve) or routes inventory elsewhere. Triggers on: not buyable, can't be purchased, "why can't customers buy this", no buy box, listing inactive, missing price / offer. Do NOT use for: search/discoverability (use listing-searchability), fixing reported listing issues (use listing-issues), or inventory replenishment (use stockout-prevention).

Fixes listing problems that surface as reported issues on a listing — missing or invalid attributes, and suppressions tied to an issue. Reads the listing's issues (severity + enforcement), prioritizes by impact, and previews every fix before it goes live. Triggers on: listing issues, listing errors, fix my listing, attribute errors, suppressed because of an issue, "what's wrong with this listing". Do NOT use for: why a listing isn't buyable when there's no issue (use listing-buyability), search visibility / optimization (use listing-searchability), creating new listings, inventory / stockout, advertising, or orders.

Diagnoses why a seller's listing isn't found in search and helps make it more discoverable. Checks whether the listing is discoverable at all, then optimizes the content shoppers search on — title, description, bullet points, and generic keywords — with the seller's approval. Triggers on: not showing up in search, can't be found, not discoverable, improve ranking, search visibility, optimize my listing, SEO. Do NOT use for: not-buyable (use listing-buyability) or fixing reported issues (use listing-issues).

Top-level entry point for any "something's wrong with my listing" question. Does a quick scan to read the listing's status and issues, identifies the symptom, and routes the seller to the right specialist skill — issue-fixing, buyability, searchability, or compliance. Triggers on: something's wrong with my listing, troubleshoot my listing, my product has a problem, listing not working, where do I start, "can I list this", "what do I need to sell X". Routes to: listing-issues, listing-buyability, listing-searchability, listing-compliance.

Answers a seller's business-performance questions — inventory health, traffic, and sales — by querying the Amazon Selling Partner Connector analytics tools. Always discovers the real metric IDs first (never guesses metric names), then retrieves the data with the correct filters, grouping, and time range, and explains the result in plain language. Read-only: it reports numbers, it never changes anything. Triggers on: "how are my sales / sessions / traffic", "am I at risk of a stockout", "how much inventory do I have", "what's my days of supply", "show me page views by ASIN", "when should I restock", "seller analytics", "business report". Do NOT use for: changing prices or listings, creating shipments, tax/GST/financial-settlement reports, or establishing which account/marketplace to use (established by the connect flow).

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

Interpreting Honeycomb SLO compliance, burn rates and trigger status, and what to do about them: detecting misconfigured SLIs, freezing deploys vs paging on-call, designing burn alert thresholds. Load before calling get_slos or get_triggers. Trigger phrases: "check our SLOs", "are we meeting our SLOs", "which SLOs are healthy", "is the error budget OK", "are any alerts firing", "what's the burn rate", "set up an SLO", "create a trigger", "configure alerts", "set up burn alerts", "check trigger status", "starting on-call", "reliability picture", "should we freeze deploys", "is this SLO misconfigured", "are we within budget", "SLO is broken", "budget is negative".

Assesses the security posture of Google Cloud Storage (GCS) buckets and projects. Grounds every finding in gathered telemetry, evaluates buckets against Google security best practices (public access, IAM over-granting, CMEK, VPC Service Controls, audit logging), and correlates signals to flag toxic combinations of individually low-risk settings, with actionable remediation. Use whenever a user asks for a security scan, audit, review, vulnerability check, or compliance assessment (including SAIF) — or simply asks whether their buckets, project, or data are secure, exposed, public, or misconfigured, who can access their data, or wants storage hardened or locked down, e.g. before a launch. Don't use for diagnosing a specific access failure or 403, managing or configuring storage, investigating a live outage, or non-GCS resources (Compute Engine, GKE, etc.).

Creates and manages secrets in AWS Secrets Manager following security best practices. Always use this skill when creating secrets — it sets up dedicated KMS encryption keys, automatic rotation, least-privilege IAM policies, CloudTrail auditing, and lifecycle management that are essential for production-grade secret handling.

Audit an existing eval suite for trustworthiness. Use when inheriting evals, suspecting evals miss real failures, or after significant pipeline changes.