What makes Operately CLI notable?

1.3K downloads. Trust evidence available

How should Operately CLI be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Operately CLI

Skills for working with Operately, the open source system for running goals and projects. Manage Operately from the CLI: goals, OKRs, projects, tasks, milestones, spaces, documents, discussions, check-ins, reviews, assignments, people, permissions, and documents.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

1.9.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 1.9.0release · observed Sep 21, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17ajffj868ejjyf86vawgyk5n84cg00:operately-cli

Install using `clawhub skill install s17ajffj868ejjyf86vawgyk5n84cg00:operately-cli` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/markoa/operately-cli before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-markoa-operately-cli/snapshot"

Documentation

CLAWHUB

145,181 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: operately-cli
description: >
  Manage Operately from the CLI: goals, OKRs, projects, project templates,
  tasks, milestones, spaces, documents, discussions, check-ins, reviews,
  assignments, people, permissions, full-text search, document history, and
  Docs & Files. Use when operating an Operately workspace, automating
  startup/company operations, updating project status, tracking goal progress,
  managing async execution, or working with the open source company operating
  system.
version: 1.9.0
metadata:
  openclaw:
    requires:
      bins:
        - operately
    env:
      - name: OPERATELY_API_TOKEN
        description: API token for environment-based Operately CLI authentication.
        required: false
        sensitive: true
      - name: OPERATELY_BASE_URL
        description: Optional Operately API base URL for self-hosted, staging, or local instances.
        required: false
        sensitive: false
      - name: OPERATELY_PROFILE
        description: Optional saved Operately CLI profile name to use.
        required: false
        sensitive: false
    primaryEnv: OPERATELY_API_TOKEN
    emoji: "📋"
    homepage: https://github.com/operately/skills
    install:
      - kind: node
        package: "@operately/operately-cli"
        bins:
          - operately
---

# Operately CLI

Operate an Operately instance through the `operately` CLI.

## Quick Reference

| Task | Command |
| --- | --- |
| Install CLI | `npm install -g @operately/operately-cli` |
| Login | `operately auth login --token <token>` |
| Interactive login | `operately auth login` |
| Login with flags | `operately auth login --method email-password --email [email protected] --password secret123456 --company-id <company-id> --access-mode full-access --profile work` |
| Sign up | `operately auth signup` |
| Sign up with flags | `operately auth signup --method email-password --full-name "New User" --email [email protected] --password secret123456 --next-step later` |
| Join Company | `operately auth join` |
| Join Company with flags | `operately auth join --invite-token <token> --method email-password --email [email protected] --password secret123456` |
| Create company | `operately auth create-company` |
| Create company with flags | `operately auth create-company --method email-password --email [email protected] --password secret123456 --company-name "Acme Corp" --profile work` |
| List saved profiles | `operately auth profiles` |
| Auth status (local config) | `operately auth status` |
| Who am I | `operately auth whoami` |
| Logout | `operately auth logout` |
| Set profile picture | `operately people update_picture --avatar-file ./avatar.png` |
| Remove profile picture | `operately people update_picture --clear` |
| Upload file to Docs & Files | `operately documents create_file --space-id <id> --file ./report.pdf` |
| List my assignments | `operately people list_assignments` |
| List projects | `operately projects list` |
| Get project | `operately projects g

_meta.json

{
  "ownerId": "kn7cy7etbrc1nyrcaqw799h4p584c6qm",
  "slug": "operately-cli",
  "version": "1.9.0",
  "publishedAt": 1789991289772
}

references/assignments-and-reviews.md

# Assignments and Reviews

Get items that need your attention or review using the Operately CLI.

## Overview

The `people list_assignments` command retrieves all assignments and items requiring your attention, organized into three categories based on urgency and your role.

## Basic Usage

```bash
operately people list_assignments
```

This returns all items assigned to you or requiring your review, with no additional parameters needed.

## Response Structure

The command returns assignments categorized into three groups:

### 1. `due_soon`
Items you own that require immediate attention:
- **Overdue** - Past their due date
- **Due today** - Due on the current date
- **Due soon** - Due within the next few days

### 2. `needs_review`
Items where you are the reviewer and need to provide acknowledgment:
- Project check-ins awaiting review
- Goal updates requiring acknowledgment
- Project and goal retrospectives awaiting acknowledgment
- Milestone completions needing approval

### 3. `upcoming`
Items you own with future due dates:
- Tasks and milestones with upcoming deadlines
- Items without due dates

## Assignment Types

Each assignment includes:

- **`type`** - The kind of item:
  - `project_check_in` - Project status update
  - `goal_check_in` - Goal progress update
  - `project_retrospective` - Closed project retrospective awaiting review
  - `goal_retrospective` - Closed goal retrospective awaiting review
  - `milestone` - Project milestone
  - `project_task` - Task within a project
  - `space_task` - Task within a space
  - `goal` - Goal itself
  - `project` - Project requiring review

- **`role`** - Your relationship to the item:
  - `owner` - You are responsible for completing it
  - `reviewer` - You need to review/acknowledge it

- **`origin`** - The parent resource (project, goal, or space) containing this assignment

- **`due_date`** - When the item is due (may be null)

- **`due_status`** - Urgency level: `overdue`, `due_today`, `due_soon`, `upcoming`, or `none`

- **`task_status`** - Current state (for tasks): `pending`, `in_progress`, `done`, etc.

## Grouping

Assignments are grouped by their origin (parent project, goal, or space), making it easy to see all related items together. Within each group, assignments are sorted by urgency, with the most critical items first.

## Example Output Structure

```json
{
  "data": {
    "due_soon": [
      {
        "origin": {
          "id": "project-123",
          "name": "Q2 Roadmap",
          "type": "project",
          "path": "/space/projects/q2-roadmap",
          "space_name": "Engineering"
        },
        "assignments": [
          {
            "name": "Complete API design",
            "type": "milestone",
            "role": "owner",
            "due_date": "2026-04-15",
            "due_status": "overdue",
            "due_status_label": "Overdue by 2 days"
          }
        ]
      }
    ],
    "needs_review": [
      {
        "origin": {
          "id": "goal-456",

references/auth-flows.md

# Auth Flows

Use this reference when the task involves `operately auth ...`, saved profiles, invite-based onboarding, or explaining how CLI authentication works.

This document is about the handcrafted auth commands in `cli/src/auth/`. Most other CLI commands are generated from backend `external_endpoints`; the auth flows are not.

## Contents

- When to use each auth command
- Shared auth behavior
- Login flows
- Signup flows
- Create-company flows
- Join flows
- Profile and verification commands
- Backend/internal endpoint map
- Agent rules

## When To Use Each Auth Command

Use these commands based on the task:

- `operately auth login --token <token>`: best for automation, CI, scripted work, or any headless task where the user already has a token.
- `operately auth login`: hybrid login for password, email code, or Google OAuth, plus prompted token entry when the user chooses it interactively.
- `operately auth signup`: hybrid account creation that can be fully interactive or mostly flag-driven, followed by create-company, join-with-invite, or stop-for-now.
- `operately auth create-company`: authenticate first, create a company, and save a full-access profile for an account that does not have one yet.
- `operately auth join`: interactive invite-based onboarding for an existing or newly activated account.
- `operately auth profiles`: inspect saved local CLI profiles and see which one is active.
- `operately auth whoami`: remote validation that the current token still works.
- `operately auth status`: local config check only.
- `operately auth logout`: remove the saved token from the selected profile.

## Shared Auth Behavior

### Base URL and profiles

- If no `--base-url` is provided, the CLI defaults to `https://app.operately.com`.
- If no `--profile` is provided for interactive auth, the CLI prompts for one with the current active profile (falling back to `default`) as the default; blank input accepts that default.
- For ordinary endpoint execution, auth resolution priority is: per-command flags > environment variables > saved profile.

### Saved profile result

Most successful auth flows end by saving:

- the final API token
- the base URL
- the resolved person name
- the company name

The profile metadata is fetched with external API calls after authentication succeeds.

### Important distinction: local vs remote checks

- `operately auth profiles` does not call the server. It prints saved local profiles, active-profile state, and saved metadata/base URLs.
- `operately auth status` does not call the server. It prints local profile/config state.
- `operately auth whoami` calls the API and is the correct post-login verification step.

### Bootstrap token model

Interactive login, signup, and join usually work in two phases:

1. The CLI gets a short-lived bootstrap token from an internal auth endpoint.
2. The CLI exchanges that bootstrap token for a reusable API token with `cli_auth/create_token`.

That final API token is company-scoped beca

references/collaboration-patterns.md

# Collaboration Patterns

Team collaboration workflows in Operately, covering spaces, members, permissions, discussions, comments, reactions, and notifications.

## Space Management

### Creating Spaces

```bash
operately spaces create \
  --name "Engineering" \
  --mission "Build great products" \
  --company-permissions 10 \
  --public-permissions 0
```

### Getting Space Details

```bash
operately spaces get --id s1
```

### Listing Spaces

```bash
operately spaces list
```

### Searching Spaces

```bash
operately spaces search --query "engineering"
```

### Updating Spaces

```bash
operately spaces update \
  --id s1 \
  --name "Engineering & Product" \
  --mission "Build and ship great products"
```

### Deleting Spaces

```bash
operately spaces delete --space-id s1
```

## Member Management

### Adding Members

```bash
# Add single member
operately spaces add_members \
  --space-id s1 \
  --members.0.id u1 \
  --members.0.access-level 70

# Add multiple members
operately spaces add_members \
  --space-id s1 \
  --members.0.id u1 \
  --members.0.access-level 70 \
  --members.1.id u2 \
  --members.1.access-level 40 \
  --members.2.id u3 \
  --members.2.access-level 40
```

### Listing Members

```bash
operately spaces list_members --space-id s1
```

### Searching for Members

```bash
operately spaces search_potential_members \
  --space-id s1 \
  --query "engineer"
```

### Removing Members

```bash
operately spaces delete_member \
  --space-id s1 \
  --member-id u1
```

### Joining Spaces

```bash
# User joins a space
operately spaces join --space-id s1
```

## Permissions and Access Levels

### Member Permissions

```bash
operately spaces update_members_permissions \
  --space-id s1 \
  --members.0.id u1 \
  --members.0.access-level 70 \
  --members.1.id u2 \
  --members.1.access-level 70
```

Access levels:
- `0` - No access
- `10` - View only
- `40` - Comment
- `70` - Edit
- `100` - Full access (admin)

### Space Permissions

```bash
operately spaces update_permissions \
  --space-id s1 \
  --access-levels.public 0 \
  --access-levels.company 10 \
  --access-levels.space 70
```

## Space Tools

### Listing Available Tools

```bash
operately spaces list_tools --space-id s1
```

### Enabling/Disabling Tools

```bash
operately spaces update_tools \
  --space-id s1 \
  --tools.tasks-enabled true \
  --tools.discussions-enabled true \
  --tools.resource-hub-enabled true
```

Common tool types:
- `projects` - Project management
- `goals` - Goal tracking
- `resource_hub` - Knowledge base
- `discussions` - Team discussions
- `tasks` - Task management

## Discussions

### Space Discussions

**Create discussion:**
```bash
operately spaces create_discussion \
  --space-id s1 \
  --title "Q2 Planning Discussion" \
  --body "# Q2 Planning\n\nLet's discuss our priorities for Q2.\n\n## Topics\n- Revenue goals\n- Product roadmap\n- Team growth"

operately spaces create_discussion \
  --space-id s1 \
  --title "Q2 Planning Discussion" \
  --body-file ./q2

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.