Update to Proxy Mail QA

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

plugin.json →

skills/proxymail-qa/SKILL.md →

plugin.json

− removed · + added

--- before
+++ after
@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "proxymail-qa",
-  "version": "1.8.0",
+  "version": "1.9.0",
   "description": "Disposable test inboxes for testing sign-up, login-code, magic-link and password-reset emails. Create an address, sign up with it, and get the code or link back without the rest of the email.",
   "author": {
     "name": "Proxy Mail QA",
@@ -25,7 +25,7 @@
       "interface": {
         "displayName": "Proxy Mail QA",
         "shortDescription": "Test inboxes for app sign-ups",
-        "longDescription": "Proxy Mail QA gives ChatGPT and Codex disposable email addresses for testing the emails your app sends. Ask things like:\n\n- \"Give me a test email for my staging sign-up and tell me the code when it arrives.\"\n- \"Why isn't my app's verification email arriving?\"\n- \"Check the password-reset email my app sent to my test address.\"\n- \"Sign up on localhost:3000 with a new test account and confirm the email.\" (Codex, or an agent with a browser)\n\nIt creates an address with a fictional name, username and, if the form needs one, a strong password. You sign up with it, or the agent does when it can use a browser, and you get the verification code or link as soon as it arrives. It works the same for login codes, magic sign-in links, password resets and invites, and it can check the email itself: SPF, DKIM and DMARC, links that point at localhost, the stated expiry and how it fits on a phone. When nothing arrives, it shows what reached the address, anything refused, and the likely cause. It can also fill a whole sign-up form's values (a username with rules, a date of birth, a country), suggest awkward names and passwords to test a form's validation, and look up how something works in Proxy Mail QA's docs.\n\nResults contain only the code or link, the service that sent it and when it expires, never the email's text, so an email can't pass instructions to your agent. Proxy Mail QA never opens links, so single-use links still work. Addresses last up to 30 days and only you can read their mail. Addresses are receive-only: nothing is ever sent from them.\n\nWhen you connect, you sign in to Proxy Mail QA (or create an account and your first project on the way) and choose one project; the agent works only in that project and can't read passwords saved earlier. Disconnect it any time in Project settings \u2192 API keys.",
+        "longDescription": "Proxy Mail QA gives ChatGPT and Codex disposable email addresses for testing the emails your app sends. Ask things like:\n\n- \"Give me a test email for my staging sign-up and tell me the code when it arrives.\"\n- \"Why isn't my app's verification email arriving?\"\n- \"Check the password-reset email my app sent to my test address.\"\n- \"Sign up on localhost:3000 with a new test account and confirm the email.\" (Codex, or an agent with a browser)\n\nIt creates an address with a fictional name, username and, if the form needs one, a strong password. You sign up with it, or the agent does when it can use a browser, and you get the verification code or link as soon as it arrives. It works the same for login codes, magic sign-in links, password resets and invites, and it can check the email itself: SPF, DKIM and DMARC, links that point at localhost, the stated expiry and how it fits on a phone. When nothing arrives, it shows what reached the address, anything refused, and the likely cause. It can also fill a whole sign-up form's values (a username with rules, a date of birth, a country, and the form's own questions, such as company size, from your project's custom fields), keep a site's sign-up screens and add a staging or local site to your project when you agree, suggest awkward names and passwords to test a form's validation, and look up how something works in Proxy Mail QA's docs.\n\nEmail results carry only the code or link, the service that sent it and when it expires, never the email's text, so an email can't pass instructions to your agent. Proxy Mail QA never opens links, so single-use links still work. Addresses last up to 30 days and only you can read their mail. Addresses are receive-only: nothing is ever sent from them.\n\nWhen you connect, you sign in to Proxy Mail QA (or create an account and your first project on the way) and choose one project; the agent works only in that project and can't read passwords saved earlier. Disconnect it any time in Project settings \u2192 API keys.",
         "developerName": "Proxy Mail QA",
         "category": "Developer Tools",
         "capabilities": [
@@ -55,7 +55,7 @@
               "description": "List test addresses with their latest codes and links",
               "prompt": "List my Proxy Mail QA test addresses and their latest codes or links.",
               "tools_triggered": "list_addresses",
-              "expected_behavior": "Lists the addresses in the Reviewer demo project, newest first. Four were made for a fictional app, Acme Notes, and show a sign-up code, a magic sign-in link, a password-reset link and a team invite. Each shows only the code or link, the sending service and when it arrived, never the email's text."
+              "expected_behavior": "Lists the addresses in the Reviewer demo project, newest first. Four were made for a fictional app, Acme Notes, and show a sign-up code, a magic sign-in link, a password-reset link and a team invite. Each shows its label, fictional persona and tags, and its latest code or link with the sending service and when it arrived, never the email's text."
             },
             {
               "description": "Find test accounts made earlier by tag",
@@ -142,6 +142,36 @@
               "expected_behavior": "Lists first names a form should accept (apostrophes, accents, other scripts, very long names), ones it should store as text rather than run (HTML or SQL), and passwords that fit 8 to 100 characters with the edge cases to check, such as spaces, every symbol class and the 72-byte limit, each saying what it tests."
             },
             {
+              "description": "List the project's custom fields for sign-up forms",
+              "prompt": "Which custom fields does my Proxy Mail QA project have for sign-up forms?",
+              "tools_triggered": "list_custom_fields",
+              "expected_behavior": "Lists the Reviewer demo project's three custom fields: Company size, which gives each test account one of 1-10, 11-50 and 51-200; How did you hear about us, which fills in Search; and Team size, which chooses 2-10 in a drop-down. Each shows how it recognises the field (words its label contains) and that it applies on every site. It also says the project guesses fields nobody taught, and that anyone on the project can change custom fields."
+            },
+            {
+              "description": "Save a custom field, then remove it",
+              "prompt": "Save a Proxy Mail QA custom field that fills any Job title field in my sign-up forms with 'QA Engineer', then remove it again.",
+              "tools_triggered": "save_custom_field, delete_custom_field",
+              "expected_behavior": "Saves a custom field named Job title that recognises fields whose label contains 'job title' and fills them with QA Engineer on every site (status: saved), then removes it (status: removed). Only the Reviewer demo project's settings change: no form is filled in or submitted."
+            },
+            {
+              "description": "Turn a custom field and a standard field off, then on again",
+              "prompt": "Turn off my Proxy Mail QA project's Team size custom field and the standard Company field, then turn both back on.",
+              "tools_triggered": "list_custom_fields, set_custom_field_enabled, set_standard_field",
+              "expected_behavior": "Finds Team size's id with list_custom_fields, turns it off and on again (set_custom_field_enabled), and turns the standard company field off and on again (set_standard_field, status: saved each time). Only the Reviewer demo project's settings change: no form is filled in or submitted."
+            },
+            {
+              "description": "Keep a sign-up screen for a site, then undo it",
+              "prompt": "Add the page /signup/team on staging.acmenotes.example as a sign-up screen called Team details, and turn on 'Sign-up goes over several screens' for that site. Then turn the setting off again and remove the screen.",
+              "tools_triggered": "save_signup_screen, set_multi_step, remove_signup_screen",
+              "expected_behavior": "Saves Team details (/signup/team) as one of staging.acmenotes.example's sign-up screens and turns the setting on, then turns it off and removes the screen. Only the Reviewer demo project's list of sign-up screens and that site's setting change: no form is filled in or submitted."
+            },
+            {
+              "description": "Add a test site to the project",
+              "prompt": "Add qa.acmenotes.example to my Proxy Mail QA project as a QA site.",
+              "tools_triggered": "add_site",
+              "expected_behavior": "Adds qa.acmenotes.example with the environment qa (status: saved), or, if an earlier review added it, says it's listed already and leaves it as it is (status: listed). Only the Reviewer demo project's list of sites changes; it gives no browser access, and a host that looks live would be refused with a link to add it in the app."
+            },
+            {
               "description": "Look up how something works in the docs",
               "prompt": "How do I wait for a sign-up code in a Playwright test with Proxy Mail QA?",
               "tools_triggered": "search_docs",
@@ -176,7 +206,7 @@
         "demo_recording_url": "https://zdqzvjogemvfzssmxazt.supabase.co/storage/v1/object/public/Video/Screen%20Recording%202026-10-13%20at%2010.58.08.mov"
       },
       "publication": {
-        "release_notes": "Since 1.0.1: checks on the emails a test address receives (check_email: SPF, DKIM, DMARC, links to localhost or plain http, where links go, a stated expiry, size and how it fits a phone; count_emails to catch duplicates; expect_no_email to check an action sends nothing), all verdicts, never the email. Runs (start_run, add_run_note, finish_run) record what each tool saw and end in a Markdown report. An account pool (check_out_account, extend_checkout, return_account) lends a test account in a known state. form_values fills a whole sign-up form's values, get_name_variants and get_password_variants suggest awkward names and passwords to test a form's validation, and search_docs looks things up in the docs. Accounts can record the site and environment they're used on, mark_dev_host lets links to a local dev server pass the checks, and waits can skip codes already used. Ready-made prompts for testing sign-up, password reset and code sign-in, auditing an app's account emails and preparing a test account. Checks on an app's marketing emails (unsubscribe links, codes in them, consent) work for people who switch them on in Labs."
+        "release_notes": "Since 1.0.1: checks on the emails a test address receives (check_email: SPF, DKIM, DMARC, links to localhost or plain http, where links go, a stated expiry, size and how it fits a phone; count_emails to catch duplicates; expect_no_email to check an action sends nothing), all verdicts, never the email. Runs (start_run, add_run_note, finish_run) record what each tool saw and end in a Markdown report. An account pool (check_out_account, extend_checkout, return_account) lends a test account in a known state. form_values fills a whole sign-up form's values, including its own questions from the project's custom fields (list_custom_fields, save_custom_field, delete_custom_field, set_custom_field_enabled, set_standard_field) and a guess, marked as one, for fields nobody taught, one screen at a time for sign-ups over several, with save_signup_screen, remove_signup_screen and set_multi_step to keep a site's sign-up screens and let Proxy Mail QA for Chrome 0.9.0 and later fill each one by itself, and add_site to add a staging, dev or local site to the project; get_name_variants and get_password_variants suggest awkward names and passwords to test a form's validation, and search_docs looks things up in the docs. Accounts can record the site and environment they're used on, mark_dev_host lets links to a local dev server pass the checks, and waits can skip codes already used. Ready-made prompts for testing sign-up, password reset and code sign-in, auditing an app's account emails and preparing a test account. Checks on an app's marketing emails (unsubscribe links, codes in them, consent) work for people who switch them on in Labs."
       },
       "apps": "./.app.json"
     }