Loops CLI Skill
This skill helps with Loops terminal workflows. Use it for installation, auth and configuration, command selection, and shell-first operational tasks.
When To Use
Use this skill when the user needs to:
- install, update, or troubleshoot the Loops CLI
- authenticate with Loops from the terminal
- manage stored team keys or switch between them
- run one-off contact, list, event, or transactional-email commands
- inspect CLI output in text or JSON locally
This skill is for command-line usage, not application integrations or email-strategy review.
Working Style
When this skill is active:
- Prefer
loops --helpand command-specific help output for exact flags and the latest command shape. - Prefer the CLI for shell workflows, one-off operational tasks, credential validation, and quick troubleshooting.
- Use
--output jsonwhen the result needs to feed another tool or script. - Use named stored keys plus
--teamwhen the user works across multiple Loops teams. - Avoid printing secrets. Prefer keyring-backed auth or environment variables over hardcoded API keys.
- If the task becomes application-code integration or exact HTTP payload design, use the separate
apiskill.
Official references:
- CLI repo:
https://github.com/Loops-so/cli - CLI README:
https://github.com/Loops-so/cli/blob/main/README.md
Category Routing
- Installation, auth flows, config resolution, global flags, and common Loops CLI workflows: Read
references/cli.md
Output Checklist
Aim to leave the user with:
- the right command or install path for the task
- any auth or team-selection caveats that affect behavior
- safe handling of credentials
- the next validation step, such as
loops --help,loops auth status, orloops api-key