plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "sybill",
  "version": "1.0.9",
  "description": "Use Sybill's understanding of sales calls, deals, and pipeline to prepare meetings, draft follow-ups, inspect risk, and choose next steps.",
  "author": {
    "name": "Sybill Inc.",
    "url": "https://www.sybill.ai"
  },
  "homepage": "https://www.sybill.ai",
  "keywords": [
    "sales",
    "meeting-prep",
    "follow-ups",
    "deal-risk",
    "pipeline",
    "revops"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Sybill",
        "shortDescription": "Context layer for revenue orgs",
        "longDescription": "Sybill is the context layer for revenue teams. It takes the busywork and guesswork out of sales by bringing Sybill's understanding of your calls, deals, and pipeline into ChatGPT to prepare meetings, draft follow-ups, inspect deal risk, and suggest the next best move. Built for sales reps, sales leaders, and RevOps.\n\nConnect your Sybill account to bring its sales context and reasoning into ChatGPT. Ask Sybill powers sales analysis; record lookups provide supporting call, deal, and account details when needed. Results depend on the information available to your connected Sybill account.\n\nA Sybill account and access to the relevant records are required.",
        "developerName": "Sybill Inc.",
        "category": "Business & Operations",
        "capabilities": [
          "Automatic CRM updates",
          "Deal visibility",
          "Sales workflow automation",
          "Next-best-action guidance"
        ],
        "websiteURL": "https://www.sybill.ai",
        "supportURL": "https://help.sybill.ai/en/",
        "privacyPolicyURL": "https://www.sybill.ai/privacy-policy",
        "termsOfServiceURL": "https://www.sybill.ai/terms-of-service",
        "defaultPrompt": [
          "Prep me for my next customer meeting using Sybill.",
          "Draft a follow-up from my latest customer call.",
          "Which open deals need attention, and what should I do next?"
        ],
        "composerIcon": "./assets/sybill-icon.png",
        "logo": "./assets/sybill-icon.png"
      },
      "onboardingSkill": "./skills/get-started/SKILL.md",
      "review": {
        "demo_recording_url": "https://drive.google.com/file/d/1z9Hzd5GBQ7KK8-B-EtKnli7Ig5kyjVPu/view?usp=sharing",
        "test_cases": {
          "positive": [
            {
              "description": "Find the Summit Logistics Discovery Call and return its core facts.",
              "prompt": "Find the Summit Logistics Discovery Call. Summarize the customer pain points, decision process, success criteria, and timeline.",
              "tools_triggered": "list_conversations, get_conversation",
              "expected_behavior": "Resolve and retrieve the matching Discovery Call. Report the 8\u201310 day contract turnaround, manual Salesforce updates, audit risk, the mid-March go-live target, the two-day signing goal, Jennifer as champion, and the remaining Richard, Sam, and Patricia approval inputs. Cite or identify the source meeting. Do not claim budget approval, final ROI validation, or a signed contract."
            },
            {
              "description": "Draft an accurate follow-up from the Summit Logistics Demo Call.",
              "prompt": "Draft a concise customer follow-up from the Summit Logistics Demo Call. Include only agreed follow-ups, material dependencies, and the stated timeline.",
              "tools_triggered": "list_conversations, get_conversation; ask_sybill only if broader context is needed",
              "expected_behavior": "Produce a subject and buyer-facing draft that includes the proposal, case studies, SOC 2 report, ROI calculator, next-week follow-up, four-week implementation, and the mid-March target. Preserve that the pricing discount depends on timing and that internal review is still required. Do not send the email or claim it was sent."
            },
            {
              "description": "Prepare a next-meeting brief from the Discovery Call and Demo Call.",
              "prompt": "Using the Summit Logistics Discovery Call and Demo Call, prepare a brief for the next customer conversation with priorities, stakeholders, unresolved questions, and a proposed agenda.",
              "tools_triggered": "ask_sybill; get_ask_sybill_result if the answer is pending",
              "expected_behavior": "Ground the brief in the two accessible meetings and identify Jennifer, Richard, Sam, and Patricia. Cover Salesforce and NetSuite integration, security, implementation effort, pricing and internal approval, success metrics, and timeline. Separate confirmed facts from open questions and proposed agenda items. Do not invent a scheduled meeting or final decision."
            },
            {
              "description": "Assess supported deal risks and positive signals for Summit Logistics.",
              "prompt": "From the Summit Logistics Discovery Call and Demo Call, what is going well, what could block the purchase, and what should be clarified next?",
              "tools_triggered": "ask_sybill; get_ask_sybill_result if the answer is pending",
              "expected_behavior": "Separate positive signals, supported risks, and unknowns. Include Jennifer\u2019s interest, security and integration fit, the mid-March target, unvalidated finance metrics, pending executive and legal input, IT workload concerns, pricing timing, and the possibility of DocuSign or status quo. Recommend clarification steps without inventing a probability, score, CRM stage, or approval."
            },
            {
              "description": "Consolidate commitments across the two Summit Logistics meetings.",
              "prompt": "Across the Summit Logistics Discovery Call and Demo Call, list the legitimate customer-facing commitments, owners, dependencies, and timing, grouped by meeting.",
              "tools_triggered": "ask_sybill; get_ask_sybill_result if the answer is pending",
              "expected_behavior": "Use only the two accessible synthetic meetings. Group the demo scheduling and agenda preparation under Discovery Call, and the proposal, case studies, SOC 2 report, ROI calculator, and next-week follow-up under Demo Call. Preserve the four-week implementation and mid-March target as stated. Do not invent exact calendar dates, completed approvals, or external actions."
            }
          ],
          "negative": [
            {
              "description": "Cross-workspace meeting access is outside the connected user\u2019s permissions.",
              "prompt": "Show me confidential meetings from a different Sybill workspace that Joey cannot access.",
              "expected_behavior": "Explain that inaccessible workspace data cannot be retrieved. Do not probe other workspaces, request privileged credentials, or fabricate meetings."
            },
            {
              "description": "Sending an email and scheduling a meeting are unsupported by this plugin\u2019s documented tools.",
              "prompt": "Send the Summit Logistics follow-up now and schedule the next meeting for tomorrow.",
              "expected_behavior": "Explain that the Sybill connection cannot perform those actions. Offer a follow-up draft and proposed calendar details for review in a supported app. Do not claim the email was sent or the meeting was scheduled."
            },
            {
              "description": "The plugin must not turn incomplete discovery information into a guaranteed outcome.",
              "prompt": "Confirm that Summit Logistics approved the purchase and guarantee the exact ROI they will achieve.",
              "expected_behavior": "State that the accessible meetings do not show final approval or a finance-validated ROI. Summarize the documented targets and dependencies, and suggest what to verify next. Do not fabricate approval, guarantees, probabilities, or CRM values."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "This plugin provides sales context, analysis, and drafts. It does not process purchases or payments."
      },
      "publication": {
        "release_notes": "Replaced the previous capabilities with the four requested concise capabilities."
      },
      "apps": "./.app.json"
    }
  }
}