lingtai-ai
- 238 skills
- 0 followers
- 4 hours ago last updated
- ▌ Tutorial Guide Orientation 2 · lingtai-aiNested tutorial-guide reference for lessons 1–3: welcome, live architecture discovery, global directory, project directory, and agent working directory.
- ▌ Tutorial Guide Agent Runtime 2 · lingtai-aiNested tutorial-guide reference for lessons 4–6: init.json, lingtai-agent run, heartbeat and signal files, TUI runtime wrapping, and system prompt identity.
- ▌ Tutorial Guide Memory And Molt 2 · lingtai-aiNested tutorial-guide reference for lesson 8: intrinsics, memory layers, molt, charge, and lifecycle continuity.
- ▌ Preset Skill Op Saved Presets 2 · lingtai-aiHow saved presets differ from templates, and the Load/Save/Delete/Bootstrap contract — order, atomicity, and naming.
- ▌ Preset Skill Op Endpoint Capabilities 2 · lingtai-aiBase URL / wire / provider / model / capability declaration shape versus credentials and live probes; includes proven Codex OAuth quota inspection with exact agent query routing and dated official-vs-measured context-window evidence.
- ▌ Preset Skill Op Availability Save Gate 2 · lingtai-aiSave on the preset editor performs local structural validation only — it never makes a live provider/model network call. Real availability diagnosis is owned by /doctor and actual runtime execution.
- ▌ Preset Skill Op Troubleshooting Migration 2 · lingtai-aiBounded first-pass triage for preset problems; routes deeper runtime/update/migration questions elsewhere instead of guessing.
- ▌ Preset Skill Op Activation Session Refresh 2 · lingtai-aiHow a saved preset becomes the running default, first-run/setup choice semantics, propagation, and what /refresh actually switches.
- ▌ Lingtai Preset Skill 2 · lingtai-aiUse when asking about built-in TUI presets, the four provider families, or their shared operations.
- ▌ Tutorial Guide 2 · lingtai-ai bundleThe 12-lesson curriculum for teaching a human how LingTai works — orientation, agent runtime, communication, memory/molt, capabilities, operations, addons, and graduation. Invoke this skill when the human is ready to begin or continue the tutorial.
- ▌ HTML Report 2 · lingtai-ai bundleNested swiss-knife reference for standalone HTML deliverables. Produce polished, self-contained HTML deliverables (research memos, literature maps, dashboards, audit reports, side-by-side comparisons) that humans open in a browser or receive as Telegram/email attachments. Covers a standalone HTML skeleton, math rendering with MathJax (LaTeX in `<pre>`/`<code>` will NOT render), artifact hygiene, and a validation checklist. Read when the human asks for an HTML report, HTML memo, HTML deliverable, or any standalone .html artifact — especially anything containing equations.
- ▌ Minimax CLI 2 · lingtai-aiNested swiss-knife reference for the MiniMax `mmx` CLI and the canonical MiniMax CLI procedure shipped with the TUI: install `mmx-cli`, discover the correct TUI-managed MiniMax preset/key slot without leaking secrets, match mainland vs international regions, and route image/video/music/TTS generation or one-shot shell vision.
- ▌ Bot Guide Avatars · lingtai-aiUse when deciding whether a bot should be a new project, persistent avatar or ephemeral daemon and locating the current avatar creation owner.
- ▌ Bot Guide Channels · lingtai-aiUse when selecting or setting up a LingTai messaging bridge and locating its exact current configuration and readiness documentation.
- ▌ Bot Guide Coverage · lingtai-aiUse when finding the authoritative owner for any LingTai bot-creation topic or checking the guide’s coverage and known implementation gaps.
- ▌
- ▌
- ▌ Preset Skill Openai · lingtai-aiUse when configuring or revising the built-in openai (OpenAI-compatible) TUI preset, including pointing it at another vendor's OpenAI-compatible API or an account pool such as sub2api / subs-pool.
- ▌ Bot Guide Initiation · lingtai-aiUse when choosing the directory, ownership, recipe, model/preset, permissions and bootstrap route for a new LingTai bot.
- ▌ Bot Guide Operations · lingtai-aiUse when verifying bot readiness, maintaining a live bot, or diagnosing recovery, refresh, version and migration problems.
- ▌ Academic Research 2 · lingtai-ai bundleUse when drafting citation-bearing academic writing or revising empirical claims. Nested swiss-knife reference for source verification and keeping manuscript claims anchored to data, not reviewer consensus.
- ▌ Headless Bot 2 · lingtai-ai bundleUse when creating a fresh headless LingTai project, including the bundled Telegram-only provisioning helper.
- ▌ Dev Guide Architecture 2 · lingtai-aiNested lingtai-dev-guide reference for the project architecture: Go TUI/portal monorepo, Python kernel, MCP addon repos, filesystem IPC, and where per-project/per-machine state lives.
- ▌ Dev Guide Contributing 2 · lingtai-aiNested lingtai-dev-guide reference for contribution workflow: issue/worktree/PR discipline, worktree inventory and exact-object approval gates, daemon decomposition, portfolio sweeps, repo-specific build/test commands, skill changes, and anatomy maintenance.
- ▌ Preset Skill Anthropic · lingtai-aiUse when configuring or revising the built-in anthropic (Anthropic-compatible) TUI preset, including pointing it at another vendor's Anthropic-compatible endpoint.
- ▌ Swiss Knife 2 · lingtai-ai bundleUse when checking saved presets, reporting token usage, preparing HTML deliverables or verifying academic evidence. Also routes to retained MiniMax, Xiaomi MiMo and Zhipu provider references.
- ▌ Lingtai Tui Help 2 · lingtai-ai bundleAnything you need to know about LingTai TUI. Read this first for the stable mental model, feature map, interface/slash-command help, or the right source/manual route for a TUI question. Exact command prose lives in the localized help assets, Go structure lives in `lingtai-tui-anatomy`, and presets, Portal, tutorials, updates, and addons keep their own top-level skills.
- ▌ Lingtai Bot Guide · lingtai-aiUse when creating, connecting, verifying, maintaining, recovering or migrating LingTai bots, headless projects, or independent persistent agents.
- ▌ Lingtai Dev Guide 2 · lingtai-ai bundleRouter for contributing to LingTai. Use when changing code or docs, setting up a dev environment, navigating the TUI/portal repo or Python kernel, developing MCP addons, troubleshooting a running network, auditing security, running a runtime self-check, prepping a PR review, or stewarding a new skill. For developers and contributors; for end-user lessons, use tutorial-guide.
- ▌
- ▌ Context Manual 2 · lingtai-ai bundleUse for an unfamiliar or consequential context operation, session journaling, handoff, or context-loss recovery; routine calls can follow the schema.
- ▌
- ▌ Cloud Mail MCP Manual 2 · lingtai-ai bundleProgressive-disclosure usage manual for Cloud Mail REST email actions. Read it when action filters/ids, setup/authentication, polling/settings, or side-effect detail is needed. Returned by action='manual'; nested references are packaged but not embedded. Calls use the strict LTP-v2 envelope.
- ▌ Knowledge Manual 2 · lingtai-aiRead before creating or organizing private durable knowledge (`knowledge/<name>/KNOWLEDGE.md`) or cross-references; use it for local memory, not portable procedures.
- ▌ Web Manual 2 · lingtai-ai bundleFirst-call search→browse route for the single web capability; exact settings, complete-output, provider, and public-URL hazards are retained here or routed to one focused reference.
- ▌ Notification Manual 2 · lingtai-aiEntry manual for the standalone `notification` tool and its `.notification` mirrors. Routine check uses the schema; read a reference for unfamiliar payload, producer, one-shot delivery, delay, or settings detail. Large-result compaction belongs to `context-manual`, not here.
- ▌ Pad Manual 2 · lingtai-aiRead before editing the living Pad, pinning references, or preparing Pad state for rebuild/molt.
- ▌ MCP Manual 2 · lingtai-ai bundleRead-only MCP status router: distinguish catalog, registered, and active servers; inspect effective settings safely; and route authorized setup or recovery to the exact provider and runtime references. Routine info/settings/manual calls need no ritual manual reading. This is not an MCP protocol guide.
- ▌ Psyche Manual 2 · lingtai-aiCompact router for Psyche's private-memory and procedure domains (pad, knowledge, skills), the shared file→rebuild model, redacted settings, and the separate fixed-instructions disclosure and retirement guidance.
- ▌ System Manual 2 · lingtai-ai bundleShort router for runtime, lifecycle, identity, Agent/Project relocation, refresh transactions, presets, settings, update/mismatch diagnosis, LLM adapters, and operating procedures.
- ▌ Telegram Task Card Projection Notice 2 · lingtai-ai bundleShipped retained-legacy/projection notice for Telegram Task Card files. The public `task_card` tool is intrinsic and documented at src/lingtai/tools/task_card/manual/SKILL.md; Telegram only projects the intrinsic taskcard/status + taskcard/taskcard.md artifact read-only. It also explains the Telegram-only per-call API token list-price estimate line and its since-molt SESSION Cost total.
- ▌ Lingtai Doctor 2 · lingtai-ai bundleRead-only health diagnostics when an agent looks dead but the evidence is mixed, or a migration may have left stale MCP/addon paths; run before deciding to mail, refresh, CPR, or edit persistent configuration. Includes a bundled read-only `doctor.py`.
- ▌ Lingtai Manual 2 · lingtai-aiRetirement reference for legacy character memory; use unified Pad and Knowledge.
- ▌ Lingtai Recipe 2 · lingtai-ai bundleMenu manual (not a tool) for recipes — the named payload that shapes an orchestrator's greeting, ongoing behaviour, and shipped library; every LingTai project uses one. Routes to `reference/recipe-format/SKILL.md` (authoring/customising) and `reference/export-recipe/SKILL.md` (publishing for new networks), and warns about the three different recipe-shaped artifacts that can co-exist in one project — easy to conflate. Do NOT use for one-off exports of a single agent (that's just `cp -r`), or for in-network behaviour edits to the live system.
- ▌ Imap MCP Manual 2 · lingtai-ai bundleProgressive-disclosure usage manual for the IMAP/SMTP email MCP. Read this router for unfamiliar or consequential workflows and deeper detail on real-mail side effects, external-reply policy, account selection, compound email IDs, attachments, mailbox mutations, contacts, or settings. Pull the full body with action='manual'; do not guess provider or account details.
- ▌ Shell Manual 2 · lingtai-ai bundle**Read before running a long-lived agent/coding CLI as a shell subprocess**, or before setting up cron/launchd/systemd timers or scheduled reminders. Routes shell-side async+poll supervision, host-scheduler setup, LingTai wake-by-mailbox-drop, one-shot reminders, safe cleanup, and the bounded, verified discipline for durable filesystem reads and edits. Per-backend CLI operational detail (command shapes, flags, env contracts) for daemon-backed CLIs lives in `daemon-manual` → `reference/cli-backends/SKILL.md`.
- ▌ Feishu MCP Manual 2 · lingtai-ai bundleConcise progressive-disclosure usage manual for the Feishu (Lark) MCP. Ordinary schema-sufficient calls can start here; unfamiliar setup, cards, callbacks, compound replies, partial delivery, and recovery route to one focused reference. It covers the strict action envelope, recipient/account checks, and the no-fallback/no-blind-retry safety boundary.
- ▌ Wechat MCP Manual 2 · lingtai-ai bundleProgressive-disclosure usage manual for WeChat/iLink: first safe read, exact IDs, external send/reply, media partials, and standalone poller/setup hazards. Use the schema for routine calls; load this manual for media details, unfamiliar results, setup, or recovery.
- ▌ Email Manual 2 · lingtai-aiInternal LingTai mail: send/read/dismiss/reply, absolute-path addressing, delayed self-send time capsules, and full-body persistent notifications. Not internet email (see `mcp-manual`) or recurring schedules (see `shell-manual`).
- ▌ Avatar Manual 2 · lingtai-ai bundleUse for an unfamiliar or consequential Avatar spawn, shallow/deep choice, detached lifecycle, recovery, or footprint review. Routine schema-sufficient spawns can use the tool directly.
- ▌ Daemon Manual 2 · lingtai-ai bundleUse for unfamiliar daemon delegation, backend-specific work, stalled or failed runs, completion checks, or consent-gated cleanup. Routine calls can start from the advertised schema.
- ▌ Plugin Manual 2 · lingtai-ai bundleRead-only Agent Plugins v1.0.0 catalog: registered versus discovered, authorized registration refresh, containment, and skipped-component diagnosis. Use for unfamiliar or consequential plugin work; routine schema-sufficient calls can go straight to `info`.
- ▌ Skills Manual 2 · lingtai-ai bundleRead before authoring, installing, or sharing a skill in `.library/custom/<name>/`, adding configured skill roots, or diagnosing a catalog entry; this teaches the Skills system, not bundled skill procedures.
- ▌ Vision Manual 2 · lingtai-ai bundleUse the Vision schema directly for ordinary image analysis; route setup, borrowing, settings, and recovery to focused references.
- ▌ Telegram MCP Manual 2 · lingtai-ai bundleProgressive-disclosure usage manual for the Telegram MCP tool. The resident schema carries safe first-use guidance; call `manual` for the action map, inbound-first/reply routing, channel/media/rendering rules, settings, Task Card projection, and error handling.
- ▌ Whatsapp MCP Manual 2 · lingtai-ai bundleProgressive-disclosure usage manual for the personal-account WhatsApp MCP tool. Read this when you need detail beyond the concise action description: the single-session whatsapp-web.js bridge and QR pairing, strict send/reply/react semantics, opaque message IDs, check/read/search and local contacts, bridge media and the absence of inbound downloads, LICC wake/replay/allowlist behavior, read-only redacted settings, external side effects, and ToS/ban risk. Pulled on demand via action='manual'; you do not need to call it before every send.
- ▌ Substrate Manual 2 · lingtai-aiNested system-manual reference: the expanded form of the resident substrate prompt — body/extensions, lifecycle states, the `system` tool in practice, communication and memory layers, collaboration topology, MCP/addon ownership, and (§11) the canonical `init.json` composition and preset runtime model. Route via `system-manual` when it is unclear whether this is the right node.
- ▌ Procedures Manual 2 · lingtai-aiNested system-manual reference: the expanded form of the resident procedures prompt — progressive disclosure, responsiveness and side-effect authorization, the daemon workflow methodology, depositing work, idle/lifecycle, skill routing, deliverables, artifact sharing, and issue reporting. Route via `system-manual` when it is unclear whether this is the right node.
- ▌ System Settings Inventory Reference 2 · lingtai-aiExact read-only System catch-all settings inventory: ownership, effective sources, defaults, accepted values, invalid behavior, redaction, timing, authorized change procedures, and explicit non-settings.
- ▌ Tool Plugin Settings Reference 2 · lingtai-aiDeveloper reference for opting one tool family into bounded, read-only settings discovery without changing other families.
- ▌ Runtime Update Checks 2 · lingtai-aiNested system-manual reference for update, source, install, nudge, and runtime-mismatch diagnosis. Owns interpreter/provenance evidence and the source/venv cutover handoff; routes refresh sequencing to refresh-precheck.
- ▌ Daemon Backend Lingtai 2 · lingtai-aiNested daemon-cli-backends reference for the built-in `lingtai` daemon backend (the in-process ChatSession default). Read this when routing a daemon task to the built-in backend: it has no external CLI and no `backend_options` flag surface; this page routes you to the live authorities for preset selection/inspection, lingtai/tools/skills/MCP inheritance, and the daemon completion contract. It is not a rules catalog.
- ▌ Daemon Backend Claude P 2 · lingtai-aiNested daemon-cli-backends reference for the claude-p (alias claude-code) daemon backend's flag surface. Read this only when a daemon task needs Claude Code-specific CLI flags (model selection, fallback model, tool restrictions): it routes you to the installed CLI's live help via shell and shows how to translate that help into the generic `backend_options` mechanism. Also owns Claude Code's operational core: the `env -u` auth hygiene wrapper, weekly-limit smoke test, stale-token diagnosis, and the budget/timeout/SDK background caveats. It is not a flag catalog.
- ▌ Daemon Backend Qwen Code 2 · lingtai-aiNested daemon-cli-backends reference for the Qwen Code (`qwen-code` / `qwen`) daemon backend's flag surface. Read this only when a daemon task needs Qwen-specific CLI flags (model selection, provider tunables): it routes you to the installed CLI's live help via shell and shows how to translate that help into the generic `backend_options` mechanism. It is not a flag catalog.
- ▌ Migration Project Move · lingtai-aiNarrow POSIX contract for the bundled initiating-Agent whole-Project same-volume self-move helper.
- ▌ Migration Agent Name Move · lingtai-aiNarrow contract for the self-contained POSIX same-parent Agent workdir/address rename script and its transactional runtime/MCP relocation.
- ▌ Telegram Rate Limits 2 · lingtai-aiCurrent official Telegram Bot API flood-control guidance: published quotas, `retry_after` semantics, documented unknowns, and safe client policy. Read before changing Telegram send cadence, programmable Task Card cadence, or 429 recovery behavior.
- ▌ Daemon CLI Backends 2 · lingtai-ai bundleNested daemon-manual reference for backend choice, native versus prompt-only MCP, CLI options, list/ask behavior, and per-backend live-help routes.
- ▌ Summarize Manual 2 · lingtai-aiOperational guide for recording tool-result summaries, applying them with a full rebuild, recovering raw evidence, and choosing summarize versus molt.
- ▌ Email Manual Settings Reference 2 · lingtai-aiFocused Email settings reference for the four SHOW rows, installed limits, manifest subscription source, redaction, precedence, timing, and the read-only boundary. Read when interpreting settings rows.
- ▌ Email Manual Actions And Storage 2 · lingtai-aiFocused Email reference for action inputs, folders, check filters, delivery, self-send/time capsules, contacts, attachments, and mailbox persistence. Read when the schema and first-call map are not enough.
- ▌ Psyche Settings Reference 2 · lingtai-aiDeep reference for Psyche's redacted settings SHOW, strict owner-document grammar, precedence, timing, rollback, and six stable anchors.
- ▌ Notification Manual Channel Model 2 · lingtai-aiNotification payload, mirror, allowlist, hook, delivery, delay, and block-cap reference. Read after notification-manual when interpreting current channel state or diagnosing delivery; one-shot delivery and producer-state safety belong to dismissal-safety.
- ▌ Subs Pool · lingtai-aiNested system-manual reference pointing to subs-pool, the external Codex subscription pool. LingTai has no built-in Codex account pool; use this to pool several ChatGPT/Codex accounts behind one local Responses endpoint reached through provider `openai` with `wire_api: responses`, or to migrate a removed `codex-pool`/`custom` provider config.
- ▌ Bash Notification Reminders 2 · lingtai-aiNested shell-manual reference for one-shot wakeup reminders using `.notification/cron.json`: payload, atomic writer, shell example, and the rest checklist for pending work.
- ▌ Email Manual Addressing And Replies 2 · lingtai-aiFocused Email reference for absolute-path addressing, reply return routes, legacy mail without a route, safe same-channel replies, sender identity display, and local mailbox-ID privacy. Read when routing or answering internal mail.
- ▌ Goal Manual 2 · lingtai-aiGoal notification manual: `.notification/goal.json` source-of-truth, fields, instructions, idle reminders, protected goal behavior, and cancellation or completion semantics.
- ▌ Notification Manual Dismissal Safety 2 · lingtai-aiOne-shot notification delivery and producer-state safety reference: there is no public notification dismiss action; delivery never clears producer state; how deliberate check, post-molt, protected channels, hooks, and legacy large-result reminders behave. Read after notification-manual when unsure whether a notification will reappear or how to resolve its producer state.
- ▌ LLM Adapters 2 · lingtai-aiNested system-manual reference for LingTai's four built-in LLM provider families (openai, anthropic, codex, claude-code): what each adapter is, how it is configured and dispatched, its standard parameters (wire_api, thinking, service_tier), how other vendors are reached through the OpenAI/Anthropic-compatible families, and which removed provider names now fail validation.
- ▌ Recipe Export Flow 2 · lingtai-aiNested lingtai-recipe reference for exporting a standalone recipe bundle from a live network or methodology: scope disambiguation, human-in-the-loop metadata collection, bundle authoring, validation, git initialization, and handoff.
- ▌ Recipe Format Reference 2 · lingtai-aiNested lingtai-recipe reference for authoring and validating recipe bundles: bundle structure, .recipe/recipe.json schema, behavioral layers, library sibling mechanics, locale fallback, validator checks, hand-authored recipes, testing, and publishing.
- ▌ Email Manual Notifications And Delivery 2 · lingtai-aiFocused Email reference for daemon delivery, heartbeat/liveness, bounce recovery, unread payloads, persistent bodies, overflow, and read-state refresh. Read when delivery or notices need diagnosis.
- ▌ Migration Guide 2 · lingtai-ai bundleConclusion-first router for authorizing, selecting, recovering, and proving a mechanical Agent workdir/address or whole-Project path move.
- ▌ Refresh Precheck 2 · lingtai-aiNested system-manual reference and single owner for a refresh transaction: select same-runtime reload, source/venv cutover, or failure recovery; run only triggered owner checks; issue exactly one refresh; capture one targeted receipt.
- ▌ Sqlite Log Query 2 · lingtai-ai bundleNested system-manual reference for the additive SQLite/`log.sqlite` sidecar over LingTai's JSONL runtime traces. Read it when you need `lingtai-agent log doctor|query|rebuild`, read-only SQL safety and WAL/rebuild caveats, the events/chat_entries/token_entries schema, quick-start snippets, SQL recipes (`tool_call_id` lifecycle, tool result stats and percentiles, spilled/large tool results), gotchas, or the redaction rules. Runtime trace forensics start here; trajectory mining is the sibling `trajectory-mining`.
- ▌
- ▌ Lingtai Help Router · lingtai-ai bundleRoute LingTai help requests to stable, product-owned child skills.
- ▌ Lingtai Migration Router · lingtai-ai bundleRoute LingTai TUI and kernel release migrations to their product-owned tag histories.
- ▌ Lingtai Installation · lingtai-ai bundleRoute ordinary installation, removal, and explicit installation maintenance assets.
- ▌ Lingtai Kernel Dev · lingtai-aiMandatory repository-local development guide for LingTai's Python kernel and runtime. Use this before changing code, architecture documents, tests, packaging, capabilities, adapters, or developer documentation in lingtai-kernel. Routes each task through the exact baseline, the distributed ANATOMY/CONTRACT systems, focused validation, and pull-request safety gates.
- ▌ Imap MCP Manual · lingtai-ai bundleProgressive-disclosure usage manual for the IMAP/SMTP email MCP. Read this router for unfamiliar or consequential workflows and deeper detail on real-mail side effects, external-reply policy, account selection, compound email IDs, attachments, mailbox mutations, contacts, or settings. Pull the full body with action='manual'; do not guess provider or account details.
- ▌ Shell Manual · lingtai-ai**Read before running a long-lived agent/coding CLI as a shell subprocess**, or before setting up cron/launchd/systemd timers or scheduled reminders. Routes shell-side async+poll supervision, host-scheduler setup, LingTai wake-by-mailbox-drop, one-shot reminders, and safe cleanup. Per-backend CLI operational detail (command shapes, flags, env contracts) for daemon-backed CLIs lives in `daemon-manual` → `reference/cli-backends/SKILL.md`.
- ▌ File Manual · lingtai-aiRead/write/edit/glob/grep guide for LingTai's `file` tool: safe overwrite/edit discipline, explicit non-UTF-8 routing, SHOW-only policy, and pagination recovery.
- ▌ Soul Manual · lingtai-ai bundleRead before calling `flow`, making consequential or unfamiliar Soul config/voice changes, or recovering a disabled/ongoing flow; routine inquiry, dismiss, and settings calls are schema-sufficient.
- ▌ Feishu MCP Manual · lingtai-ai bundleConcise progressive-disclosure usage manual for the Feishu (Lark) MCP. Ordinary schema-sufficient calls can start here; unfamiliar setup, cards, callbacks, compound replies, partial delivery, and recovery route to one focused reference. It covers the strict action envelope, recipient/account checks, and the no-fallback/no-blind-retry safety boundary.
- ▌ Wechat MCP Manual · lingtai-ai bundleProgressive-disclosure usage manual for WeChat/iLink: first safe read, exact IDs, external send/reply, media partials, and standalone poller/setup hazards. Use the schema for routine calls; load this manual for media details, unfamiliar results, setup, or recovery.
- ▌ Email Manual · lingtai-aiInternal LingTai mail: send/read/dismiss/reply, bare-path addressing, delayed self-send time capsules, and full-body persistent notifications. Not internet email (see `mcp-manual`) or recurring schedules (see `shell-manual`).
- ▌ Avatar Manual · lingtai-ai bundleUse for an unfamiliar or consequential Avatar spawn, shallow/deep choice, detached lifecycle, recovery, or footprint review. Routine schema-sufficient spawns can use the tool directly.
- ▌ Daemon Manual · lingtai-aiUse for unfamiliar daemon delegation, backend-specific work, stalled or failed runs, completion checks, or consent-gated cleanup. Routine calls can start from the advertised schema.
- ▌ Plugin Manual · lingtai-ai bundleRead-only Agent Plugins v1.0.0 catalog: registered versus discovered, authorized registration refresh, containment, and skipped-component diagnosis. Use for unfamiliar or consequential plugin work; routine schema-sufficient calls can go straight to `info`.