talos-action-development

Develop and maintain standalone Talos actions for on-chain operations across EVM networks.

152|115|Updated Aug 3, 2020
One-click install
npx skills add https://github.com/OriginProtocol/origin-dollar --skill talos-action-development-originprotocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: talos-action-development
Source: https://github.com/OriginProtocol/origin-dollar/tree/main/contracts/tasks/actions
Command: npx skills add https://github.com/OriginProtocol/origin-dollar --skill talos-action-development-originprotocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ethers.

What problem does it solve? It standardizes how engineers author, modify, and maintain Talos actions in contracts/tasks/actions so that transaction-writing operations stay safe, chain-guarded, and consistent with production schedules. ## Core Features & Use Cases - Action authoring conventions: Enforces the action() wrapper pattern, camelCase naming, params builder usage, and explicit chains guardrails for every action. - Contract binding guidance: Directs use of getContract and getContractAt with curated ABIs, plus logTxDetails for write transactions instead of raw calldata. - Schedule and catalogue maintenance: Covers updating migrations/seed_schedules.sql, docs/ACTIONS.md, regenerating the actions inventory, and rebuilding the runtime catalogue. - Use Case: When adding a new scheduled action like a vault rebase on Base, follow the Skill to define chain guardrails, validate signer authority, register parameters, and update the schedule and documentation in the same change. ## Quick Start Ask the assistant to create a new Talos action that calls a specific contract method on a given chain, following the conventions in this Skill.

Frequently Asked Questions about talos-action-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Talos action?

Create a file in tasks/actions matching the camelCase action name, wrap the logic with the action() helper from tasks/lib/action, define chains guardrails and params, then run it with pnpm exec tsx tasks/run.ts <actionName> --network <network>.

How do Talos actions get scheduled in production?

Production schedules are defined in migrations/seed_schedules.sql, and the Talos runner loads the generated catalogue from actions-catalog.json. Actions self-register through the action() wrapper and are never registered as ops tasks.

Should I use getContract or getContractAt for contract bindings?

Use getContract with a committed deployment name for direct bindings, and getContractAt with a curated interface ABI for proxy or interface calls. Avoid raw selector encoding and signer.sendTransaction when the method name is known.

What verification steps are required after changing an action?

Run pnpm prettier:ts and pnpm typecheck, regenerate docs/talos-actions-inventory.md with the action-chains script if entry points changed, and update docs/ACTIONS.md when scheduled behavior changes.

Can two transaction-writing actions run on the same schedule?

Avoid co-scheduling two transaction-writing actions for the same signer within a five-minute window. Check migrations/seed_schedules.sql before enabling any schedule, and never enable a manual-only action without explicit authorization.