Stripe Projects
fossasia/eventyay
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
A skill your agent uses whenever the user wants to work with the Loops CLI from the terminal.
Install Loops CLI
$ npx skills add openinary/openinary --skill loops-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openinary/openinary loops-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/loops-cli .claude/skills/loops-cli && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .claude/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openinary/openinary --skill loops-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openinary/openinary loops-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/loops-cli .agents/skills/loops-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .agents/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openinary/openinary --skill loops-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openinary/openinary loops-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/loops-cli .cursor/skills/loops-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .cursor/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openinary/openinary.git --path .agents/skills/loops-cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openinary/openinary --skill loops-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openinary/openinary loops-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/loops-cli .gemini/skills/loops-cli && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .gemini/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openinary/openinary loops-cliInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openinary/openinary --skill loops-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/loops-cli .github/skills/loops-cli && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .github/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openinary/openinary --skill loops-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openinary/openinary loops-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/loops-cli .opencode/skills/loops-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "loops-cli" agent skill from https://github.com/openinary/openinary/tree/main/.agents/skills/loops-cli into .opencode/skills/loops-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "loops-cli", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
loops-cli- GitHub stars
- 412
- Token cost
- ~782 tokens
- SKILL.md length
- 309 words
- Files
- 2 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
A skill your agent uses whenever the user wants to work with the Loops CLI from the terminal.
- Works in 6 steps: Prefer loops agent-context for exact… → Prefer the CLI for shell workflows,… → Use --output json when the result needs… → …
- The user wants to work with the Loops CLI from the terminal
- SKILL.md covers When To Use, Working Style, Category Routing and Output Checklist
- Reaches github.com and loops.so
What it does
Loops CLI is an agent skill from openinary/openinary. 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"…
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/cli.md`).
It sits in Backend & APIs, covering Transactional email and Codebase knowledge for agents. It works with Homebrew. The repository describes itself as: The self-hostable alternative to Cloudinary. The licence is AGPL-3.0.
When your agent uses it
- The user wants to work with the Loops CLI from the terminal
- Phrases like Loops CLI
- Loops auth login
- Loops campaigns create
Example prompts
- “Loops CLI”
- “loops auth login”
- “loops campaigns create”
- “/loops-cli”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Prefer loops agent-context 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 json when the result needs to feed another tool or script.
- Use named stored keys plus --team when 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-api skill.
What it can do on your machine
Read from SKILL.md and the folder at commit 1f05325. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.comloops.so
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Loops CLI loads about 782 tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 195 tokens; SKILL.md has 309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from openinary/openinary at commit 1f05325, republished under its AGPL-3.0 licence (© openinary). 309 words, ~782 tokens.
Download SKILL.mdSave it as
.claude/skills/loops-cli/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- loops-cli
- 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.
- metadata.version
- 1.1.1
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
© openinary, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .agents/skills/loops-cli of openinary/openinary.
- SKILL.md
- references/cli.md
Open the folder on GitHubat commit 1f05325
Compare with similar skills
Loops CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Loops CLI this skillopeninary/openinary | 412 | — | ~782 | Automated safety check: Pass | AGPL-3.0 | |
| Stripe Projectsfossasia/eventyay | 1.7k | 5 repos | ~2k | Automated safety check: Notes | Apache-2.0 | |
| WooCommerce Email Editor Developmentwoocommerce/woocommerce | 11k | — | ~893 | Automated safety check: Pass | Custom licence | |
| Email Best Practicesviclafouch/meme-studio | 110 | 7 repos | ~787 | Automated safety check: Pass | None | |
| React Emailviclafouch/meme-studio | 110 | 2 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Email Deliverability Auditgrowthenginenowoslawski/coldoutboundskills | 740 | — | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
WooCommerce Email Editor Development
woocommerce/woocommerce
Sets up a local environment for the WooCommerce block email editor, with a watcher, Mailpit email capture and build and test commands for its PHP and JS packages.
Email Best Practices
viclafouch/meme-studio
A skill your agent uses when building email features, emails going to spam, high bounce rates, setting up SPF/DKIM/DMARC authentication, implementing email capture, ensuring compliance (CAN-SPAM…
React Email
viclafouch/meme-studio
A skill your agent uses when creating HTML email templates with React components - welcome emails, password resets, notifications, order confirmations, newsletters, or transactional emails.
Email Deliverability Audit
growthenginenowoslawski/coldoutboundskills
Diagnostic audit for a running cold email program. An agent skill from growthenginenowoslawski/coldoutboundskills.
Cloudflare Email Service
hodgef/apiker
Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing).
More from openinary/openinary
Loops API
openinary/openinary
A skill your agent uses whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation.
Loops Email Sending Best Practices
openinary/openinary
A skill your agent uses when the user wants to review, audit, improve, or plan email sending best practices.
Issue Fixer
openinary/openinary
Implement GitHub issues collaboratively in open-source repositories with explicit approval gates, incremental delivery, atomic commits, and PR-ready validation.
Related
Works with
Categories
Questions about Loops CLI
What does Loops CLI do?
A skill your agent uses whenever the user wants to work with the Loops CLI from the terminal. Loops CLI is an agent skill from openinary/openinary. Use this skill whenever the user wants to work with the Loops CLI from the terminal.
When should I use Loops CLI?
Loops CLI fits situations like: the user wants to work with the Loops CLI from the terminal; phrases like Loops CLI; loops auth login; loops campaigns create.
How do I install Loops CLI in Claude Code?
Run `npx skills add openinary/openinary --skill loops-cli -a claude-code`. Or copy the skill folder (.agents/skills/loops-cli in openinary/openinary) into .claude/skills/loops-cli in your project. Claude Code loads it when a task matches its description.
How do I install Loops CLI in Codex?
Run `npx skills add openinary/openinary --skill loops-cli -a codex`. Or copy the skill folder (.agents/skills/loops-cli in openinary/openinary) into .agents/skills/loops-cli in your project. Codex loads it when a task matches its description.
Can I use Loops CLI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openinary/openinary --skill loops-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/loops-cli, .gemini/skills/loops-cli, .github/skills/loops-cli and .opencode/skills/loops-cli in your project.
What does Loops CLI need to run?
SKILL.md names no scripts, command-line tools or credentials: Loops CLI is instructions for the agent only.
Does Loops CLI access the network?
SKILL.md names 2 domains. In commands or code: github.com and loops.so; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Loops CLI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Loops CLI use?
Loops CLI is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Loops CLI use?
About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.
What are the alternatives to Loops CLI?
Skills that share tags, products or a category with Loops CLI: Stripe Projects (fossasia/eventyay, 1.7k stars), WooCommerce Email Editor Development (woocommerce/woocommerce, 11k stars), Email Best Practices (viclafouch/meme-studio, 110 stars) and React Email (viclafouch/meme-studio, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Loops CLI?
openinary (a GitHub organization) maintains it in openinary/openinary, which has 412 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 4, 2026.
Source: openinary/openinary on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.