How do I install the Pi Provider Kimi Code Foundation skill?

Run npx skillmds@latest add ryan-brosas/pi-provider-kimi-code-foundation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pi Provider Kimi Code Foundation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pi Provider Kimi Code Foundation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pi Provider Kimi Code Foundation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pi Provider Kimi Code Foundation?

ryan-brosas (@ryan-brosas) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pi Provider Kimi Code Foundation by ryan-brosas

Name: Pi Provider Kimi Code Foundation
Author: ryan-brosas

Pi Provider Kimi Code Foundation

Use when porting Kimi Code (Moonshot K2/K3) provider machinery — vendor-constrained payload mutation pipelines, inline-threshold file uploads with stale-token refresh ladders, content-hash upload memo caches, JSON Schema type back-fill for strict validators, per-tool $defs schema dedup under byte caps, empty-response stream suppression, speculative OAuth retry around synthetic start events, layered defaults/home/project/env/runtime config merge with source attribution, JSON-pointer config validation projection, window-tracking output caps, and a resolved-config stream store with live overlay.

ryan-brosas acce3b2 17 files · 69.6 KB Updated Sep 17, 2026

File contents

pi-provider-kimi-code: request-construction foundation

Foundation contract

This is a cold, source-specific foundation, not an operational procedure. It is historical, revision-pinned evidence rather than timeless guidance. Current project source, tests, requirements, and runtime behavior outrank this projection and decide what ships.

Provenance and revision

Source record: pi-provider-kimi-code; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.
Recorded revision: main@794330400343d6f0cd0059635187b233c4d90273.
Full provenance, coverage caveats, boundaries, and preserved evidence: references/index.md.

Topic map

Representative topics: Payload mutation pipeline; File-upload IO edge; Upload memo cache; Schema type back-fill; Tool schema dedup; Empty-response filter; Stream auth retry; Layered config merge ladder.
Scope and retrieval questions: references/index.md#use-this-for.
Complete capsule chooser: references/index.md#load-the-matching-source-dump.
Detailed grouped map: references/index.md#capsule-map.
Source limitations and portability boundaries: references/index.md#boundaries.

Retrieval

Open the index, choose one capsule matching the active question, and load only that capsule. Revalidate its cited source and revision before relying on it. Do not bulk-load the inventory, treat historical claims as current truth, or apply this foundation as a procedure.

---name: pi-provider-kimi-code-foundationdescription: Use when porting Kimi Code (Moonshot K2/K3) provider machinery — vendor-constrained payload mutation pipelines, inline-threshold file uploads with stale-token refresh ladders, content-hash upload memo caches, JSON Schema type back-fill for strict validators, per-tool $defs schema dedup under byte caps, empty-response stream suppression, speculative OAuth retry around synthetic start events, layered defaults/home/project/env/runtime config merge with source attribution, JSON-pointer config validation projection, window-tracking output caps, and a resolved-config stream store with live overlay.---# pi-provider-kimi-code: request-construction foundation## Foundation contractThis is a cold, source-specific foundation, not an operational procedure. It ishistorical, revision-pinned evidence rather than timeless guidance. Currentproject source, tests, requirements, and runtime behavior outrank thisprojection and decide what ships.## Provenance and revision- Source record: `pi-provider-kimi-code`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.- Recorded revision: `main@794330400343d6f0cd0059635187b233c4d90273`.- Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`.## Topic map- Representative topics: Payload mutation pipeline; File-upload IO edge; Upload memo cache; Schema type back-fill; Tool schema dedup; Empty-response filter; Stream auth retry; Layered config merge ladder.- Scope and retrieval questions: `references/index.md#use-this-for`.- Complete capsule chooser: `references/index.md#load-the-matching-source-dump`.- Detailed grouped map: `references/index.md#capsule-map`.- Source limitations and portability boundaries: `references/index.md#boundaries`.## RetrievalOpen the index, choose one capsule matching the active question, and load onlythat capsule. Revalidate its cited source and revision before relying on it. Donot bulk-load the inventory, treat historical claims as current truth, or applythis foundation as a procedure.

Frequently asked questions