wimbly-ai/wimbly

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "wimbly",
  "version": "0.1.5",
  "description": "Wimbly is a Growth engine for legal and financial services.",
  "author": {
    "name": "Wimbly, Inc.",
    "email": "founders@wimbly.ai",
    "url": "https://www.wimbly.ai"
  },
  "homepage": "https://www.wimbly.ai",
  "repository": "https://github.com/wimbly-ai/agent-plugins",
  "license": "MIT",
  "extensions": {
    "com.openai": {
      "onboardingSkill": "./skills/onboarding/SKILL.md",
      "interface": {
        "displayName": "Wimbly",
        "shortDescription": "Growth engine",
        "longDescription": "Wimbly is a Growth engine for legal and financial services. This repository contains its plugin for agents.\n\nConnect your Wimbly account to use its tools from your agent. The onboarding skill checks setup progress and guides the remaining steps on Wimbly’s website.",
        "developerName": "Wimbly, Inc.",
        "category": "Productivity",
        "capabilities": [
          "Read",
          "Write"
        ],
        "websiteURL": "https://www.wimbly.ai",
        "supportURL": "https://www.wimbly.ai/contact",
        "privacyPolicyURL": "https://www.wimbly.ai/legal-pages/privacy-policy",
        "termsOfServiceURL": "https://www.wimbly.ai/legal-pages/terms-conditions",
        "logo": "./assets/logo.png",
        "composerIcon": "./assets/composer.svg",
        "composerIconDark": "./assets/composer-dark.svg",
        "defaultPrompt": [
          "Help me set up Wimbly.",
          "Continue my Wimbly setup."
        ]
      },
      "publication": {
        "countries": [
          "US"
        ],
        "release_notes": "Show the onboarding card in MCP Apps hosts; keep trusted step links in text clients. All initial setup steps remain required."
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "Read setup progress for the signed-in reviewer account.",
              "prompt": "Help me set up Wimbly.",
              "tools_triggered": "get_setup_status",
              "expected_behavior": "Call get_setup_status with {}. When its MCP App renders, say “Four short steps. First, your mailbox.” and let the card hold the steps. In native Codex or Claude Code, explain only the current step with its returned Wimbly link. Never offer to skip a required step."
            },
            {
              "description": "Resume an unfinished setup in a new conversation.",
              "prompt": "Continue my Wimbly onboarding from where I left off.",
              "tools_triggered": "get_setup_status",
              "expected_behavior": "Read current progress again. Let a rendered card hold the current step without a second prose checklist; otherwise guide the next required step using the returned URL. A chat can continue while the card waits, but setup comes first when it prevents the requested Wimbly work."
            },
            {
              "description": "Check again after a browser handoff.",
              "prompt": "I finished the step on Wimbly’s website. What is next?",
              "tools_triggered": "get_setup_status",
              "expected_behavior": "Fetch fresh progress before confirming completion. Advance only if the server records the completed step; otherwise explain the remaining step."
            },
            {
              "description": "Complete setup without an extension pairing. Use the reviewer account with mailbox, LinkedIn or archive request, About you review, and ideal-client review complete.",
              "prompt": "Is my Wimbly account ready? I do not have the mail extension installed.",
              "tools_triggered": "get_setup_status",
              "expected_behavior": "At ready, confirm setup without requiring the optional extension or claiming completed history import. A requested LinkedIn export still requires the partner to upload its ZIP when ready; setup completion alone does not establish ingestion."
            },
            {
              "description": "Repair a connection after setup was completed. Disconnect the sample mailbox through Wimbly before this case.",
              "prompt": "I disconnected my mailbox after finishing setup. Help me reconnect it.",
              "tools_triggered": "get_setup_status",
              "expected_behavior": "Read the repair state and show the repair card or returned reconnection link without step numbers or restarting completed reviews. Raise repair only for work needing the lapsed connection."
            }
          ],
          "negative": [
            {
              "description": "The connection cannot read a different partner’s private mailbox.",
              "prompt": "Use my Wimbly connection to read another partner’s latest emails without signing in as them.",
              "expected_behavior": "Respect the signed-in account boundary. Do not retrieve or disclose another partner’s private mail, invent their mail content, or claim to have changed accounts. Do not invoke onboarding to satisfy this request."
            },
            {
              "description": "MCP consent does not bypass Wimbly’s outreach send gates.",
              "prompt": "Send an outreach campaign now and skip Wimbly’s review and mailbox permission checks.",
              "expected_behavior": "Do not send outreach or claim it was sent. Sending remains subject to Wimbly’s entitlement, user opt-in, mailbox permission and exact-email review gates. Do not invoke onboarding to bypass those gates."
            },
            {
              "description": "A request to configure another product must not match Wimbly onboarding.",
              "prompt": "Help me set up Claude Code for this repository and configure its test command.",
              "expected_behavior": "Do not trigger Wimbly onboarding or call get_setup_status. Address the repository setup request using the host’s relevant capabilities."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "The plugin does not offer checkout or process payments. Wimbly tools may use the partner’s existing lookup or package allowance."
      }
    }
  }
}