sales-bagisto

Solid

Bagisto platform help — open-source (MIT) Laravel/PHP eCommerce framework for developers and makers: products, orders, carts, customers, and checkout via a REST API and a GraphQL API (Shop + Admin), plus multi-vendor marketplace, POS, B2B, and multi-channel/headless storefronts, self-hosted or on Bagisto Cloud. Use when building a Bagisto REST or GraphQL integration, authenticating requests (Laravel Sanctum bearer token, X-STOREFRONT-KEY storefront key, or JWT for the headless package), creating a guest cart token, pulling products/orders into a CRM or warehouse, fixing a broken install or slow page loads, fixing broken images after an APP_URL change, choosing self-host vs Bagisto Cloud, or comparing Bagisto to Medusa/Saleor/Shopify. Do NOT use for cross-cart checkout-conversion strategy (use /sales-checkout) or picking a Merchant of Record for global tax (use /sales-merchant-of-record).

API & Backend 92 stars 11 forks Updated 2 days ago

Install

Quality Score: 82/100

Stars 20%

66

Recency 20%

100

Frontmatter 20%

70

Documentation 15%

100

Issue Health 10%

50

License 10%

0

Description 5%

100

Skill Content

# Bagisto Platform Help ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated platform knowledge. Figure out what the user actually needs before diving in: - **Goal** — building/debugging an API integration, syncing orders/products to a CRM or warehouse, a checkout/conversion question, an install/ops problem, or a platform-selection decision? - **Surface** — REST API (`/api/shop`, `/api/admin`), GraphQL API (`/api/graphql`), the older headless `bagisto/graphql-api` package (`/graphql`), the admin panel UI, or a marketplace/POS add-on? - **Auth** — Laravel **Sanctum bearer token**, the **`X-STOREFRONT-KEY`** storefront key, a guest **cart token**, or **JWT** (legacy headless package)? - **Hosting** — self-hosted (own infra: PHP/Laravel + MySQL/MariaDB + Redis) or **Bagisto Cloud** (managed)? - **Version** — Bagisto 2.x line (current; v2.4.x as of mid-2026)? API packages need 2.3.0+. Skip-ahead rule: if the prompt already says what they need, go straight to Step 2. ## Step 2 — Route or answer directly If the question is really a cross-platform strategy, hand off with the exact command: | If the user wants… | Route to | |---|---| | Checkout conversion / order bumps / cart-abandonment tactics across carts | `/sales-checkout {question}` | | Whether to use a Merchant of Record for global VAT/sales tax | `/sales-merchant-of-record {question}` | | Digital-product pricing & launch strategy | `/sales-digital-products {question}` | | Post-...

Details

Author: sales-skills
Repository: sales-skills/sales
Created: 4 months ago
Last Updated: 2 days ago
Language: Python
License: None

Integrates with

Shopify · Commerce Redis · Database MySQL · Database Laravel · Backend GraphQL · API REST API · API

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

sales-ahrefs

Ahrefs (ahrefs.com) platform help — industry-leading SEO toolset: Site Explorer (backlinks, organic keywords, Domain Rating), Keywords Explorer, Rank Tracker, Site Audit, Content Explorer, and Brand Radar AI-visibility. REST API v3 (api.ahrefs.com/v3, Bearer key, metered API units; v2 now discontinued) plus an official MCP server (Claude/ChatGPT/Cursor, Lite+). Use when building an Ahrefs API integration, your API units or monthly credits keep running out, setting up the Ahrefs MCP server with Claude, migrating off the dead v2 API to v3, getting throttled or locked by the 'suspicious activity' system within your limits, pulling backlinks/keywords/DR into a warehouse or report, deciding if you need the paid API subscription vs Enterprise, or choosing Starter vs Lite vs Standard vs Advanced. Do NOT use for SEO strategy or tool selection across vendors (use /sales-seo), AI-search-visibility tracking strategy across tools (use /sales-ai-visibility), or content optimization strategy (use /sales-seo).

92 Updated 2 days ago

API & Backend Solid

sales-adbutler

AdButler platform help — full-stack ad server for display, video, mobile, native, and email ads with self-serve advertiser portal, programmatic SSP, REST API, MCP server, and cookieless targeting. Use when setting up AdButler to monetize your newsletter or website with ads, email ad zone tags aren't rendering in Outlook or dark mode, API calls to the management or reporting endpoints are failing, self-serve portal setup for letting advertisers book their own campaigns, ad revenue is underperforming and you need to optimize targeting or demand sources, trying to decide between AdButler and alternatives like Kevel or Google Ad Manager, or need help with the AdButler MCP server for AI-powered ad ops. Do NOT use for general newsletter monetization strategy (use /sales-newsletter) or newsletter sponsorship marketplace transactions (use /sales-paved or /sales-hecto).

92 Updated 2 days ago

API & Backend Solid

sales-attio

Attio platform help — AI-native CRM with custom objects, relationship database, deal pipelines, email sequences, automations, and built-in enrichment for 80,000+ startups. Covers custom data model design (objects, attributes, relationships), pipeline configuration, workflow automations, email sequences, AI agents (Ask Attio), reporting, API integration (REST, OAuth 2.0, 100+ endpoints, webhooks, MCP server), and pricing tiers (Free/Plus/Pro/Enterprise). Use when Attio data model doesn't fit your workflow, deal pipeline stages need restructuring, automations aren't firing correctly, API or webhook integration isn't working, or not sure if Attio is the right CRM for your team. Do NOT use for general CRM data hygiene strategy (use /sales-data-hygiene), outbound sequences across platforms (use /sales-cadence), contact enrichment strategy (use /sales-enrich), or tool integration patterns (use /sales-integration).

92 Updated 2 days ago