mcpField
C
cli

cli

github.com/loops-soMarketing & growth12122 installsUpdated 3d ago
Repository

About cli

Loops CLI Skill guides terminal-based use of the Loops CLI for installation, authentication, configuration, and operational commands. It focuses on shell workflows rather than application integrations or email strategy.

Key features

  1. 01Guide CLI installation and updates
  2. 02Explain authentication and team keys
  3. 03Select commands for contacts, lists, and events
  4. 04Inspect text or JSON output
  5. 05Handle credentials safely

Use cases

  1. 01Troubleshooting Loops CLI authentication
  2. 02Running a one-off contact or event command
  3. 03Using JSON output in a script
  4. 04Switching between Loops teams

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/loops-so/skills --skill cli

After installing, type/cliin Claude Code to confirm it loaded.

Bundled filesreferences/cli.md

Details

From the project README

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:

  1. Prefer loops --help and command-specific help output for exact flags and the latest command shape.
  2. Prefer the CLI for shell workflows, one-off operational tasks, credential validation, and quick troubleshooting.
  3. Use --output json when the result needs to feed another tool or script.
  4. Use named stored keys plus --team when the user works across multiple Loops teams.
  5. Avoid printing secrets. Prefer keyring-backed auth or environment variables over hardcoded API keys.
  6. If the task becomes application-code integration or exact HTTP payload design, use the separate api skill.

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, or loops api-key

Comments

Markdown supported