lytics-integrations SKILL.md skillA
lytics-integrations from lytics/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lytics/agent-skills/lytics-integrations@git:20261010.8ca5e27Pins git:20261010.8ca5e27 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lytics/agent-skills
- Path
lytics-integrations/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261010.8ca5e27, committed Oct 10, 2026
- First version recorded
- Oct 9, 2026
- Size
- 5,964 bytes
- Repository stars
- 4
- License
- MIT
Lytics CDP: plan, set up, manage and debug data integrations -- choose a provider and workflow, map fields, create auth and connections, run the job lifecycle (create, update, pause, resume, bounce, kill, logs), build and test webhook templates, and trace why a user was or wasn't exported. Use when the user wants to connect a platform (Facebook, Google, Salesforce, Klaviyo...) for import, export, enrichment, audience sync or conversion API (CAPI); wants advice on an integration approach or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Lytics Integrations Everything between "I want to connect X" and a running job: picking the provider and workflow, field mapping, auth credentials, connections to external data sources, webhook templates for custom destinations, the job lifecycle (create, update, pause, resume, bounce, kill, logs), and debugging why one user did or didn't reach a destination. Integrations are layered: **Provider** (what platform) -> **Auth** (how to authenticate) -> **Connection** (optional, for data-source integrations) -> **Job** (runs one workflow). ## Before you start - Credentials: `references/auth.md`. - Request conventions, URL-encoding and the `/v2` error shape (`.errors[0].message`): `references/api.md`. - Every create, update, delete and lifecycle command goes through `references/confirmation-gate.md` (pause/resume may use a brief confirmation; kill needs explicit confirmation). - Never log or display full credential values. OAuth cannot be completed from the CLI: send the user to the Lytics UI, then pick up the new `auth_id` via `GET /v2/auth`. ## Gotchas …
Read the whole file at its exact version.
How to install
mdr add lytics/agent-skills/lytics-integrations@sha256:ea7fa0d8ab050567The line at the top of this page pins the label git:20261010.8ca5e27, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2ifzp5265dimzxaw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 10, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261010.8ca5e27 latest | 2026-10-10 | 8ca5e27 | 5,964 B | A | view · diff |
| git:20261009.c5336f3 | 2026-10-09 | c5336f3 | 4,263 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5964 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
lytics/agent-skills · 4 stars · license MIT · pushed 2026-10-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ifzp5265dimzxaw GET https://markdownregistry.com/api/v1/resolve?ref=lytics/agent-skills/lytics-integrations GET https://markdownregistry.com/api/v1/blob/ea7fa0d8ab050567dc2422c79d7e4f1b6f0b7b9c1af0f4598cf5f8ddefeaadaf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.