How do I install the Pi Hypercharm Provider Foundation skill?

Run npx skillmds@latest add ryan-brosas/pi-hypercharm-provider-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 Hypercharm Provider 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 Hypercharm Provider 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 Hypercharm Provider Foundation free to use?

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

Who published Pi Hypercharm Provider Foundation?

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

Pi Hypercharm Provider Foundation by ryan-brosas

Name: Pi Hypercharm Provider Foundation
Author: ryan-brosas

Pi Hypercharm Provider Foundation

Use when building a pi provider extension: stale-while-revalidate model catalogs with hot-swap, merge precedence over patch/custom/deprecated layers, teed-stream usage capture with settle barriers, agent_settled polling gates, never-throw account fetch ladders, slash-command/interactive settings over one config object, ANSI-aware width math, progressive-tier status widgets, magnitude-tiered number formatting, runtime API-key plumbing behind provider registration, streamSimple delegation adapters, offline catalog-sync choreography, and overlay-list promotion pruning.

ryan-brosas 06a86d1 27 files · 116.2 KB Updated Sep 17, 2026

File contents

Pi-Hypercharm-Provider: Provider Extension Foundation (SWR Catalog + Telemetry Status Line)

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-hypercharm-provider; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.
Recorded revision: main@4520704.
Full provenance, coverage caveats, boundaries, and preserved evidence: references/index.md.

Topic map

Representative topics: Catalog sync; Merge pipeline; Grace period; Usage tee; Settle barrier; Account fetch; Polling gate; Optimistic balance.
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-hypercharm-provider-foundationdescription: Use when building a pi provider extension: stale-while-revalidate model catalogs with hot-swap, merge precedence over patch/custom/deprecated layers, teed-stream usage capture with settle barriers, agent_settled polling gates, never-throw account fetch ladders, slash-command/interactive settings over one config object, ANSI-aware width math, progressive-tier status widgets, magnitude-tiered number formatting, runtime API-key plumbing behind provider registration, streamSimple delegation adapters, offline catalog-sync choreography, and overlay-list promotion pruning.---# Pi-Hypercharm-Provider: Provider Extension Foundation (SWR Catalog + Telemetry Status Line)## 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-hypercharm-provider`; portable upstream identity, license, coverage caveats, and retrieval history are preserved in the index.- Recorded revision: `main@4520704`.- Full provenance, coverage caveats, boundaries, and preserved evidence: `references/index.md`.## Topic map- Representative topics: Catalog sync; Merge pipeline; Grace period; Usage tee; Settle barrier; Account fetch; Polling gate; Optimistic balance.- 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