06-reference/research

ray plugins marketplace verified eligibility

2026-10-07·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
plugin-directoryray-pluginsbrigade-houseanthropic-policycredibility-for-phdata

The gate is published now, ray-plugins fails two mechanical checks on every plugin, and "Anthropic Verified" is a connector label RDCO cannot earn with a skills-only bundle

The question

"Is ray-plugins (or any brigade-house public plugin) eligible for and worth submitting to the community marketplace plus 'Anthropic Verified' review, what does the security-review gate actually require, and does the leak-gate/manifest-allowlist output already satisfy it?" Promoted follow-up #1 of [[2026-07-21-anthropic-plugin-marketplace-brigade-strategy]], which recommended pursuing the badge without having read any acceptance criteria.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Eligibility: yes, and the generated-public-surface worry is a non-issue. The Software Directory Policy has no source-availability, open-source, reproducibility, or provenance requirement at all, and the review reads the shipped payload, not its build history. Nothing asks where ray-plugins came from, whether distribute.py produced it, or whether a private monorepo sits behind it. The only structural requirements the topology touches are satisfiable and already mostly satisfied: the repo must be public before the listing goes live (it is), the submission is one plugin folder at a time (which maps cleanly onto public.manifest.json's explicit allowlist), and after the first submission the directory follows the tracked branch. The real consequence of the generated topology is not eligibility, it is that a distribute pass stops being an internal hygiene step and becomes a public release, scanned on every commit and served to whoever installed. That is the part of the hold that marketplace submission actually changes.

The gate, concretely, and what the leak gate does not cover. I ran the mechanical layer today. claude plugin validate passes on the marketplace manifest and all ten plugin folders, including --strict on spot checks. ray-plugins ships zero hooks and zero MCP servers, no package launchers in any loaded surface, no lockfiles or .npmrc, no symlinks, submodules, LFS pointers or .gitattributes, no junk files, every file under 256 KiB (largest 69.7 KB), every plugin under 64 files against a 512 cap, and all 52 SKILL.md files carry front matter. That is the entire expensive half of the checklist cleared, and it is cleared because the brigades are skills-and-markdown, which is the shape the scanner likes. Against that, two Blocks classes fail on nearly every plugin: no LICENSE file and no license field in any of the ten plugin.json manifests (10/10 fail), and no README in the plugin folder for eight of ten (only ab-skill-factory at 1,897 words and ab-registrar at 380 clear it; the repo-root README does not count, and the directory renders the plugin-folder README as the listing description, so eight plugins would have no listing copy). Two names draw an almost certain reviewer hold: snowflake-cli and copilot-studio-agent-builder are built on brands that are not RDCO's, which the checklist calls out explicitly ("Name matches a known brand"). [INFER, medium] rdco-example and the opaque ab- prefix on generic discipline words invite the generic-name and look-alike holds. The leak gate and manifest allowlist satisfy one row of all of this (credentials absent from every file) plus the governance discipline of deciding deliberately what ships. They do not and cannot speak to license, README, naming, file-type limits, launcher pinning, hook scope, telemetry disclosure, or description-matches-behavior. Treating a clean leak-gate run as readiness would be the specific mistake this brief exists to prevent.

Worth it: yes, once, for the instrument rather than the reach or the badge. Under the credibility-for-phData-sales frame, where the domain is agents in production and the measure is pipeline rather than subscribers, the directory's most valuable output is not distribution. It is the Usage tab: installs, versions, per-skill run counts, and error rates on a plugin Anthropic reviewed and listed. That is the only artifact in reach that converts "I build agents" into third-party-attested operating numbers a phData buyer recognizes, and it is structurally impossible to produce from a self-hosted marketplace, which is why four months of ray-plugins yielded an uninformative zero rather than a negative result. A listing is also the cheapest available answer to the credibility-surface problem the builder-track brief named: a public repo that still describes itself as a "/hello example" while carrying seven production brigades currently argues against RDCO's competence to anyone who follows a link. The costs are real and should be stated flatly. Review latency is [UNKNOWN] by Anthropic's own wording. The maintenance obligation is contractual, not implied (Policy 3.G, plus verified contact info and a privacy-policy link). Exposure is continuous: every commit to the tracked branch is scanned, a failed version cannot go live, and the directory runs daily owner-liveness and SHA-bump sweeps, so a dormant RDCO is a visibly dormant listing. And the per-plugin multiplication is the quiet cost: ten plugins means ten submissions, ten READMEs, ten license decisions, ten reviews, ten things to maintain.

So: submit exactly one, and not for the badge. The badge recommendation in the parent brief should be retired outright rather than deferred, because Verified is a connector escalation and RDCO ships no connector. If the founder wants Verified, that is a decision to publish an MCP server, which is a different project with a different cost. The single-submission candidate that minimizes work and maximizes signal is ab-skill-factory: it is the only plugin that already clears the README gate, its name is the least brand-collision-prone and the least generic, and "the brigade that manufactures brigades" is the most legible story to a buyer evaluating agents-in-production. snowflake-cli should be excluded on two independent grounds, the brand-name hold and its adjacency to the phData disclosure boundary. The prerequisites are four, all reversible and all cheap except the first, which is the founder's: (1) greenlight a distribute pass, because submitting today would publish v1 artifacts that the center retired three months ago, and because post-submission every distribute pass is a release; (2) add a license (file or manifest field) and a plugin-folder README for whatever is submitted; (3) fix the repo and marketplace descriptions that still call the surface a minimal /hello template; (4) decide which claude.ai organization submits, because the listing belongs to that org and the first org to submit a repository folder holds it permanently. One further piece of free upside worth taking in the same pass: the brigades already carry two-arm eval evidence as prose reports in evals/*.md, and claude plugin eval now runs a native case.yaml + graders/ suite with a no-plugin baseline arm. Porting one station's evidence into the native format makes RDCO's eval claim independently re-runnable by anyone who installs it, which is the closest thing to a credibility artifact in this entire surface.

Why this is in the vault

This closes follow-up #1 of [[2026-07-21-anthropic-plugin-marketplace-brigade-strategy]] and follow-up #2 of [[2026-08-24-claude-marketplace-free-skill-paid-cta-policy]] with primary sources, and it converts step 3 of [[2026-08-30-anthropic-builder-track-solo-founder-lane]] ("submit one plugin and instrument installs") from a recommendation into a priced, prerequisite-complete action with a named candidate plugin. It also retires the standing "pursue Anthropic Verified" item, which was based on press coverage and does not apply to a skills-only bundle, and it supplies the specific blocker list the next ray-plugins distribution review needs so that review does not re-derive it.

Open follow-ups

Related

Sources

Vault:

Local artifacts, inspected 2026-10-07:

Web (primary):

Web (secondary, used only to attribute the badge claim):