Agent Skills
› openinary/openinary
› loops-cli
loops-cli
GitHub提供 Loops CLI 的终端工作流支持，涵盖安装、认证、配置管理及各类营销命令执行。适用于在 Shell 中进行一次性操作、凭证验证及快速故障排查，不涉及应用代码集成。
Trigger Scenarios
Loops CLI
loops auth login
loops campaigns create
loops uploads create
loops email-messages update
loops themes list
loops components get
loops contacts create
loops events send
loops transactional send
loops api-key
loops agent-context
brew install loops-so/tap/loops
Install
npx skills add openinary/openinary --skill loops-cli -g -y
SKILL.md
Frontmatter
{
"name": "loops-cli",
"metadata": {
"version": "1.1.1"
},
"description": "Use this skill whenever the user wants to work with the Loops CLI from the terminal. This includes installing or updating the CLI, authenticating, storing and selecting API keys, validating credentials, and running commands for contacts, contact properties, lists, events, transactional email, campaigns, email messages, themes, components, and uploads. Trigger on phrases like \"Loops CLI\", \"loops auth login\", \"loops campaigns create\", \"loops uploads create\", \"loops email-messages update\", \"loops themes list\", \"loops components get\", \"loops contacts create\", \"loops events send\", \"loops transactional send\", \"loops api-key\", \"loops agent-context\", \"brew install loops-so\/tap\/loops\", or any time the user wants to use Loops from the shell instead of application code.\n"
}
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
- create draft campaigns, update email-message content, and upload images from the shell
- list/get themes and reusable components for LMX
- 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 agent-contextfor 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
loops-apiskill.
Official references:
- CLI docs:
https://loops.so/docs/cli - 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 - Campaigns, email messages, themes, components, revision handling, LMX file flags, and uploads:
Read
references/cli.md. For LMX markup itself, also use theloops-lmxskill.
If the task becomes application-code integration or exact HTTP payload design beyond the CLI, use the loops-api skill.
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,loops api-key, orloops agent-context
Version History
- fdcff9e Current 2026-08-20 09:59
