@atollhq/skill-claude 0.4.8 → 0.4.10

package/README.md

@@ -7,23 +7,25 @@ Gives your Claude Code agent the ability to manage tasks, goals, KPIs, initiativ
 ## Install
 
 ```bash
-npx @atollhq/skill-claude --profile agent-a --key sk_atoll_... --org your-org-id --project project-id --team team-id
+npx @atollhq/skill-claude@latest --profile agent-a --key sk_atoll_... --org your-org-id --project project-id --team team-id
 # or
-ATOLL_API_KEY=sk_atoll_... ATOLL_ORG_ID=your-org-id npx @atollhq/skill-claude
+ATOLL_API_KEY=sk_atoll_... ATOLL_ORG_ID=your-org-id npx @atollhq/skill-claude@latest
 ```
 
-Optional defaults: `--project`, `--team`, and `--base-url` are stored with the selected mode. Use `--no-project`, `--no-team`, or `--no-base-url` to clear previously saved defaults. Pass `--profile` to store credentials and defaults only in that named Atoll CLI profile; Claude settings keep only `ATOLL_PROFILE` so direct CLI commands can use the profile safely. Omit `--profile` to use env-var mode, which writes `ATOLL_ENV_MODE=1` with the credential settings.
+Optional defaults: `--project`, `--team`, and `--base-url` are stored with the selected mode. Use `--no-project`, `--no-team`, or `--no-base-url` to clear previously saved defaults. Pass `--profile` to store credentials and defaults only in that named Atoll CLI profile. The installer does not write a global `ATOLL_PROFILE` or `ATOLL_*` credential settings in profile mode, so direct CLI commands should use `atoll --profile agent-a ...`. Omit `--profile` to use env-var mode, which writes `ATOLL_ENV_MODE=1` with the credential settings.
 
 Get an agent API key from **Agents** in the Atoll app. Integration keys are still managed from **Settings > Members**.
 
 This does three things:
 
 1. Copies the skill into `~/.claude/skills/atoll-api/`
-2. Stores only `ATOLL_PROFILE` in `~/.claude/settings.json` when profile mode is used
+2. Removes stale Atoll credential/profile env from `~/.claude/settings.json` when profile mode is used
 3. Creates or updates the named Atoll CLI profile when `--profile` is provided
 
 Restart Claude Code and the `atoll-api` skill is available.
 
+Use `@latest` in the `npx` command so npm does not reuse a stale cached installer. In profile mode, the installer prints its package version and a verification command; run `atoll --profile agent-a agent-context --json` if you need to confirm the profile was created.
+
 ## Using the skill
 
 Once installed, ask Claude anything task-related:
@@ -45,9 +47,9 @@ For terminal-first work, see [`@atollhq/cli`](https://www.npmjs.com/package/@ato
 ```bash
 npm install -g @atollhq/cli
 atoll auth login --profile agent-a --key sk_atoll_... --org-id org-uuid --project project-id --team team-id
-atoll heartbeat
-atoll issue list --json
-atoll agent-context
+atoll --profile agent-a heartbeat
+atoll --profile agent-a issue list --json
+atoll --profile agent-a agent-context
 ```
 
 For multiple agents or orgs, use CLI auth profiles:

package/bin/install.mjs

@@ -6,6 +6,7 @@ import { homedir } from 'node:os'
 import { fileURLToPath } from 'node:url'
 
 const __dirname = dirname(fileURLToPath(import.meta.url))
+const packageJson = JSON.parse(readFileSync(join(__dirname, '..', 'package.json'), 'utf-8'))
 
 function parseArgs(argv) {
   const args = {}
@@ -37,8 +38,8 @@ function parseArgs(argv) {
 
 function printUsage() {
   console.log(`
-Usage: npx @atollhq/skill-claude [--profile <name>] --key <api-key> --org <org-id> [--project <id>] [--team <id-or-slug>] [--base-url <url>]
-   or: ATOLL_API_KEY=<api-key> ATOLL_ORG_ID=<org-id> npx @atollhq/skill-claude
+Usage: npx @atollhq/skill-claude@latest [--profile <name>] --key <api-key> --org <org-id> [--project <id>] [--team <id-or-slug>] [--base-url <url>]
+   or: ATOLL_API_KEY=<api-key> ATOLL_ORG_ID=<org-id> npx @atollhq/skill-claude@latest
 
 Options:
   --profile   Atoll CLI profile name to create/update.
@@ -72,6 +73,8 @@ if (args.help) {
   process.exit(0)
 }
 
+console.log(`Running @atollhq/skill-claude installer v${packageJson.version}`)
+
 if (!args.key || !args.org) {
   console.error('Error: provide --key and --org, or set ATOLL_API_KEY and ATOLL_ORG_ID\n')
   printUsage()
@@ -112,7 +115,6 @@ function writeAtollProfile() {
   else delete profile.defaultTeam
   if (args.baseUrl) profile.baseUrl = args.baseUrl
   else delete profile.baseUrl
-  config.activeProfile = args.profile
 
   mkdirSync(atollDir, { recursive: true })
   writeFileSync(configPath, JSON.stringify(config, null, 2) + '\n')
@@ -128,14 +130,14 @@ cpSync(skillSrc, skillDest, { recursive: true })
 console.log(`Installed skill to ${skillDest}`)
 
 // 2. Configure ~/.claude/settings.json. Profile mode stores credentials only
-// in the Atoll CLI profile and keeps Claude's host env limited to profile
-// selection, removing stale credential/default env from earlier installs.
+// in the Atoll CLI profile and removes stale credential/profile env from
+// earlier installs so a new profile install does not become globally active.
 const settingsPath = join(homedir(), '.claude', 'settings.json')
 let settings = readJson(settingsPath)
 
 if (!settings.env) settings.env = {}
 if (args.profile) {
-  settings.env.ATOLL_PROFILE = args.profile
+  delete settings.env.ATOLL_PROFILE
   delete settings.env.ATOLL_API_KEY
   delete settings.env.ATOLL_ORG_ID
   delete settings.env.ATOLL_PROJECT
@@ -160,14 +162,19 @@ writeAtollProfile()
 
 const configuredVars = []
 if (args.profile) {
-  configuredVars.push('ATOLL_PROFILE')
+  console.log(`Removed stale Atoll env from ${settingsPath}`)
 } else {
   configuredVars.push('ATOLL_API_KEY', 'ATOLL_ORG_ID', 'ATOLL_ENV_MODE')
   if (args.project) configuredVars.push('ATOLL_PROJECT')
   if (args.team) configuredVars.push('ATOLL_TEAM')
   if (args.baseUrl) configuredVars.push('ATOLL_BASE_URL')
+  console.log(`Configured ${configuredVars.join(', ')} in ${settingsPath}`)
+}
+if (args.profile) {
+  console.log('No global Claude ATOLL_PROFILE was written.')
+  console.log(`Run profile-scoped commands with: atoll --profile ${args.profile} ...`)
+  console.log(`Verify the profile with: atoll --profile ${args.profile} agent-context --json`)
 }
-console.log(`Configured ${configuredVars.join(', ')} in ${settingsPath}`)
 
 console.log(`\nDone! Start Claude Code and the atoll-api skill will be available.`)
 console.log(`Try: "List my Atoll tasks" or "Check my heartbeat"`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atollhq/skill-claude",
-  "version": "0.4.8",
+  "version": "0.4.10",
   "description": "Install the Atoll project management skill for Claude Code",
   "bin": {
     "skill-claude": "bin/install.mjs"

package/skill/SKILL.md

@@ -186,7 +186,7 @@ CLI JSON conventions:
 
 When a human asks you to help automate a KPI from a third-party API, use this Atoll skill. If the current agent environment does not have the `atoll-api` skill installed, tell the user to install it before continuing or use the Atoll CLI/MCP tools directly if they are available.
 
-Agents may create draft syncs and validate proposed configs only after a human admin has allowlisted the exact destination host in Atoll. Human admins must review the draft in Atoll, enter secrets, dry-run, publish, disable, or run-now with snapshot writing.
+Agents may create draft syncs and validate proposed configs only after a human admin has allowlisted the exact destination host in Atoll. Human admins must create or review the draft in Settings > Integrations > KPI syncs, edit supported request/extraction fields and secrets through structured UI, dry-run, publish, disable, or run-now with snapshot writing.
 
 ```bash
 atoll kpi sync validate <kpi-id> \

package/skill/references/api-endpoints.md

@@ -203,6 +203,7 @@ Roles: `owner`, `admin`, `member`, `guest`.
 | POST | `/api/orgs/{id}/kpis/{kpiId}/snapshots` | Record a snapshot |
 | GET | `/api/orgs/{id}/kpi-http-sync-policy` | List exact-host KPI HTTP sync allowlist policy |
 | POST | `/api/orgs/{id}/kpi-http-sync-policy` | Add an allowed exact host (human admin only) |
+| GET | `/api/orgs/{id}/kpi-http-syncs` | List org-wide KPI HTTP sync review rows for Settings; admins get config/secret metadata, members get redacted status rows |
 | GET | `/api/orgs/{id}/kpis/{kpiId}/http-syncs` | List KPI HTTP syncs |
 | POST | `/api/orgs/{id}/kpis/{kpiId}/http-syncs` | Create a draft KPI HTTP sync |
 | PUT | `/api/orgs/{id}/kpis/{kpiId}/http-syncs` | Validate a proposed KPI HTTP sync config without storing or running it |
@@ -429,7 +430,7 @@ URL must be an HTTPS DNS hostname. IP literals, `localhost`, and `.local` hosts
 |--------|----------|-------------|
 | GET | `/api/orgs/{id}/agents` | List agents (owner/admin) |
 | GET | `/api/orgs/{id}/agents/manageable` | List agents the current human can manage |
-| POST | `/api/orgs/{id}/agents` | Create org, project-scoped, or personal agent |
+| POST | `/api/orgs/{id}/agents` | Create org agent (`{ name, role?, setupScoped? }`), project-scoped agent (`{ name, projectIds }` or legacy `{ name, projectId, projectIds? }`), or personal agent (`{ name, personal: true }`) |
 | DELETE | `/api/orgs/{id}/agents/{agentId}` | Revoke manageable agent |
 | PATCH | `/api/orgs/{id}/agents/{agentId}/projects` | Replace project access for a manageable non-personal agent |
 | POST | `/api/orgs/{id}/projects/{projectId}/agents` | Grant selected manageable agents access to a project |

package/skill/references/api-fields.md

@@ -15,6 +15,7 @@
 - [Heartbeat Response](#heartbeat-response)
 - [Analytics Response](#analytics-response)
 - [Plan Limit Errors](#plan-limit-errors)
+- [Agent Fields](#agent-fields)
 - [Enums](#enums)
 
 ---
@@ -73,6 +74,10 @@ Creation endpoints may return `402` when an org reaches its billing plan limit:
 
 `resource` is one of `humans`, `agents`, `activeProjects`, or `activeIssues`.
 
+## Agent Fields
+
+Create org-wide agents with `{ "name": "...", "role": "member", "setupScoped": false }`; org-wide creation is owner/admin-only. Create project-scoped agents with non-empty `projectIds`, for example `{ "name": "...", "projectIds": ["project-uuid"] }`; `projectId` remains accepted as a legacy/default-project alias and is merged with `projectIds`. Project-scoped agents are created as guests, and human members may only scope them to projects they can access. Create personal agents with `{ "name": "...", "personal": true }`; personal agents inherit their human owner's project access and reject explicit `projectId`/`projectIds`.
+
 ## Goal Fields
 
 ```json