Menu
Chrono AI 非技术团队 onboarding — 安装 NyxID CLI, 配置 AI 工具 MCP, 克隆战略仓库, 运行每日更新
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Aevatar scheduling & workflow automation: scheduled_agent_creator (cron/one-shot), the long-running task automation playbook, workflow creation semantics (Scope Workflow vs Ornn publish), agent_builder lifecycle, and scheduled-run credential lifetimes (5-minute broker token at fire) with a token_expired triage protocol.
Aevatar channel & delivery how-to: capability tools (code_execute, nyxid_proxy, GitHub PAT fallback, channel bots), token_expired/401 credential triage for capability tools, LLM route selection slash commands, channel_registrations (staged Lark provisioning), and agent_delivery_targets binding.
Configure and prove Aevatar codex_exec for one NyxID account, choosing either operator-managed OpenSandbox or a private NyxID node-backed SSH service. Use for managed allowlist/binding readiness, node registration, forced-command hardening, service binding, Codex authentication/workspace configuration, mandatory public-sample verification, or diagnosing managed sandbox and private SSH failures.
Mount and run harmless Aevatar workflows that prove codex_exec works through either the operator-managed OpenSandbox target or a private NyxID node-backed SSH target. Use after configuring managed access or a personal node, before real tasks, and when diagnosing identity, allowlist, binding, sandbox, service, principal, or Codex runner failures.
Decide — honestly — whether a thing the user wants to build on Aevatar is possible, what its prerequisites are, or why it cannot be done, BEFORE anyone starts building. Use this first whenever a user describes a goal rather than a concrete artifact — "can aevatar do X", "I want a bot that…", "build me something that posts to Twitter / reads my GitHub / replies on Telegram", "is it possible to…", "automate … every day", "let Lark Base trigger a workflow". It teaches the one hard premise (every third-party capability is brokered by NyxID), the two distinct surfaces (outbound connector vs inbound channel), external HTTP trigger options such as Lark Base automation, how to check what is actually connectable, the prerequisite for each capability class, what is host-gated (and so not self-serve), and what is genuinely impossible without new NyxID/Aevatar platform work — so you can negotiate scope and give the user a straight answer plus next steps instead of over-promising. It scopes; it does not build (hand off to
Entry point, panorama, and router for the entire Aevatar skill family — load this FIRST whenever someone wants to build, run, publish, schedule, externally trigger, or operate anything on Aevatar ("create an agent team", "make a workflow / member", "publish or bind a service", "register it with NyxID", "set up a recurring / cron run", "invoke my service", "let Lark Base trigger my workflow"), wants to know whether something is even possible ("can Aevatar do X?", "能不能用 aevatar 实现"), or just wants to know what Aevatar can do. It teaches the object model (scope → team → member[workflow|script|gagent] → service → schedule/external trigger), how to authenticate as a NyxID-bearer REST client, how to resolve your scope, and the two caller modes (client REST vs in-session server-side tools). It does not do the work itself — it routes you to the right companion skill (feasibility-advisor, workflow-authoring, team-builder, service-publisher, scheduler, plus diagnostics probes and the safety-net fallback), held together
Basé sur la classification professionnelle SOC
| name | chrono-onboarding |
| description | Chrono AI 非技术团队 onboarding — 安装 NyxID CLI, 配置 AI 工具 MCP, 克隆战略仓库, 运行每日更新 |
| version | 1.0.0 |
| license | MIT |
| compatibility | Claude Code, Cursor, OpenAI Codex, Windsurf, any MCP-compatible AI tool |
| metadata | {"category":"plain","tag":["onboarding","nyxid","chrono-ai","team","mcp"]} |
本技能引导 Chrono AI 非技术团队成员完成环境搭建, 让你可以用 AI 工具参与公司战略协作。
完成后你将拥有:
当用户说 "onboarding"、"设置环境"、"安装 NyxID" 时, 按下面的步骤引导。每一步完成后确认, 再进入下一步。
先检查用户的系统环境:
echo "=== 系统检查 ==="
echo "OS: $(uname -s)"
echo "Shell: $SHELL"
which git 2>/dev/null && echo "git: OK" || echo "git: 未安装"
which cargo 2>/dev/null && echo "cargo: OK" || echo "cargo: 未安装 (NyxID 需要)"
which gh 2>/dev/null && echo "gh: OK" || echo "gh: 未安装 (GitHub CLI)"
git (必须):
xcode-select --installcargo (NyxID 编译需要):
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shcargo --version 确认gh (GitHub CLI, 用于 /daily):
brew install ghwinget install GitHub.cligh auth logincargo install nyxid-cli
安装完成后验证:
nyxid --version
应该显示 nyxid 0.1.0 或更高版本。
如果你还没有 NyxID 账号:
nyxid register
按提示输入邮箱和密码。注册后验证邮箱。
已有账号直接登录:
nyxid login
登录后确认身份:
nyxid whoami
NyxID 可以作为 MCP Server 连接到你的 AI 工具。根据你使用的工具选择:
nyxid mcp config --tool claude-code
这会自动写入 Claude Code 的 MCP 配置。重启 Claude Code 即可使用。
nyxid mcp config --tool cursor
配置会写入 Cursor 的 MCP settings。重启 Cursor 生效。
nyxid mcp config --tool <tool-name>
运行 nyxid mcp config --help 查看支持的工具列表。
配置完成后, 在 AI 工具中确认 NyxID MCP 已连接。你应该能看到 NyxID 提供的工具 (如 proxy, service 管理等)。
cd ~
git clone https://github.com/ChronoAIProject/chrono-ai-ceo.git
cd chrono-ai-ceo
这是公司的战略仓库, 包含:
strategy/goals.md — 公司北极星和里程碑products/ — 每个产品线的战略文档internal/ — 内部文档 (团队分配、运营)team.yaml — 团队成员和产品线映射grep -A 5 "$(gh api user --jq '.login' 2>/dev/null)" team.yaml
你应该能看到你的名字、Lark ID、角色和产品线。如果找不到, 联系 CEO 添加。
在战略仓库目录下, 用你的 AI 工具运行:
/daily
这会生成你的个人化工作看板, 包含:
如果 cargo install nyxid-cli 失败:
rustup updatexcode-select --installgh auth login --web
用浏览器完成 GitHub 认证。确保你的 GitHub 账号已加入 ChronoAIProject org。
确认 gh api user --jq '.login' 返回的用户名在 team.yaml 中。如果不在, 联系 CEO。
nyxid whoaminyxid mcp config --tool <your-tool>恭喜! 你现在可以: