fba-inbound-management

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.

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

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts, rollback, and production infrastructure. Applies to any framework agents-cli deploys (ADK, LangChain, ...). Part of the agents-cli skills suite. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), evaluation (use google-agents-cli-eval), or project scaffolding (use google-agents-cli-scaffold).

This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers `agents-cli scaffold create`, `scaffold enhance`, and `scaffold upgrade` commands, template options, deployment targets, and the prototype-first workflow. Do NOT use for writing agent code (ADK projects: use google-agents-cli-adk-code) or deployment operations (use google-agents-cli-deploy).

This skill should be used when the user wants to "set up tracing", "monitor my agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring deployed agents, including ADK (Agent Development Kit) agents. Covers Cloud Trace, prompt-response logging, BigQuery Agent Analytics, third-party integrations (AgentOps, Phoenix, MLflow, etc.), and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment setup (use google-agents-cli-deploy) or API code patterns (use google-agents-cli-adk-code).

Deploy and operate apps on Prisma Compute with the Prisma 8 CLI. Use whenever the user mentions Prisma Compute, deploying or hosting a Prisma app, `prisma deploy`, `prisma dev module.ts`, Prisma Composer apps (`module.ts`, `compute()`, the `composer` section of `prisma.config.ts`), preview stages, deploy on push (`prisma git connect`, `prisma/cloud-deploy-action`), `prisma service` logs, versions, rollback, or custom domains, `project env`, `PRISMA_SERVICE_TOKEN`, regions, 504s, sleeping instances, or `waitUntil`; also when a project still uses the removed `@prisma/cli app deploy`, `prisma.compute.ts`, `defineComputeConfig`, `compute:deploy`, or `build logs` surface.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".