Tiantian Fund TTSkill Runtime

Problem

When agents call Tiantian Fund capabilities, they may treat the entry as a one-time install, rerun base package setup, or ask users to configure API keys. This skill focuses on the local ttskill runtime: check command availability and login state first, then route to the right atomic skill_id instead of treating the install guide as a daily step.

How It Works

• Pre-use checks: verify that ttskill exists and reports a healthy status; if so, proceed to business routing without reinstalling the base package.
• Login and updates: handle cli_login_required, expired tokens, or outdated packages by guiding browser authorization or triggering the relevant install / update flow.
• Business calls: select a concrete atomic skill_id and action from routing or the local business package list; for complex parameters, write the request body to a temporary file and pass it via --body.
• Result handling: omit --summary when full analysis is needed, and return refined business information rather than raw JSON, tokens, cookies, or other sensitive fields.

Boundaries

It is useful for engineer environments that already have or are preparing Tiantian Fund TTSkill, especially when enforcing runtime checks and call order. It is not a business-rule interpreter, and category names are not callable skills. Login state must be judged from ttskill status or actual call results, not from chat history.