[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F1237RAAPTXT6G0G1CKSEH":3,"skill-same:01M7F1237RAAPTXT6G0G1CKSEH":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F1237RAAPTXT6G0G1CKSEH","klaviyo-automation",null,"Automate Klaviyo tasks via Rube MCP (Composio): manage email\u002FSMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fklaviyo-automation-antigravity-awesome-skills-main\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: klaviyo-automation\ndescription: \"Automate Klaviyo tasks via Rube MCP (Composio): manage email\u002FSMS campaigns, inspect campaign messages, track tags, and monitor send jobs. Always search tools first for current schemas.\"\nrisk: safe\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Klaviyo Automation via Rube MCP\n\nAutomate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\n3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Filter Campaigns\n\n**When to use**: User wants to browse, search, or filter marketing campaigns\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]\n\n**Key parameters**:\n- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)\n- `filter`: Additional filter string (e.g., `equals(status,\"draft\")`)\n- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')\n- `page_cursor`: Pagination cursor for next page\n- `include_archived`: Include archived campaigns (default: false)\n\n**Pitfalls**:\n- `channel` is required; omitting it can produce incomplete or unexpected results\n- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)\n- Follow `page_cursor` until exhausted to get all campaigns\n- Status filtering via `filter` (e.g., `equals(status,\"draft\")`) can return mixed statuses; always validate `data[].attributes.status` client-side\n- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')\n- Response shape is nested: `response.data.data` with status at `data[].attributes.status`\n\n### 2. Get Campaign Details\n\n**When to use**: User wants detailed information about a specific campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]\n\n**Key parameters**:\n- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')\n- `include_messages`: Include campaign messages in response\n- `include_tags`: Include tags in response\n\n**Pitfalls**:\n- Campaign IDs are alphanumeric strings, not numeric\n- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism\n- Campaign details include audiences, send strategy, tracking options, and scheduling info\n\n### 3. Inspect Campaign Messages\n\n**When to use**: User wants to view the email\u002FSMS content of a campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]\n\n**Key parameters**:\n- `id`: Message ID string\n- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')\n- `fields__campaign`: Sparse fieldset for campaign attributes\n- `fields__template`: Sparse fieldset for template attributes\n- `include`: Related resources to include ('campaign', 'template')\n\n**Pitfalls**:\n- Message IDs are separate from campaign IDs; extract from campaign response\n- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'\n- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email\n- SMS messages have content fields: body\n- Including 'template' provides the HTML\u002Ftext content of the email\n\n### 4. Manage Campaign Tags\n\n**When to use**: User wants to view tags associated with campaigns for organization\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]\n\n**Key parameters**:\n- `id`: Campaign ID string\n\n**Pitfalls**:\n- Returns only tag IDs, not tag names\u002Fdetails\n- Tag IDs can be used with Klaviyo's tag endpoints for full details\n- Rate limit: 3\u002Fs burst, 60\u002Fm steady (stricter than other endpoints)\n\n### 5. Monitor Campaign Send Jobs\n\n**When to use**: User wants to check the status of a campaign send operation\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]\n\n**Key parameters**:\n- `id`: Send job ID\n\n**Pitfalls**:\n- Send job IDs are returned when a campaign send is initiated\n- Job statuses indicate whether the send is queued, in progress, complete, or failed\n- Rate limit: 10\u002Fs burst, 150\u002Fm steady\n\n## Common Patterns\n\n### Campaign Discovery Pattern\n\n```\n1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'\n2. Paginate through all results via page_cursor\n3. Filter by status client-side for accuracy\n4. Extract campaign IDs for detailed inspection\n```\n\n### Sparse Fieldset Pattern\n\nKlaviyo supports sparse fieldsets to reduce response size:\n```\nfields__campaign__message=['content.subject', 'content.from_email', 'send_times']\nfields__campaign=['name', 'status', 'send_time']\nfields__template=['name', 'html', 'text']\n```\n\n### Pagination\n\n- Klaviyo uses cursor-based pagination\n- Check response for `page_cursor` in the pagination metadata\n- Pass cursor as `page_cursor` in next request\n- Default page size is ~10 campaigns\n- Continue until no more cursor is returned\n\n### Filter Syntax\n\n```\n- equals(status,\"draft\") - Campaigns in draft status\n- equals(name,\"Newsletter\") - Campaign named \"Newsletter\"\n- greater-than(created_at,\"2024-01-01T00:00:00Z\") - Created after date\n```\n\n## Known Pitfalls\n\n**API Version**:\n- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)\n- Response schemas may change between API versions\n- Tool responses follow the version configured in the Composio integration\n\n**Response Nesting**:\n- Data is nested: `response.data.data[].attributes`\n- Campaign status at `data[].attributes.status`\n- Mis-parsing the nesting yields empty or incorrect results\n- Always navigate through the full path defensively\n\n**Rate Limits**:\n- Burst: 10\u002Fs (3\u002Fs for tag endpoints)\n- Steady: 150\u002Fm (60\u002Fm for tag endpoints)\n- Required scope: campaigns:read\n- Implement backoff on 429 responses\n\n**Status Values**:\n- Status strings are case-sensitive\n- Compound statuses exist (e.g., 'Cancelled: No Recipients')\n- Server-side filtering may return mixed statuses; always validate client-side\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |\n| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |\n| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |\n| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |\n| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Klaviyo Automation via Rube MCP\n\nAutomate Klaviyo email and SMS marketing operations through Composio's Klaviyo toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Klaviyo connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `klaviyo`\n3. If connection is not ACTIVE, follow the returned auth link to complete Klaviyo authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Filter Campaigns\n\n**When to use**: User wants to browse, search, or filter marketing campaigns\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - List campaigns with channel and status filters [Required]\n\n**Key parameters**:\n- `channel`: Campaign channel - 'email' or 'sms' (required by Klaviyo API)\n- `filter`: Additional filter string (e.g., `equals(status,\"draft\")`)\n- `sort`: Sort field with optional `-` prefix for descending (e.g., '-created_at', 'name')\n- `page_cursor`: Pagination cursor for next page\n- `include_archived`: Include archived campaigns (default: false)\n\n**Pitfalls**:\n- `channel` is required; omitting it can produce incomplete or unexpected results\n- Pagination is mandatory for full coverage; a single call returns only one page (default ~10)\n- Follow `page_cursor` until exhausted to get all campaigns\n- Status filtering via `filter` (e.g., `equals(status,\"draft\")`) can return mixed statuses; always validate `data[].attributes.status` client-side\n- Status strings are case-sensitive and can be compound (e.g., 'Cancelled: No Recipients')\n- Response shape is nested: `response.data.data` with status at `data[].attributes.status`\n\n### 2. Get Campaign Details\n\n**When to use**: User wants detailed information about a specific campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGNS` - Find campaign to get its ID [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN` - Retrieve full campaign details [Required]\n\n**Key parameters**:\n- `campaign_id`: Campaign ID string (e.g., '01GDDKASAP8TKDDA2GRZDSVP4H')\n- `include_messages`: Include campaign messages in response\n- `include_tags`: Include tags in response\n\n**Pitfalls**:\n- Campaign IDs are alphanumeric strings, not numeric\n- `include_messages` and `include_tags` add related data to the response via Klaviyo's include mechanism\n- Campaign details include audiences, send strategy, tracking options, and scheduling info\n\n### 3. Inspect Campaign Messages\n\n**When to use**: User wants to view the email\u002FSMS content of a campaign\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN` - Find campaign and its message IDs [Prerequisite]\n2. `KLAVIYO_GET_CAMPAIGN_MESSAGE` - Get message content details [Required]\n\n**Key parameters**:\n- `id`: Message ID string\n- `fields__campaign__message`: Sparse fieldset for message attributes (e.g., 'content.subject', 'content.from_email', 'content.body')\n- `fields__campaign`: Sparse fieldset for campaign attributes\n- `fields__template`: Sparse fieldset for template attributes\n- `include`: Related resources to include ('campaign', 'template')\n\n**Pitfalls**:\n- Message IDs are separate from campaign IDs; extract from campaign response\n- Sparse fieldset syntax uses dot notation for nested fields: 'content.subject', 'content.from_email'\n- Email messages have content fields: subject, preview_text, from_email, from_label, reply_to_email\n- SMS messages have content fields: body\n- Including 'template' provides the HTML\u002Ftext content of the email\n\n### 4. Manage Campaign Tags\n\n**When to use**: User wants to view tags associated with campaigns for organization\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS` - Get tag IDs for a campaign [Required]\n\n**Key parameters**:\n- `id`: Campaign ID string\n\n**Pitfalls**:\n- Returns only tag IDs, not tag names\u002Fdetails\n- Tag IDs can be used with Klaviyo's tag endpoints for full details\n- Rate limit: 3\u002Fs burst, 60\u002Fm steady (stricter than other endpoints)\n\n### 5. Monitor Campaign Send Jobs\n\n**When to use**: User wants to check the status of a campaign send operation\n\n**Tool sequence**:\n1. `KLAVIYO_GET_CAMPAIGN_SEND_JOB` - Check send job status [Required]\n\n**Key parameters**:\n- `id`: Send job ID\n\n**Pitfalls**:\n- Send job IDs are returned when a campaign send is initiated\n- Job statuses indicate whether the send is queued, in progress, complete, or failed\n- Rate limit: 10\u002Fs burst, 150\u002Fm steady\n\n## Common Patterns\n\n### Campaign Discovery Pattern\n\n```\n1. Call KLAVIYO_GET_CAMPAIGNS with channel='email'\n2. Paginate through all results via page_cursor\n3. Filter by status client-side for accuracy\n4. Extract campaign IDs for detailed inspection\n```\n\n### Sparse Fieldset Pattern\n\nKlaviyo supports sparse fieldsets to reduce response size:\n```\nfields__campaign__message=['content.subject', 'content.from_email', 'send_times']\nfields__campaign=['name', 'status', 'send_time']\nfields__template=['name', 'html', 'text']\n```\n\n### Pagination\n\n- Klaviyo uses cursor-based pagination\n- Check response for `page_cursor` in the pagination metadata\n- Pass cursor as `page_cursor` in next request\n- Default page size is ~10 campaigns\n- Continue until no more cursor is returned\n\n### Filter Syntax\n\n```\n- equals(status,\"draft\") - Campaigns in draft status\n- equals(name,\"Newsletter\") - Campaign named \"Newsletter\"\n- greater-than(created_at,\"2024-01-01T00:00:00Z\") - Created after date\n```\n\n## Known Pitfalls\n\n**API Version**:\n- Klaviyo API uses versioned endpoints (e.g., v2024-07-15)\n- Response schemas may change between API versions\n- Tool responses follow the version configured in the Composio integration\n\n**Response Nesting**:\n- Data is nested: `response.data.data[].attributes`\n- Campaign status at `data[].attributes.status`\n- Mis-parsing the nesting yields empty or incorrect results\n- Always navigate through the full path defensively\n\n**Rate Limits**:\n- Burst: 10\u002Fs (3\u002Fs for tag endpoints)\n- Steady: 150\u002Fm (60\u002Fm for tag endpoints)\n- Required scope: campaigns:read\n- Implement backoff on 429 responses\n\n**Status Values**:\n- Status strings are case-sensitive\n- Compound statuses exist (e.g., 'Cancelled: No Recipients')\n- Server-side filtering may return mixed statuses; always validate client-side\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List campaigns | KLAVIYO_GET_CAMPAIGNS | channel, filter, sort, page_cursor |\n| Get campaign details | KLAVIYO_GET_CAMPAIGN | campaign_id, include_messages, include_tags |\n| Get campaign message | KLAVIYO_GET_CAMPAIGN_MESSAGE | id, fields__campaign__message |\n| Get campaign tags | KLAVIYO_GET_CAMPAIGN_RELATIONSHIPS_TAGS | id |\n| Get send job status | KLAVIYO_GET_CAMPAIGN_SEND_JOB | id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fklaviyo-automation-antigravity-awesome-skills-main",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill klaviyo-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill klaviyo-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill klaviyo-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fklaviyo-automation-antigravity-awesome-skills-main\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]