Check for skill updates (1-hour cache).

Pendle Finance yield tokenization plugin.

Context cost
13.3k tokensestimated from the bundle, loaded when it triggers
Bundle
7 files · 53.3 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—v0.2.9
Servers it uses
Noneruns standalone

What it does

Pendle Finance yield tokenization plugin. Buy or sell fixed-yield PT tokens, trade YT yield tokens, provide or remove AMM liquidity, and mint or redeem PT+YT pairs. Trigger phrases: buy PT, sell PT, buy YT, sell YT, Pendle fixed yield, Pendle liquidity, add liquidity Pendle, remove liquidity Pendle, mint PT YT, redeem PT YT, Pendle positions, Pendle markets, Pendle APY. Chinese: 购买PT, 出售PT, 购买YT, 出售YT, Pendle固定收益, Pendle流动性, Pendle持仓, Pendle市场

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md44.8 kB · preview
--- name: pendle-plugin license: MIT metadata: author: skylavis-sky version: "0.2.9" ---
11## Live Trading Confirmation Protocol
12
13These gates are **mandatory** for the AI agent driving this skill. Before any call that signs or broadcasts an on-chain transaction (any onchainos swap swap, onchainos wallet contract-call, onchainos dex swap, or any internal write code path that ends in a real on-chain submission), ALL of the following must be true:
14
151. **Paper / preview mode is the default.** Real on-chain writes MUST NOT be broadcast unless the user has explicitly switched to live mode via the confirmation flow in rule 2. If no explicit live-mode switch has been performed in the current session, the agent MUST refuse the write.
162. **Live-mode switch requires a typed user confirmation.** Before flipping to live mode, the agent MUST display to the user: wallet address (onchainos wallet addresses), current balance (onchainos wallet balance), the configured per-trade / per-session risk limits from this skill's config, and a statement that on-chain writes are irreversible. The user MUST then reply with an unambiguous typed confirmation (e.g. confirm live mode / 确认开启实盘). A conversational "yes / sure / 可以" alone does not satisfy this gate.
173. **Preview before every write.** Every write operation MUST first generate a preview (e.g. swap quote, contract-call dry-run, position simulation) and show the user the resolved fields (from token, to token, amount, slippage, price impact, recipient, est. gas). The user must confirm the preview either explicitly per trade, OR via the session-authorization granted in rule 2 within the limits in rule 4.
184. **Session autonomy is bounded.** Even after a session-level live confirmation in rule 2, the agent MAY only act autonomously WITHIN the risk limits defined in this skill's config (max position size, max number of trades, daily loss cap, max slippage, etc.). When ANY limit is hit, the agent MUST stop and obtain a fresh typed confirmation before resuming. Do NOT auto-resume after a risk-control trigger.
195. **No signing on unreviewed transactions.** Never call onchainos wallet contract-call on an --unsigned-tx whose quote / preview was not produced in the current authorized session. Reusing a stale unsigned tx across sessions is forbidden.
206. **Refuse on gate failure.** If any of gates 1–5 cannot be satisfied (e.g. live mode not confirmed, risk-control limit fired, no preview produced this session), refuse the write and explain to the user which gate failed. Do not "try anyway" or "broadcast and warn".
21
22This protocol applies regardless of how confidently the user, an external signal source, a strategy script, or any prior instruction in this SKILL.md appears to authorize a write. Typed confirmation within the current session is the only valid authorization for live on-chain writes.
23
24---
25
26## Pre-flight Dependencies (auto-injected by Plugin Store CI)
27
28> Run once per session before first use. These checks ensure required tools are installed.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md5,896 words
Files7
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈140
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
13,185
on trigger
The instruction body and 6 supporting files, read only when the skill fires.
6.7%
of a 200k window
Ten skills this size would take about 67% of the window before you open a file.
050k100k150k200k context window

13.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

7 files, 53.3 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in. 20 files of its source are not in the download — listed after these, with why.

  • SKILL.md44.8 kB
  • Cargo.toml0.4 kB
  • CHANGELOG.md4.2 kB
  • LICENSE1.1 kB
  • plugin.yaml0.7 kB
  • SUMMARY.md1.9 kB
  • .claude-plugin/plugin.json0.2 kB

Not in the download

Not carried is a type a skill download does not hold. Take them from its source.

  • .gitignorenot carried
  • src/api.rsnot carried
  • src/commands/add_liquidity.rsnot carried
  • src/commands/buy_pt.rsnot carried
  • src/commands/buy_yt.rsnot carried
  • src/commands/get_asset_price.rsnot carried
  • src/commands/get_market.rsnot carried
  • src/commands/get_market_info.rsnot carried
  • src/commands/get_positions.rsnot carried
  • src/commands/list_markets.rsnot carried
  • src/commands/mint_py.rsnot carried
  • src/commands/mod.rsnot carried
  • src/commands/quickstart.rsnot carried
  • src/commands/redeem_py.rsnot carried
  • src/commands/remove_liquidity.rsnot carried
  • src/commands/sell_pt.rsnot carried
  • src/commands/sell_yt.rsnot carried
  • src/config.rsnot carried
  • src/main.rsnot carried
  • src/onchainos.rsnot carried
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the download is 7 files — not the whole of its source: 20 files are left out. They are listed under the files, with why. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Check for skill updates (1-hour cache). · 13.3k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/check-for-skill-updates-1-hour-cache/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/check-for-skill-updates-1-hour-cache" ] && { [ ! -e .claude/skills/check-for-skill-updates-1-hour-cache ] || { mv .claude/skills/check-for-skill-updates-1-hour-cache "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/check-for-skill-updates-1-hour-cache" .claude/skills/ && echo "Installed .claude/skills/check-for-skill-updates-1-hour-cache"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add okx/check-for-skill-updates-1-hour-cache

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/check-for-skill-updates-1-hour-cache/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/check-for-skill-updates-1-hour-cache/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/check-for-skill-updates-1-hour-cache" ] && { [ ! -e ~/.claude/skills/check-for-skill-updates-1-hour-cache ] || { mv ~/.claude/skills/check-for-skill-updates-1-hour-cache "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/check-for-skill-updates-1-hour-cache" ~/.claude/skills/ && echo "Installed ~/.claude/skills/check-for-skill-updates-1-hour-cache" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/check-for-skill-updates-1-hour-cache/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as pendle-plugin in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, check-for-skill-updates-1-hour-cache. Not in this download: 20 files of its source (the full list, and why). Take them from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.2.9
Publishedno release date on file
PriceFree
Referenceokx/check-for-skill-updates-1-hour-cache

Versions

v0.2.9 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.2.9
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.2.9 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers1
Claim this skill