agentleFS
ChainGPT-orgChainGPT-org/chaingpt-claude-skill/skills/drift/SKILL.md

drift

Skill7 starsChanged 53 days agoMITView on GitHub

Inspect the legacy Drift Protocol integration and its availability limits. The original program is paused and hosted data endpoints are unavailable. Tools remain read-only and must not silently use Velocity data. Triggers: drift, drift protocol, SOL-PERP, drift funding, app.drift.trade.

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat their market, orderbook, funding and account reads as unavailable until a compatible legacy data source is independently verified.

    line 10
  2. Distinctive:

    All five tool names are retained for compatibility.

    line 23
  3. Distinctive:

    Verify its ownership, program identity, response schema, units and freshness before using its output.

    line 35
  4. Distinctive:

    Do not connect a wallet, fund an account or initiate migration as part of availability checks.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ChainGPT Drift Skill

The original Drift program is paused. The hosted dlob.drift.trade and data.api.drift.trade services do not resolve from the validation environment. Treat their market, orderbook, funding and account reads as unavailable until a compatible legacy data source is independently verified. Do not recommend the old trading or funding-arbitrage workflows as currently executable.

The official migration guide describes Velocity as a separate deployment with a new program ID and no carried-over account state. Its quote asset and SDK also differ. Never return Velocity markets, accounts or prices under the existing Drift tool names. Adding Velocity requires a separately identified integration and validation. Changing SOLANA_RPC_URL does not repair these HTTP data endpoints.

Tools

All five tool names are retained for compatibility. They read legacy Drift data and never sign or broadcast transactions.

ToolLegacy data
chaingpt_drift_marketsPerp market list
chaingpt_drift_marketOne-market detail
chaingpt_drift_orderbookL2 bids and asks
chaingpt_drift_fundingFunding history
chaingpt_drift_userAccount collateral, positions and orders

DRIFT_DLOB_URL can select a trusted service implementing the legacy routes. Verify its ownership, program identity, response schema, units and freshness before using its output. The override does not resume the onchain program. Do not connect a wallet, fund an account or initiate migration as part of availability checks. Surface errors and missing coverage explicitly.

Reference

  • Provider investigation and remaining gaps
  • Legacy app pause notice
  • Original Drift program: dRiftyHA39MWEi3m9aunc5MzRF1JYuBsbn6VPcn33UH
  • Legacy public endpoints: https://dlob.drift.trade, https://data.api.drift.trade

These tools cost 0 ChainGPT credits. Successful fixture tests establish handler behavior, not live availability or current market liquidity.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.