New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Loops API

by openinary in 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.

AGPL-3.0Auto-check passedBackend & APIs

Install Loops API

skills CLI
$ npx skills add openinary/openinary --skill loops-api -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openinary/openinary loops-api --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openinary/openinary.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/loops-api .claude/skills/loops-api && rm -rf skills-src

Use ~/.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/

Facts

Skill name
loops-api
GitHub stars
412
Token cost
~1.1k tokens
SKILL.md length
437 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 integrate Loops from application code, backend services, webhook handlers, or server-side automation.

  • Works in 7 steps: Choose the right interface first: SDK or… → Prefer official SDKs for application… → Prefer raw HTTP only when no SDK is… → …
  • The user wants to integrate Loops from application code
  • SKILL.md covers When To Use, Working Style, Choose The Interface and Category Routing, plus 1 more section
  • Reaches loops.so

What it does

Loops API is an agent skill from openinary/openinary. Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, campaign groups, transactional groups, audience segments, email messages, themes, and components), and workflow graph/node inspection and mutation. Trigger on phrases like "Loops API"…

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/http-api.md`).

It sits in Backend & APIs, covering Webhooks, Transactional email and REST APIs. 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 integrate Loops from application code
  • Backend services
  • Webhook handlers
  • Server-side automation

Example prompts

  • “Loops API”
  • “Loops SDK”
  • “create a campaign via API”
  • “/loops-api”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Choose the right interface first: SDK or raw HTTP.
  2. Prefer official SDKs for application code when the language has one.
  3. Prefer raw HTTP only when no SDK is available or the user needs exact payload control.
  4. Keep Loops requests server-side.
  5. Verify exact behavior against the official docs or OpenAPI spec when details matter.
  6. For LMX email design or brand work, use the theme/component endpoints in references/http-api.md; the LMX design policy lives in the…
  7. If the task is primarily about Loops CLI install, auth, shell usage, or command help, use the separate loops-cli 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:

    • loops.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 API loads about 1.1k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 227 tokens; SKILL.md has 437 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~227
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

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). 437 words, ~1,084 tokens.

Download SKILL.mdSave it as .claude/skills/loops-api/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
loops-api
description
Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. This includes the Loops HTTP API and official SDKs for server-side contact, contact-property, mailing-list, event, API-key-validation, transactional-email, content editing (campaigns, campaign groups, transactional groups, audience segments, email messages, themes, and components), and workflow graph/node inspection and mutation. Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "create a workflow via API", "add a workflow node", "send a Loops event from my app", "add a contact to Loops in a webhook", "send a transactional email from backend code", or any time the user wants to integrate Loops into their app, backend, webhook, or automation. Do not trigger for CLI or shell-only requests.
metadata.version
1.6.0

Loops API and SDK Skill

This skill helps with Loops implementation workflows from application code. Use it for backend integrations, exact request guidance, and SDK or HTTP decisions.

When To Use

Use this skill when the user needs to:

  • integrate Loops into an app, backend, webhook, or automation
  • decide between official SDKs and raw HTTP
  • manage contacts, contact properties, mailing lists, events, or transactional email
  • send transactional emails or create, edit, and publish transactional email templates via API
  • manage contact suppression status/removal
  • create draft campaigns with audience targeting (mailing list, segment, or filter), groups, and scheduling
  • organize campaigns and transactional emails into groups
  • list or create audience segments for campaign/workflow targeting
  • update email-message content (subject, sender, CC/BCC, format, fallbacks, LMX), send previews, and run Guardian checks
  • list/get themes and components to build LMX payloads
  • upload images for email content
  • create, update, and inspect workflows and workflow nodes (including mailing-list changes, branches, and queued-contact handling)
  • list event patterns for workflow event triggers
  • validate credentials or troubleshoot Loops request behavior from code

This skill is for implementation and operational usage, not broad email strategy or deliverability review.

Working Style

When this skill is active:

  1. Choose the right interface first: SDK or raw HTTP.
  2. Prefer official SDKs for application code when the language has one.
  3. Prefer raw HTTP only when no SDK is available or the user needs exact payload control.
  4. Keep Loops requests server-side.
  5. Verify exact behavior against the official docs or OpenAPI spec when details matter.
  6. For LMX email design or brand work, use the theme/component endpoints in references/http-api.md; the LMX design policy lives in the loops-lmx skill.
  7. If the task is primarily about Loops CLI install, auth, shell usage, or command help, use the separate loops-cli skill.

Official references:

  • Docs: https://loops.so/docs
  • API reference: https://loops.so/docs/api-reference/intro
  • Campaign examples: https://loops.so/docs/api-reference/examples/campaigns
  • JavaScript SDK: https://loops.so/docs/sdks/javascript
  • OpenAPI spec: https://app.loops.so/openapi.json
Show full SKILL.md (127 more words)Show less

Choose The Interface

  • SDK or HTTP API:
    • application code
    • backend services
    • webhook handlers
    • repeatable integrations Read references/http-api.md

If the user is working from the terminal instead of writing application code, use the loops-cli skill.

Category Routing

  • Auth, base URL, rate limits, contacts, suppression, properties, lists, events, uploads, SDK examples, and HTTP errors: Read references/http-api.md
  • Campaigns, campaign groups, transactional groups, audience segments, workflows, workflow nodes, event patterns, transactional emails, email messages, themes, components, and revision-safe updates: Read references/http-api.md. For LMX markup itself, also use the loops-lmx skill.

Output Checklist

Aim to leave the user with:

  • the right API interface choice for the task
  • exact payload shapes or SDK usage
  • any Loops-specific caveats that affect behavior
  • the next validation step, such as a small test request or API-key check

© 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-api of openinary/openinary.

  • SKILL.md
  • references/http-api.md

Open the folder on GitHubat commit 1f05325

Compare with similar skills

Loops API 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.

Loops API compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Loops API this skillopeninary/openinary412—~1.1kAutomated safety check: PassAGPL-3.0
E2a Integratetokencanopy/e2a192—~840Automated safety check: PassApache-2.0
Payram Widget IntegrationPayRam/payram-mcp158—~2.9kAutomated safety check: PassNone
Nodejs Backend Patternsever-works/ever-works15817 repos~4kAutomated safety check: PassAGPL-3.0
Pangolin CRUD Endpointsfosrl/pangolin23k—~461Automated safety check: PassCustom licence
Fastcrudbenavlabs/fastcrud1.6k—~5kAutomated safety check: PassMIT

Similar skills

  • E2a Integrate

    tokencanopy/e2a

    A skill your agent uses when adding e2a email capabilities to an application or codebase: outbound sending, inbound signed webhooks, REST polling, or SDK integration.

    192 GitHub stars~840 tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Payram Widget Integration

    PayRam/payram-mcp

    Integrate the PayRam Add Credit widget (payram-add-credit-v1.js) into a website or web app.

    158 GitHub stars~2.9k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    158 GitHub starsUsed in 17 repos~4k tokens
    Backend & APIsAuto-check passed

  • Pangolin CRUD Endpoints

    fosrl/pangolin

    Use whenever asked to add, create, or scaffold a CRUD endpoint, router, or entity in this repo's server (create/list/get/update/delete handlers, new…

    23k GitHub stars~461 tokensUpdated today
    Backend & APIsAuto-check passed

  • Fastcrud

    benavlabs/fastcrud

    A skill your agent uses when building or modifying CRUD endpoints with FastCRUD (the fastcrud PyPI package) in a FastAPI project — covers FastCRUD, crudrouter, EndpointCreator, FilterConfig…

    1.6k GitHub stars~5k tokensUpdated 12 days ago
    Backend & APIsAuto-check passed

  • Dr Jskill

    jdubois/dr-jskill

    Creates Java + Spring Boot projects: Web applications, full-stack apps with Vue.js or Angular or React or vanilla JS, PostgreSQL, REST APIs, and Docker.

    342 GitHub stars~4.6k tokensUpdated 7 days ago
    Backend & APIsAuto-check: notes

More from openinary/openinary

  • Loops CLI

    openinary/openinary

    A skill your agent uses whenever the user wants to work with the Loops CLI from the terminal.

    412 GitHub stars~782 tokensUpdated 2 days ago
    Auto-check passed

  • 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.

    412 GitHub stars~943 tokensUpdated 2 days ago
    Auto-check passed

  • Issue Fixer

    openinary/openinary

    Implement GitHub issues collaboratively in open-source repositories with explicit approval gates, incremental delivery, atomic commits, and PR-ready validation.

    412 GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Loops API

What does Loops API do?

A skill your agent uses whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation. Loops API is an agent skill from openinary/openinary. Use this skill whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation.

When should I use Loops API?

Loops API fits situations like: the user wants to integrate Loops from application code; backend services; webhook handlers; server-side automation.

How do I install Loops API in Claude Code?

Run `npx skills add openinary/openinary --skill loops-api -a claude-code`. Or copy the skill folder (.agents/skills/loops-api in openinary/openinary) into .claude/skills/loops-api in your project. Claude Code loads it when a task matches its description.

How do I install Loops API in Codex?

Run `npx skills add openinary/openinary --skill loops-api -a codex`. Or copy the skill folder (.agents/skills/loops-api in openinary/openinary) into .agents/skills/loops-api in your project. Codex loads it when a task matches its description.

Can I use Loops API 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-api -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-api, .gemini/skills/loops-api, .github/skills/loops-api and .opencode/skills/loops-api in your project.

What does Loops API need to run?

SKILL.md names no scripts, command-line tools or credentials: Loops API is instructions for the agent only.

Does Loops API access the network?

SKILL.md names 1 domain. In commands or code: loops.so; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Loops API 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 API use?

Loops API 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 API use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 13k tokens, read only when the agent opens those files.

What are the alternatives to Loops API?

Skills that share tags, products or a category with Loops API: E2a Integrate (tokencanopy/e2a, 192 stars), Payram Widget Integration (PayRam/payram-mcp, 158 stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars) and Pangolin CRUD Endpoints (fosrl/pangolin, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Loops API?

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.