# ClickUp Operator Public Packaging

Use this when the goal is to make the package legible and valuable to someone outside Sam's workspace.

## Product promise

ClickUp Operator is a reusable skill that teaches an agent how to:

- capture ideas without over-structuring them
- route action items into the right operational lane
- apply sane assignment and due-date defaults
- read back today's work cleanly
- avoid annoying confirmation loops when the correct action is obvious

## What this is not

- not a universal ClickUp autopilot with zero setup
- not a replacement for ClickUp auth or account wiring
- not magic project architecture
- not bundled with one person's private workspace IDs or member IDs

## Public package shape

The public-facing version should feel like:

1. clear promise
2. clear setup boundary
3. example prompts
4. example config
5. realistic expectations about what still needs user-specific wiring

## Messaging angle

Best current framing:

- "operator-style ClickUp handling"
- "clean defaults for ideas, to-dos, and project routing"
- "less back-and-forth, more direct execution"

Avoid weaker framing like:

- "AI productivity magic"
- "fully autonomous project manager"
- anything that hides the setup/config requirement

## Public-release bar

Before calling the public version ready:

- the description explains the real value in plain English
- the setup burden is visible, not hidden
- the examples feel like real user prompts
- the package contains no private workspace data
- the first-run experience is understandable without insider context