akili community

Manage community contributions on the Akili platform. Contributions are shared artifacts (connectors, transforms, templates) that teams can publish to the tenant-wide community registry for reuse across data products.

Commands

akili community list

List all community contributions visible to the current tenant.

Flags:

Flag	Short	Default	Description
--mine		false	Show only contributions you authored

Examples:

# List all contributions
akili community list

# List only your contributions
akili community list --mine

# List as JSON
akili community list --json

---

akili community get <id>

Show detailed information about a specific contribution including metadata, status, author, and timestamps.

Arguments:

Argument	Type	Required	Description
id	string	yes	Contribution ID

Examples:

# Show contribution details
akili community get contrib-abc123

# Show as JSON
akili community get contrib-abc123 --json

---

akili community create

Create a new community contribution. The contribution starts in draft status and must be submitted for review before it can be approved and published.

Flags:

Flag	Short	Default	Description
--artifact-type			Artifact type: connector, transform, or template (required)
--name			Contribution name (required)
--description			Description of the contribution (required)
--version		0.1.0	Semantic version string

Examples:

# Create a connector contribution
akili community create \
  --artifact-type connector \
  --name pg-cdc \
  --description "PostgreSQL CDC connector with WAL-level replication"

# Create a transform template
akili community create \
  --artifact-type template \
  --name scd-type-2 \
  --description "Slowly changing dimension type 2 transform" \
  --version 1.0.0

---

akili community submit <id>

Submit a draft contribution for review. Moves the contribution from draft to pending_review status.

Arguments:

Argument	Type	Required	Description
id	string	yes	Contribution ID

Examples:

# Submit for review
akili community submit contrib-abc123

---

akili community approve <id>

Approve a contribution that is pending review. Requires reviewer permissions. Moves the contribution to approved status.

Arguments:

Argument	Type	Required	Description
id	string	yes	Contribution ID

Examples:

# Approve a contribution
akili community approve contrib-abc123

---

akili community reject <id>

Reject a contribution that is pending review. Requires a reason. Moves the contribution back to draft status.

Arguments:

Argument	Type	Required	Description
id	string	yes	Contribution ID

Flags:

Flag	Short	Default	Description
--reason			Reason for rejection (required)

Examples:

# Reject with a reason
akili community reject contrib-abc123 --reason "Missing tests and documentation"

---

akili community publish <id>

Publish an approved contribution to the community registry, making it available for use by all teams in the tenant.

Arguments:

Argument	Type	Required	Description
id	string	yes	Contribution ID

Examples:

# Publish to the registry
akili community publish contrib-abc123

---

Contribution Lifecycle

Contributions follow a linear review workflow:

draft --> pending_review --> approved --> published
                 |
                 +--> draft (rejected, fix and resubmit)

Status	Who Can Transition	Next State
draft	Author	pending_review (via submit)
pending_review	Reviewer	approved (via approve) or draft (via reject)
approved	Author	published (via publish)

Global Flags

All akili community commands support these global flags:

Flag	Short	Default	Description
--json		false	Output as JSON instead of tables
--profile		default	Config profile to use
--api-url		from config	API base URL override
--timeout		30	Request timeout in seconds