@atollhq/skill-claude

Install the Atoll project management skill for Claude Code.

Gives your Claude Code agent the ability to manage tasks, goals, KPIs, initiatives, milestones, comments, and webhooks on Atoll — the same API surface a human teammate uses.

Install

Install or refresh the local skill files without configuring credentials:

npx --yes @atollhq/skill-claude@latest

Bare invocation and --install-only only update ~/.claude/skills/atoll/. They do not inspect or change Atoll credentials, profiles, shell files, or Claude settings, even when ATOLL_* variables are present.

Configure a named profile explicitly:

npx --yes @atollhq/skill-claude@latest --profile agent-a --key sk_atoll_... --org org-uuid --project project-id --team team-id

For intentional environment configuration, use --configure:

ATOLL_API_KEY=sk_atoll_... ATOLL_ORG_ID=org-uuid npx --yes @atollhq/skill-claude@latest --configure

Configuration mode supports --project, --team, and --base-url. Use --no-project, --no-team, or --no-base-url to clear 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 setting in profile mode, so direct CLI commands should use atoll --profile agent-a ....

Get an agent API key from Agents in the Atoll app. Integration keys are managed from Settings > Integrations.

Every invocation copies the skill. Configuration mode additionally:

1. Copies the skill into ~/.claude/skills/atoll/
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 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.

The installer writes credential-bearing files atomically, refuses symbolic-link targets, uses 0600 for credential files, and uses 0700 for dedicated credential directories. Concurrent installer runs are serialized so profile and settings updates are not lost.

Using the skill

Once installed, ask Claude anything task-related:

"List my Atoll tasks"
"Create an issue to fix the login bug, priority 1"
"What goals are off pace?"
"Check my Atoll heartbeat"
"Move ATOLL-42 to in_progress"

The skill also documents how to talk to the Atoll API directly via curl, in case your agent needs to.

Companion CLI

For terminal-first work, see @atollhq/cli:

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 --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:

atoll auth login --profile agent-a --key sk_atoll_... --org-id org-uuid
atoll auth login --profile agent-b --key sk_atoll_... --org-id org-uuid --project project-id --team team-id
atoll --profile agent-b issue list

Always persist --org-id on named profiles, or pass --org-id per command. Resource commands fail when the selected profile has no org ID so agents do not accidentally operate with the wrong scope.

The companion CLI also supports safer issue removal and upstream feedback with local retry drafts:

atoll issue archive ATOLL-42
atoll issue delete ATOLL-42 --dry-run
atoll feedback "The heartbeat output should include blocked issue details"

License

MIT