本文へ移動
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（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 のスキルをすべて見る

このスキルの問題を報告する