seller-analytics

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).

Pre-flight compliance gate before any listing write. Identifies which Amazon listing and regulatory requirements (FDA, EPA, CPSC, FCC, FTC, disclosures, GTIN, category gating) apply, asks the seller once for the facts only they know, checks account-side gating, and holds the write until the seller gives an explicit go. Triggers on: "can I list this", "what do I need to sell X", "is this compliant", listing requirements, help me list, or when a sibling listing skill is about to change product claims, ingredients, category, condition, images, or identifiers. Do NOT use for: reported issues (listing-issues), buyability (listing-buyability), search optimization (listing-searchability), or general program-policy Q&A unrelated to listings.

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.

About 450 ready-made HyperFrames blocks and components installed as editable source - transitions, overlays, titles, kinetic type, captions, charts, map overlays, 3D, camera moves. Use it before hand-building any named visual (CRT scanlines, glitch, film grain, a chart); also for hyperframes add and catalog.

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.

Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.

Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.

Obtain or reuse a Prisma Postgres database and connect an application. Use when the user needs a database and has none configured ("I need a database", "add a Postgres database", "set up a database for this app"), runs or mentions `create-db` or `npx create-db`, or asks to set up or connect Prisma Postgres, including in v0 and the Vercel Marketplace. Hands Prisma ORM configuration to prisma-orm-setup; reuses an existing connection first and honors an explicit provider, driver, alternative ORM, or database-only choice.

Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).

Guides and best practices for working with Lakebase Postgres on Neon: connections, pooled vs direct, schema migrations, branching (including schema-only, reset-from-parent, and branch-per-PR workflows), autoscaling, scale-to-zero, instant restore, read replicas, IP allow lists, logical replication, egress optimization, and Lakebase Search. Use when the work is an existing DATABASE_URL, SQL, schema, inspect, or search. New backends, Auth, files, Functions, and LLM calls go to the parent `neon` skill. Live queries, reactive UIs, and realtime data go to `neon-realtime`. Also use for "@neondatabase/serverless", "@neon/neon-js", "neon inspect db", "neon postgres computes", "Neon branch", "schema-only branch", "reset branch", "branch per PR", high database bills, network transfer or egress, SELECT * optimization, query overfetching, "semantic search", "vector search", "full-text search", "BM25", or "hybrid search".