Skip to content

feat(plugin): Qwen Code, Gemini CLI and Kimi Code manifests + Chinese README section - #8

Merged
teakesdev merged 2 commits into
mainfrom
session/china-marketplaces
Oct 16, 2026
Merged

teakesdev merged 2 commits into
mainfrom
session/china-marketplaces

Conversation

@teakesdev

Copy link
Copy Markdown
Owner

What

Makes the kit installable from the repo URL in three more agent harnesses, as part of listing Corpus on Chinese agent marketplaces:

  • qwen-extension.json, gemini-extension.json and kimi.plugin.json at the repo root. Each loads both canonical skills (skills/), the hosted MCP server and a shared CORPUS.md context.
    • Gemini and Qwen spell Streamable HTTP as httpUrl; in those two, url means SSE, which Corpus doesn't serve.
    • Kimi spells it url.
  • CORPUS.md: when to use the tools, plus honest limits for founders outside the US, matching the corpuslaw.us China guide:
    • US entities only, and a US street address is needed for the principal office;
    • no EIN, bank accounts or tax filings;
    • English checkout, card payment, sign-in by emailed code.
  • A 中文 README section with the Qwen Cloud hackathon win and a link to the Chinese guide.
  • scripts/check-plugin-package.mjs now requires every root manifest to:
    • point at the same headerless MCP URL, with the right key for its harness;
    • carry the plugin version;
    • name a context file that exists;
    • include the award line.
  • Also fixed:
    • the README badge now links the Devpost project page (the proof);
    • the stale "571,582 provisions" now reads "700,000+" (live initialize says 700,682+).

There is no Qoder plugin manifest. Qoder's marketplace requires a plugin's MCP to be a listed Connector, which needs OAuth plus company verification. The two skills were submitted to Qoder as Skills instead.

Verification

  • Kit gate, run locally:
    • plugin-skill drift: OK;
    • autopilot 39/39;
    • mcp-server 6/6;
    • typecheck, build and check-plugin-package.mjs: all pass;
    • python packaging tests 3/3.
    • The check failed before the manifests existed (ENOENT on gemini-extension.json), as expected.
  • Qwen Code 0.25.0 (qwen extensions install <local checkout>:corpus) installed corpus (0.1.0) with both skills and CORPUS.md. qwen mcp list showed corpus: https://corpuslaw.us/api/mcp (http) - Connected.
  • Gemini CLI 0.62.0: gemini extensions validate <checkout> validated it.
  • Kimi Code was not tested, because the CLI isn't installed here.

After merge

Add the gemini-cli-extension repo topic. The Gemini CLI gallery indexes public repos that have this topic and a root gemini-extension.json, and Qwen Code's /extensions explore opens that gallery.

Not independently reviewed.

🤖 Generated with Claude Code

… README section

Adds repo-root qwen-extension.json, gemini-extension.json and kimi.plugin.json
so `qwen extensions install <repo>:corpus`, `gemini extensions install <repo>`
and Kimi Code `/plugins install <repo>` load both canonical skills, the hosted
MCP URL and a shared CORPUS.md context (incl. the honest limits for founders
outside the US, matching the corpuslaw.us China guide). Descriptions are
bilingual and name the Qwen Cloud hackathon Track 4 win.

check-plugin-package.mjs now pins every root manifest to the same headerless
Streamable HTTP URL (httpUrl for Gemini/Qwen, whose `url` means SSE; url for
Kimi), the plugin version, an existing context file and the award line.

Verified: Qwen Code 0.25.0 local install -> both skills + CORPUS.md loaded,
`qwen mcp list` -> corpus Connected; `gemini extensions validate` (0.62.0) OK.
Kimi Code not tested (CLI not installed).

Also: README badge links the Devpost project (proof), and the stale
"571,582 provisions" -> "700,000+" (live initialize says 700,682+).

No Qoder plugin manifest: Qoder's marketplace plugins must reference listed
Connectors (OAuth + company verification); the skills go to Qoder as Skills.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

… P2)

The Coverage paragraph still said "18 jurisdictions, 16 fully searchable"
with per-state counts summing to ~557K, contradicting the "700,000+"
headline this PR introduced. Live initialize (2026-10-16): 700,682+
provisions, 20 jurisdictions (18 fully searchable). Per-jurisdiction counts
are dropped in favour of law.list_coverage, so the README can't go stale
the same way again. Founder approved this fix only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@teakesdev
teakesdev merged commit 0202c7d into main Oct 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant