跳到正文
cccskills
免费在 GitHub 公开

nac-onboarding

Install and configure Arcee AI nac, get the user into the nac dashboard, and connect their MCP client to nac. Use when a user asks to get started with nac, connect nac to an agent, add MCP servers, or expose nac's MCP server to Claude Code, Codex, OpenCode, or another MCP client.

中文简介正在准备中。当前显示原文说明。

arcee-ai/nac星标 291(GitHub 291 + cccskills 0)

实测评分 未实测

查看安装方法

包含的文件（2）

  • SKILL.md2.6 KB
  • agents/openai.yaml188 B

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

NAC onboarding

Get the user to a running nac dashboard as fast as possible, then connect their MCP client. Authentication, model choice, and MCP server setup all happen in the dashboard UI — do not walk the user through them in chat.

Keep credentials private: if the user ever needs to enter a key or complete a device login, they do it themselves in the UI or their own shell; never request a token in chat or write one into a tracked file.

1. Install and launch

  1. Check whether nac-web is available with nac-web --version.

  2. If it is missing, install the latest stable release:

    curl -fsSL https://raw.githubusercontent.com/arcee-ai/nac/main/scripts/install.sh | sh

  3. Start nac from the repository the user wants it to work on:

    nac-web

    Use nac-web -C /path/to/project -y when a non-interactive launch is useful. Keep the process running.

  4. Hand the user the dashboard URL (http://127.0.0.1:3210 by default) and confirm it responds. Everything from here — signing in with Arcee or ChatGPT, picking a model, adding MCP servers from the MCP Library — is done in the UI. Point the user at the dashboard's auth and model picker and let them drive.

2. Connect this MCP client to nac

The MCP client is the harness running this session — the agent the user prompted to install the skill. Do not ask which client to use; configure the one you are running in. Add this streamable-HTTP server to your own harness's MCP configuration:

URL: http://127.0.0.1:3210/mcp
Transport: streamable HTTP

This exposes nac session-management tools to the client agent. The listener is intended for the same machine and has no built-in authentication; do not expose it through a tunnel or reverse proxy unless the user adds strong access control.

Use the client's normal MCP configuration mechanism and adapt its configuration syntax around the URL above. Restart or reload the client if it does not pick up the server automatically, then confirm the client can see nac's tools.

Completion checklist

Before calling setup complete, confirm that:

  • nac-web is installed and running, and the dashboard URL responds.
  • The user is in the dashboard and can reach sign-in and the model picker themselves.
  • nac's /mcp endpoint is configured in this harness's MCP client configuration and nac's tools are visible.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

qa

免费

Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test episodes; setup selects or creates a clean worktree for the requested revision, every phase changes to that worktree, slots and paths stay immutable after setup, and preloaded workers never dispatch.

中文简介正在准备中。当前显示原文说明。

arcee-ai/nac2912026年10月26日 更新

release

免费

Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.

中文简介正在准备中。当前显示原文说明。

arcee-ai/nac2912026年10月26日 更新

triage

免费

Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage issues or invokes triage.

中文简介正在准备中。当前显示原文说明。

arcee-ai/nac2912026年10月26日 更新

查看 arcee-ai 的全部技能

报告此技能的问题