loops-api
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 workflows (campaigns, email messages, themes, and components). Trigger on phrases like "Loops API", "Loops SDK", "create a campaign via API", "update email message LMX", "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.
What this skill does
# 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 - manage contact suppression status/removal - create draft campaigns, update email-message content (subject, sender, LMX), and upload image assets - list themes and components to build LMX payloads - 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. 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` ## 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, transactional payloads, uploads, SDK examples, and HTTP errors: Read `references/http-api.md` - Campaigns, email messages, themes, and components: 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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".