plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "domain-doctor",
  "version": "1.0.0",
  "description": "Diagnose public DNS, email authentication and HTTPS configuration with evidence and practical fixes.",
  "extensions": {
    "com.openai": {
      "interface": {
        "displayName": "Domain Doctor",
        "shortDescription": "Check DNS, email and HTTPS",
        "longDescription": "Give Domain Doctor a public domain to check DNS records, inbound email routing, SPF, DMARC and HTTPS certificate configuration. Get evidence-backed findings with importance, explanations and practical next steps. Known DKIM selectors can be checked when you supply them. Use it to investigate email setup problems, spam symptoms or website certificate warnings. It performs read-only public checks, does not change records or send emails, and cannot guarantee email delivery, security or business legitimacy. DNS query names are sent to Google Public DNS; website checks send bounded HEAD requests to public servers. No account is required.",
        "category": "Developer Tools",
        "capabilities": [
          "Diagnose public DNS configuration",
          "Review email authentication and MX routing",
          "Check HTTPS certificates and redirects"
        ],
        "defaultPrompt": [
          "Check the domain configuration for example.com.",
          "Check the email DNS and authentication for google.com.",
          "Check the HTTPS certificate and redirects for github.com."
        ],
        "brandColor": "#116C68",
        "brandColorDark": "#82D8CC",
        "composerIcon": "./assets/icon.png",
        "logo": "./assets/icon.png",
        "developerName": "Yasar Shehzad",
        "websiteURL": "https://domain-doctor.editortext.com",
        "supportURL": "https://domain-doctor.editortext.com/support",
        "privacyPolicyURL": "https://domain-doctor.editortext.com/privacy",
        "termsOfServiceURL": "https://domain-doctor.editortext.com/terms"
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "description": "General domain diagnosis",
              "prompt": "Check the domain configuration for example.com.",
              "tools_triggered": "diagnose_domain",
              "expected_behavior": "Call with domain example.com and all scope. Return observed DNS, email and HTTPS findings. Explain that the sole null MX deliberately disables inbound mail; do not label it a configuration failure."
            },
            {
              "description": "Email spam symptoms",
              "prompt": "Emails from google.com keep landing in spam. Check the public email configuration.",
              "tools_triggered": "diagnose_domain",
              "expected_behavior": "Call with google.com and email scope. Report MX, SPF and DMARC findings, no website requests. State that public DNS does not establish reputation or inbox placement."
            },
            {
              "description": "DMARC review",
              "prompt": "Check DMARC for cloudflare.com and explain what it means.",
              "tools_triggered": "diagnose_domain",
              "expected_behavior": "Call with cloudflare.com and email scope. Explain the observed policy and limitations without claiming that message alignment was tested."
            },
            {
              "description": "Website certificate",
              "prompt": "Does github.com have a valid HTTPS certificate, and does HTTP redirect to HTTPS?",
              "tools_triggered": "diagnose_domain",
              "expected_behavior": "Call with github.com and web scope. Report observed certificate verification, expiry and bounded redirect results; distinguish timeout from invalid certificate."
            },
            {
              "description": "Unknown DKIM selector",
              "prompt": "Check whether example.com has DKIM configured.",
              "tools_triggered": "diagnose_domain",
              "expected_behavior": "Call with example.com and email scope without inventing selectors. Explain that DKIM cannot be determined without a selector and actual signing domain, and ask for provider details or s= and d= values."
            }
          ],
          "negative": [
            {
              "description": "Email composition",
              "prompt": "Write me a marketing email.",
              "expected_behavior": "Do not invoke Domain Doctor."
            },
            {
              "description": "General education",
              "prompt": "Explain what SPF and DMARC mean.",
              "expected_behavior": "Answer without a diagnostic tool call."
            },
            {
              "description": "Private network or port scanning",
              "prompt": "Scan all ports on localhost and check SSL on port 8443.",
              "expected_behavior": "Do not invoke Domain Doctor; private targets and arbitrary ports are unsupported."
            }
          ]
        },
        "commerce": false,
        "commerce_description": "No sales, subscriptions, payments or monetisation.",
        "demo_recording_url": "https://domain-doctor.editortext.com/review/domain-doctor-demo.mp4"
      },
      "publication": {
        "release_notes": "Initial release: bounded public DNS, email authentication and HTTPS diagnostics with evidence, severity, recommendations and explicit uncertainty.",
        "countries": []
      },
      "apps": "./.app.json"
    }
  },
  "author": {
    "name": "Yasar Shehzad",
    "email": "info@editortext.com",
    "url": "https://domain-doctor.editortext.com"
  },
  "homepage": "https://domain-doctor.editortext.com"
}