chrome-extension-messaging-tests SKILL.md skillA
chrome-extension-messaging-tests from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/chrome-extension-messaging-tests@v1.2.6Pins v1.2.6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-browser-extension/skills/chrome-extension-messaging-tests/SKILL.md- Versions recorded
- 3
- Latest version
- v1.2.6, committed Oct 11, 2026
- First version recorded
- Jul 20, 2026
- Size
- 16,714 bytes
- Repository stars
- 11
- License
- MIT
Asserts Chrome extension message-passing behaviour against a running extension: one-shot `chrome.runtime.sendMessage` plus the literal `return true` that holds the response channel open for an async `sendResponse`, `chrome.tabs.sendMessage` into one tab's content script, long-lived `chrome.runtime.connect` ports and their `onDisconnect` triggers, web-page messages gated by `externally_connectable`, and `chrome.runtime.connectNative` native-messaging hosts. Covers the payload rules a test must…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# chrome-extension-messaging-tests ## Overview Extension components run in separate contexts (content script, service worker, popup, options page, an external web page, a native host process) and can only reach each other through the messaging APIs described on the [Chrome Extensions message passing page][cr-msg]. That page defines five distinct shapes, each with its own failure mode: [cr-msg]: https://developer.chrome.com/docs/extensions/develop/concepts/messaging 1. One-shot **runtime** messages inside one extension (`chrome.runtime.sendMessage`). 2. One-shot **tabs** messages into a content script (`chrome.tabs.sendMessage`). 3. Long-lived **ports** (`chrome.runtime.connect`). 4. **Cross-extension** and **web-page** messages, gated by `externally_connectable`. 5. **Native messaging** (`chrome.runtime.connectNative`). Most "the feature silently does nothing" bugs in an extension are one of these five failing quietly: a channel closed before the response, a message sent to a tab with no matching content script, a port dropped by a suspended service worker, or an origin missing from an allow-list. Tests here make each of those loud. ## Scope boundary …
Read the whole file at its exact version.
How to install
mdr add testland/qa/chrome-extension-messaging-tests@sha256:fe8fdaabd690d98eThe line at the top of this page pins the label v1.2.6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jgpwfdyl2u5vmqal)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 20, 2026 and Oct 11, 2026, about one every 41 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2.6 latest | 2026-10-11 | a1bd3f7 | 16,714 B | A | view · diff |
| git:20260725.4f623d0 | 2026-07-25 | 4f623d0 | 16,695 B | A | view · diff |
| git:20260720.a861081 | 2026-07-20 | a861081 | 20,426 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16714 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jgpwfdyl2u5vmqal GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/chrome-extension-messaging-tests GET https://markdownregistry.com/api/v1/blob/fe8fdaabd690d98e9c9cc876a67dab7e4416196cf38a11b77dc273a5ecff9bae
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.