plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "hobbes",
  "version": "0.2.1",
  "description": "Inspect and update Hobbes product agents, review demo conversations and prospect engagement, and create personalized demo links.",
  "author": {
    "name": "Hobbes",
    "url": "https://www.hihobbes.com/"
  },
  "homepage": "https://docs.hihobbes.com/guides/chatgpt-plugin-support",
  "keywords": [
    "hobbes",
    "demos",
    "sales",
    "prospects",
    "accounts",
    "gtm",
    "product-agents",
    "playbooks",
    "coaching"
  ],
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Hobbes",
        "shortDescription": "Manage your product agents",
        "longDescription": "Hobbes helps B2B sales and go-to-market teams review and improve their AI product-demo agents in ChatGPT. Inspect agent playbooks and versions, review demo conversations and prospect engagement, and improve how your agents explain and demonstrate your product. Preview playbook updates, review coaching proposals, and apply approved changes to an agent draft. Publish a specific approved version through Hobbes' confirmation and conversation-test flow.\n\nYou can also review demo funnel metrics, investigate objections with saved transcripts, explore engagement by person or account, and create personalized demo links.\n\nConnect your existing Hobbes account and choose the organization to share with ChatGPT. Available actions depend on your granted permissions. Agent changes, coaching, publishing, and personalized link creation require an organization admin. Draft changes, shared knowledge approvals, and production publication remain separate steps. Hobbes does not send outreach, change CRM records, or process payments through this plugin.",
        "developerName": "Hobbes",
        "defaultPrompt": [
          "How did our demos perform over the last 7 days?",
          "Which prospects should our sales team follow up with?",
          "Help me create a personalized demo link."
        ],
        "websiteURL": "https://docs.hihobbes.com/guides/chatgpt-plugin-support",
        "supportURL": "https://docs.hihobbes.com/guides/chatgpt-plugin-support",
        "privacyPolicyURL": "https://www.hihobbes.com/privacy-policy",
        "termsOfServiceURL": "https://www.hihobbes.com/terms-of-use",
        "logo": "./assets/logo.png",
        "composerIcon": "./assets/composer-icon.png",
        "logoDark": "./assets/logo-dark.png",
        "composerIconDark": "./assets/composer-icon-dark.png",
        "brandColor": "#000000",
        "brandColorDark": "#FFFFFF",
        "category": "Productivity"
      },
      "review": {
        "demo_recording_url": "https://docs.hihobbes.com/guides/chatgpt-plugin-walkthrough",
        "test_cases": {
          "positive": [
            {
              "description": "Use the dedicated production Clay reviewer organization and its synthetic October 5 cohort: Alex and Jordan at OpenAI, Casey at Stripe, Morgan at Figma. Include aggregate metrics, qualified/high-intent filtering, saved transcript evidence, and account rollups. These fixtures do not represent real buying interest. Also check a valid empty window.",
              "prompt": "Review Clay's demos over the last 7 days. Find qualified high-intent sessions, explain Alex Demo's latest objections from the saved transcript (alex.demo.hobbes-review-20261005@openai.com), and summarize the synthetic OpenAI account at openai.com. Cite returned source IDs.",
              "tools_triggered": "get_funnel_metrics(days=7); list_sessions with supported qualification/intent/date/search filters; get_session and get_session_transcript for the same returned Alex session; get_account(domain=\"openai.com\"); get_person only for needed returned people",
              "expected_behavior": "Keep session counts and unique-person counts distinct, state the trailing UTC window and denominators, and preserve empty-window null rates. Cite saved session/person/account IDs and compare actual transcript evidence with analysis. Disclose the account narrative/structured-qualification discrepancy. State pagination coverage and synthetic context; do not invent scores, outreach, or agent changes."
            },
            {
              "description": "Use the connected Clay organization. Resolve its default product agent through list_roles and carry its exact Role ID into inspection and coaching reads. Do not assume an agent name or fabricate product settings.",
              "prompt": "Show our default Clay product agent's playbook, staging and production versions, and pending coaching changes. Explain what is live and what is still a draft.",
              "tools_triggered": "list_roles; get_playbook(role_id from returned default Role); list_coaching_feedback and list_coaching_changes for that same role_id",
              "expected_behavior": "Identify the returned Role name and ID. Report actual staging/production versions, supported Playbook sections, links, and coaching backlog. Label absent data honestly. This inspection must create no preview, feedback, draft change, shared-fact approval, or publish job."
            },
            {
              "description": "Use the default Clay reviewer product agent, with coaching:read/write and Admin access. The harmless synthetic review feedback concerns the opening workflow question. Review the generated proposals before approving only the intended draft behavior; never invent a pricing or shared product fact. If no applicable change is generated, report that result and use an actual pending supported proposal for additional coverage.",
              "prompt": "Coach our default Clay product agent to ask one concise question about the visitor's workflow before starting a walkthrough. Show me the proposed changes first; apply only the changes I approve. Do not publish.",
              "tools_triggered": "list_roles; get_playbook; file_coaching_feedback(role_id, kind=\"guidance\", source=\"platform\", stable submission_key); derive_coaching_changes(feedback_id); after explicit approval, apply_coaching_changes with selected IDs and returned draft tokens; list_coaching_changes/get_playbook for verification",
              "expected_behavior": "Show the actual feedback, derived changes, evidence, and destinations before applying. Wait for approval. Carry the exact revision and ETags, handle draft drift, and inspect every per-change outcome. Distinguish filed feedback, proposals, saved draft, shared approval, recapture, unsupported, and failed states. Create no publish job or organization-wide shared-fact approval in this case."
            },
            {
              "description": "Use the default Clay reviewer product agent with playbook:read/write, agent:publish, and Admin access. Inspect its returned section catalog, preview one small supported behavior change, and show the exact before/after. The reviewer approves that preview in a follow-up, then separately requests publication of the exact saved staging version. Exercise native confirmation decline before an approved publish; the declined path must create no job. Preserve the original content for restoration after testing.",
              "prompt": "Preview a change to our default Clay product agent's playbook so it asks one workflow question before the walkthrough. Show the exact before and after, and wait for my approval before applying anything.",
              "tools_triggered": "list_roles; get_playbook; preview_playbook_update with exact section patches, current sections_etag and stable operation_key; apply_playbook_update only after preview approval; publish_agent_version only after a separate publish request and native confirmation; get_agent_publish_job and get_playbook for verification",
              "expected_behavior": "Target the exact returned Role and preserve unrelated content. Report the preview without writing staging. Apply only the approved, unexpired preview from this same connection; reload on drift. Do not auto-publish a saved draft. Honor native decline with no job. For an approved publish, run the server test gate, poll the original job idempotently, distinguish pending/failure/success, and verify the production version before claiming publication. Restore the original test behavior through an approved preview rather than silently overwriting later changes."
            },
            {
              "description": "In the dedicated Clay reviewer organization, the reviewer admin grants custom_links:read and custom_links:write. Use the fictional Alex Demo contact at OpenAI, one stable operation_key, and no thumbnail generation. Honor any host confirmation.",
              "prompt": "Create one personalized demo link for Alex Demo at OpenAI, alex.demo.hobbes-review-20261005@openai.com, in a campaign named ChatGPT Review. Skip thumbnail generation.",
              "tools_triggered": "list_custom_link_campaigns to resolve the campaign if needed; create_custom_links with one synthetic prospect, campaign name or exact existing ID, generate_thumbnails=false, and a stable operation_key; get_custom_link_job(job_id from creation, include_items=true)",
              "expected_behavior": "Honor host confirmation and never bypass a decline. Poll the accepted job with bounded retries until a terminal status or report that it remains pending. Return only URLs produced by Hobbes and per-item success or failure. Reuse the original operation_key after a timeout; do not create duplicate jobs or claim the link was emailed."
            }
          ],
          "negative": [
            {
              "description": "Email delivery is outside this plugin. Explain the limitation and offer to draft text. Do not invoke Hobbes tools or claim messages were sent.",
              "prompt": "Email all of our qualified prospects a follow-up right now."
            },
            {
              "description": "Purchases, subscription upgrades, and billing are outside this first release. Explain that limit. Do not invoke Hobbes tools or claim a purchase or upgrade occurred.",
              "prompt": "Buy another Hobbes subscription for our team and charge our saved card."
            },
            {
              "description": "This plugin cannot mutate Salesforce deals. Explain the limitation and offer a review or export only if the user asks for it. Do not invoke Hobbes tools or claim CRM records changed.",
              "prompt": "Mark every qualified prospect as a won deal in Salesforce."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "No payments or purchases occur inside the plugin. It connects to an existing Hobbes account."
      },
      "publication": {
        "release_notes": "Initial public release for Hobbes customers: product-agent inspection, previewed Playbook updates, coaching review and application, confirmed agent publication, demo and prospect analysis, and personalized demo links through the permission-scoped Hobbes MCP.",
        "countries": []
      },
      "apps": "./.app.json"
    }
  }
}