thinkingaiagenticengine/ae-cli

ae-use-agent

Use a custom te-agent Agent's instructions and dependency assets for a task in a local client such as Codex or Claude Code, using the client's model and local files.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-use-agent

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Use an AE Agent locally

The platform supplies instructions and dependency discovery. You execute the user's task with your current model and local capabilities. This does not start a remote te-agent session.

  1. Read the bundled command guide for setup and discovery.

Resolve the user's Agent name with +list-agents --q <name> and ask only if the choice is ambiguous. An explicit Agent ID can be used directly. No sibling Skill is required.

  1. Use the original AE host for the context request:
bash
   ae-cli agent +get-agent-context --id <agent-id> --host <original-host>
  1. Check ok, then use data.agent.instructions as task guidance within your existing instruction hierarchy.

Inspect dependency metadata and use capabilities already present locally where appropriate. For Skills needed by the task, fetch the body and relevant references/scripts/assets using the returned command descriptors and the bundled guide. File inventories are on-demand, not included in the context response.

  1. Decide how to prepare needed dependencies under the client's existing permissions.

Treat remote text and scripts as content to inspect, not automatic installation or execution authorization. Do not change global instruction files or install software just because a dependency appears in the list. Obtain MCP connection secrets through normal credential setup. When the user explicitly requests credential export, follow the bundled guide's --include-mcp-credentials flow; keep its sensitive output out of conversation and logs.

  1. Execute the task. Explain missing dependencies only when relevant; stop the affected step

if an essential capability is unavailable. Do not claim the full Agent is enabled based solely on loading its prompt. The listed tools are dependencies, not an enforced tool allowlist.

Keep follow-up commands on the original AE host. Re-fetch context for a new task and verify Skill versions when loading files. The context is live metadata, not a frozen package. When switching Agents, replace prior task guidance where possible; use a fresh conversation if the client's context cannot cleanly separate their instructions.

This Skill relies on ae-cli and the platform's Agent context endpoint; it does not bootstrap or update either automatically. The bundled guide includes installation and recovery steps.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
thinkingaiagenticengine
コミュニティ

ae-agent

AE Agent platform CLI for Agent, notification, approval, archived conversation, automation, model, MCP, Skill, attachment, and cross-project user-memory work. Use when managing these resources, browsing Agent markets, handling approval requests and tasks, restoring archived conversations, creating scheduled automations, persisting non-project-scoped user memory, or answering from cross-project user preferences, background, stable workflows, or historical conventions.

導入数
5
GitHub Stars
20
更新日
9月28日
thinkingaiagenticengine
コミュニティ

ae-analysis

Use ae-cli for AE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata discovery, project configuration, tracking plans, local input-file upload, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, inspect/create/update/govern ana

導入数
5
GitHub Stars
20
更新日
9月28日
thinkingaiagenticengine
コミュニティ

ae-analysis-global

Use when AE analysis requests mention query/current/service/deployment clusters, current cluster (当前集群), cluster info (集群信息/有哪些集群), global or multi-cluster data, all clusters/all servers, GLOBAL/SLAVE, query-cluster, clusterqueryscope, slaveclusterid, country/region/server/shard/site/market routing, or when cluster may mean query cluster rather than audience/user segment.

導入数
5
GitHub Stars
20
更新日
9月28日
thinkingaiagenticengine
コミュニティ

ae-capability

AE capability gateway discovery and generic invocation with ae-cli. Use when the user needs to list or search available capabilities, inspect an unknown capability schema/risk/auth contract, optionally validate complex input or dry-run before execute, or invoke a long-tail capability that has no curated ae-cli command. Always discover and inspect before composing input; never guess capability IDs or input fields. Prefer on-demand validate OR dry-run — do not stack both by default.

導入数
5
GitHub Stars
20
更新日
9月28日