pendle-pt-yield-strategy
Pendle PT fixed-yield strategy for market scanning, ranking, position tracking, maturity monitoring, and execution planning. Prefer managed wallet execution through Privy or a similar policy-controlled wallet backend, and otherwise fall back to manual user-executed transactions. Use when the user wants to research Pendle PT opportunities, choose stable-ish PT markets, monitor active PT positions, or prepare Pendle PT deposit, redeem, withdraw, and rollover actions with explicit confirmation and clear wallet-path disclosures.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/agnostic98/pendle-pt-yield-strategyPendle PT Yield Strategy
Pendle PT strategy skill for fixed-yield workflows built around Principal Tokens.
This publishable package is intentionally scoped to:
- analysis / monitoring
- execution planning
- managed-wallet-oriented operation guidance
- manual execution fallback
It does not bundle raw secret-key signing code. It does not bundle direct transaction-submission helpers that read local wallet secrets.
Wallet philosophy
Default to the safest practical wallet path.
Priority order:
- Managed wallet with policy controls — preferred
- Manual user-executed transaction flow — fallback
- Do not default to raw secret-key runtime signing in this public package
This public package is designed to avoid normalizing secret key export or runtime secret-key injection as the standard path.
Preferred wallet path: Privy or another managed wallet layer
The preferred execution model for this skill is a managed wallet system with policy controls, spend limits, and explicit operator setup.
Use a managed wallet provider such as Privy when available. That is the preferred deployment pattern for agentic execution.
Why this is preferred:
- avoids normalizing raw secret key export as the default
- supports policy-based controls and safer operational boundaries
- is a better fit for production agent workflows
- maps better to the security posture expected for agentic onchain systems
Current behavior of this package
This package helps the agent:
- scan and rank markets
- plan deposits, redeems, exits, and rollovers
- track positions in local JSON state
- monitor maturities and prepare the next action
- clearly state the expected managed-wallet or manual-execution path
Actual transaction submission should happen through:
- a managed wallet backend such as Privy, orchestrated by the host environment
- or a manual user-executed wallet flow
If the host environment already has the privy skill installed, prefer using
that wallet layer for transaction execution and use this skill for Pendle
market/position logic plus execution planning.
Supported execution modes
Mode 1 — Managed wallet execution via Privy or equivalent
Preferred.
Use this when the runtime has:
- a managed agent wallet system
- policy controls / spending limits
- server-side transaction execution with guardrails
In this mode, this skill should:
- scan / rank the market
- preview the intended Pendle action
- ask for explicit confirmation
- route execution through the managed wallet backend
- update
data/positions.json
When privy skill is available, prefer that integration path.
Mode 2 — Manual user-executed transaction flow
Fallback.
Use this when no managed wallet is configured.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-agnostic98-pendle-pt-yield-strategy": {
"enabled": true,
"auto_update": true
}
}
}