SeggWat CLI

Use the SeggWat CLI to manage feedback, projects, and ratings from the terminal. Trigger this skill whenever the user wants to collect, triage, query, or aut...

Security Scan

The skill's instructions, required data, and behaviors are coherent with a CLI for managing SeggWat feedback; nothing requests unrelated credentials or system access, though it recommends installing a remote shell installer which you should review before running.

Purpose & Capability

The SKILL.md describes a CLI for managing feedback, projects, and ratings and all commands, auth methods, and config paths align with that purpose. Minor metadata mismatch: the registry lists no homepage but the docs reference https://seggwat.com — this is consistent with the tool but the registry metadata could be incomplete.

Instruction Scope

Runtime instructions stay within the stated domain: installing the CLI, authenticating (API key or OAuth), running CRUD and stats commands, and caching tokens at ~/.config/seggwat/tokens.json. The doc references use of SEGGWAT_API_KEY and SEGGWAT_API_URL as optional flags/env vars; it does not instruct the agent to access unrelated files or secrets.

Install Mechanism

The skill is instruction-only (no install spec) but recommends installing via 'cargo install' or a remote shell installer hosted at https://seggwat.com/static/install.sh. Fetching and running a remote install script is a common convenience but carries higher risk than a reviewed package—verify the script and prefer pinned releases or installing from a trusted package source.

Credentials

The only environment variables mentioned are SEGGWAT_API_KEY and SEGGWAT_API_URL (and token caching path). Those are appropriate and proportionate for a CLI that authenticates to a feedback service. The registry lists no required env vars; the SKILL.md uses them as optional/authenticated usage, which is reasonable.

Persistence & Privilege

No elevated privileges requested. The skill does not set always:true, does not request system-wide config changes, and only references storing tokens under the user's config directory (~/.config/seggwat), which is typical for a CLI.

Assessment

This skill appears coherent for a SeggWat CLI: it documents installation, API key auth, and commands for feedback and ratings. Before installing or running the provided installer script: inspect https://seggwat.com/static/install.sh (avoid piping unknown scripts directly into a shell), prefer installing via cargo or a pinned release if possible, and only provide a scoped API key for CI (use least privilege). Note the registry metadata omits a homepage but the SKILL.md references seggwat.com — verify you trust that domain. If you use CI, store SEGGWAT_API_KEY in your pipeline secrets and rotate/revoke tokens when no longer needed.

The SeggWat CLI (seggwat) lets you manage feedback, projects, and ratings for the SeggWat feedback platform directly from the terminal.

Installation

cargo install seggwat-cli

A shell-based installer is also available at https://seggwat.com/static/install.sh (supports pinning a version via VERSION=v0.17.2).

Verify: seggwat --version

Authentication

Two methods are available. Use API key for scripts/CI, OAuth for interactive use.

API Key (non-interactive, recommended for automation)

# Environment variable
export SEGGWAT_API_KEY=oat_<your-token>

# Or inline flag
seggwat --api-key oat_<your-token> project list

API keys use the oat_ prefix (Organization Access Token) and are created in the SeggWat Dashboard under Settings > API Tokens.

OAuth Login (interactive)

seggwat login          # Opens browser, caches tokens at ~/.config/seggwat/tokens.json
seggwat whoami         # Show current user
seggwat logout         # Clear cached tokens

For self-hosted instances, pass --api-url, --zitadel-domain, and --client-id to point at your own deployment.

Global Options

Flag	Env Variable	Description
--api-url <url>	SEGGWAT_API_URL	API base URL (default: https://seggwat.com)
--api-key <key>	SEGGWAT_API_KEY	API key for authentication
--json	—	Output as JSON instead of tables
-v, --verbose	—	Enable debug logging

Commands Reference

Projects

seggwat project list                    # List all projects (alias: p ls)
seggwat project get <id>                # Get project details
seggwat project summary <id>            # Project overview with feedback & rating stats

Feedback

CRUD operations:

# List (with optional filters and pagination)
seggwat feedback list <project-id> [--status <status>] [--type <type>] [--search <text>] [--page N] [--limit N]

# Get single item
seggwat feedback get <project-id> <feedback-id>

# Create
seggwat feedback create <project-id> --message "text" [--type bug|feature|praise|question|improvement|other] [--path /page] [--version 1.0.0]

# Update
seggwat feedback update <project-id> <feedback-id> [--message "text"] [--type <type>] [--status <status>] [--resolution-note "text"]

# Delete (archive)
seggwat feedback delete <project-id> <feedback-id>

# Statistics
seggwat feedback stats <project-id>

Feedback statuses: new, active, assigned, hold, closed, resolved

Feedback types: bug, feature, praise, question, improvement, other

Aliases: feedback → fb, list → ls, delete → rm

Ratings

# List (with optional filters)
seggwat rating list <project-id> [--type helpful|star|nps] [--path /page] [--page N] [--limit N]

# Get single rating
seggwat rating get <project-id> <rating-id>

# Delete (archive)
seggwat rating delete <project-id> <rating-id>

# Statistics (type defaults to helpful)
seggwat rating stats <project-id> --type helpful   # Thumbs up/down percentage
seggwat rating stats <project-id> --type star      # Star distribution & average
seggwat rating stats <project-id> --type nps       # NPS score, promoters/passives/detractors

Rating types:

• helpful — binary thumbs up/down (value: true/false)
• star — 1-5 star rating (value + max_stars)
• nps — Net Promoter Score 0-10 (promoters 9-10, passives 7-8, detractors 0-6)

Aliases: rating → r, list → ls, delete → rm

Shell Completions

seggwat completions bash > ~/.local/share/bash-completion/completions/seggwat
seggwat completions zsh > ~/.zfunc/_seggwat
seggwat completions fish > ~/.config/fish/completions/seggwat.fish

JSON Output & Scripting

Add --json to any command for machine-readable output, useful for piping to jq or other tools:

# List project IDs
seggwat project list --json | jq -r '.projects[].id'

# Count open bugs
seggwat feedback list PROJECT_ID --type bug --status new --json | jq '.feedback | length'

# Export all feedback
seggwat feedback list PROJECT_ID --limit 100 --json > feedback.json

# Get NPS score
seggwat rating stats PROJECT_ID --type nps --json | jq '.score'

# Find feedback containing a keyword
seggwat feedback list PROJECT_ID --search "login" --json | jq '.feedback[].message'

Common Workflows

Triage new feedback

# See what's new
seggwat feedback list PROJECT_ID --status new

# Review and update status
seggwat feedback update PROJECT_ID FEEDBACK_ID --status active
seggwat feedback update PROJECT_ID FEEDBACK_ID --status resolved --resolution-note "Fixed in v2.1"

Monitor rating health

# Quick health check
seggwat rating stats PROJECT_ID --type helpful
seggwat rating stats PROJECT_ID --type nps

# Check specific page performance
seggwat rating list PROJECT_ID --type star --path "/pricing"

CI/CD integration

# In your pipeline, create feedback from test results
export SEGGWAT_API_KEY=oat_<your-token>
seggwat feedback create PROJECT_ID \
  --message "E2E test failure: checkout flow" \
  --type bug \
  --version "$(git describe --tags)"