[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CC3BJ2FD9SWRHGZC7D25Y0":3,"skill-same:01M7CC3BJ2FD9SWRHGZC7D25Y0":50},{"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":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CC3BJ2FD9SWRHGZC7D25Y0","postmark-automation",null,"Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fpostmark-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: postmark-automation\ndescription: \"Automate Postmark email delivery tasks via Rube MCP (Composio): send templated emails, manage templates, monitor delivery stats and bounces. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Postmark Automation via Rube MCP\n\nAutomate Postmark transactional email operations through Composio's Postmark toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Postmark connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `postmark`\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 `postmark`\n3. If connection is not ACTIVE, follow the returned auth link to complete Postmark authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Templated Batch Emails\n\n**When to use**: User wants to send templated emails to multiple recipients in one call\n\n**Tool sequence**:\n1. `POSTMARK_LIST_TEMPLATES` - Find available templates and their IDs [Prerequisite]\n2. `POSTMARK_VALIDATE_TEMPLATE` - Validate template with model data before sending [Optional]\n3. `POSTMARK_SEND_BATCH_WITH_TEMPLATES` - Send batch emails using a template [Required]\n\n**Key parameters**:\n- `TemplateId` or `TemplateAlias`: Identifier for the template to use\n- `Messages`: Array of message objects with `From`, `To`, `TemplateModel`\n- `TemplateModel`: Key-value pairs matching template variables\n\n**Pitfalls**:\n- Maximum 500 messages per batch call\n- Either `TemplateId` or `TemplateAlias` is required, not both\n- `TemplateModel` keys must match template variable names exactly (case-sensitive)\n- Sender address must be a verified Sender Signature or from a verified domain\n\n### 2. Manage Email Templates\n\n**When to use**: User wants to create, edit, or inspect email templates\n\n**Tool sequence**:\n1. `POSTMARK_LIST_TEMPLATES` - List all templates with IDs and names [Required]\n2. `POSTMARK_GET_TEMPLATE` - Get full template details including HTML\u002Ftext body [Optional]\n3. `POSTMARK_EDIT_TEMPLATE` - Update template content or settings [Optional]\n4. `POSTMARK_VALIDATE_TEMPLATE` - Test template rendering with sample data [Optional]\n\n**Key parameters**:\n- `TemplateId`: Numeric template ID for GET\u002FEDIT operations\n- `Name`: Template display name\n- `Subject`: Email subject line (supports template variables)\n- `HtmlBody`: HTML content of the template\n- `TextBody`: Plain text fallback content\n- `TemplateType`: 'Standard' or 'Layout'\n\n**Pitfalls**:\n- Template IDs are numeric integers, not strings\n- Editing a template replaces the entire content; include all fields you want to keep\n- Layout templates wrap Standard templates; changing a layout affects all linked templates\n- Validate before sending to catch missing variables early\n\n### 3. Monitor Delivery Statistics\n\n**When to use**: User wants to check email delivery health, open\u002Fclick rates, or outbound overview\n\n**Tool sequence**:\n1. `POSTMARK_GET_DELIVERY_STATS` - Get bounce counts by type [Required]\n2. `POSTMARK_GET_OUTBOUND_OVERVIEW` - Get sent\u002Fopened\u002Fclicked\u002Fbounced summary [Required]\n3. `POSTMARK_GET_TRACKED_EMAIL_COUNTS` - Get tracked email volume over time [Optional]\n\n**Key parameters**:\n- `fromdate`: Start date for filtering stats (YYYY-MM-DD)\n- `todate`: End date for filtering stats (YYYY-MM-DD)\n- `tag`: Filter stats by message tag\n- `messagestreamid`: Filter by message stream (e.g., 'outbound', 'broadcast')\n\n**Pitfalls**:\n- Date parameters use YYYY-MM-DD format without time component\n- Stats are aggregated; individual message tracking requires separate API calls\n- `messagestreamid` defaults to all streams if not specified\n\n### 4. Manage Bounces and Complaints\n\n**When to use**: User wants to review bounced emails or spam complaints\n\n**Tool sequence**:\n1. `POSTMARK_GET_BOUNCES` - List bounced messages with details [Required]\n2. `POSTMARK_GET_SPAM_COMPLAINTS` - List spam complaint records [Optional]\n3. `POSTMARK_GET_DELIVERY_STATS` - Get bounce summary counts [Optional]\n\n**Key parameters**:\n- `count`: Number of records to return per page\n- `offset`: Pagination offset for results\n- `type`: Bounce type filter (e.g., 'HardBounce', 'SoftBounce', 'SpamNotification')\n- `fromdate`\u002F`todate`: Date range filters\n- `emailFilter`: Filter by recipient email address\n\n**Pitfalls**:\n- Bounce types include: HardBounce, SoftBounce, SpamNotification, SpamComplaint, Transient, and others\n- Hard bounces indicate permanent delivery failures; these addresses should be removed\n- Spam complaints affect sender reputation; monitor regularly\n- Pagination uses `count` and `offset`, not page tokens\n\n### 5. Configure Server Settings\n\n**When to use**: User wants to view or modify Postmark server configuration\n\n**Tool sequence**:\n1. `POSTMARK_GET_SERVER` - Retrieve current server settings [Required]\n2. `POSTMARK_EDIT_SERVER` - Update server configuration [Optional]\n\n**Key parameters**:\n- `Name`: Server display name\n- `SmtpApiActivated`: Enable\u002Fdisable SMTP API access\n- `BounceHookUrl`: Webhook URL for bounce notifications\n- `InboundHookUrl`: Webhook URL for inbound email processing\n- `TrackOpens`: Enable\u002Fdisable open tracking\n- `TrackLinks`: Link tracking mode ('None', 'HtmlAndText', 'HtmlOnly', 'TextOnly')\n\n**Pitfalls**:\n- Server edits affect all messages sent through that server\n- Webhook URLs must be publicly accessible HTTPS endpoints\n- Changing `SmtpApiActivated` affects SMTP relay access immediately\n- Track settings apply to future messages only, not retroactively\n\n## Common Patterns\n\n### Template Variable Resolution\n\n```\n1. Call POSTMARK_GET_TEMPLATE with TemplateId\n2. Inspect HtmlBody\u002FTextBody for {{variable}} placeholders\n3. Build TemplateModel dict with matching keys\n4. Call POSTMARK_VALIDATE_TEMPLATE to verify rendering\n```\n\n### Pagination\n\n- Set `count` for results per page (varies by endpoint)\n- Use `offset` to skip previously fetched results\n- Increment offset by count each page until results returned \u003C count\n- Total records may be returned in response metadata\n\n## Known Pitfalls\n\n**Authentication**:\n- Postmark uses server-level API tokens, not account-level\n- Each server has its own token; ensure correct server context\n- Sender addresses must be verified Sender Signatures or from verified domains\n\n**Rate Limits**:\n- Batch send limited to 500 messages per call\n- API rate limits vary by endpoint; implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Template IDs are always numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send batch templated emails | POSTMARK_SEND_BATCH_WITH_TEMPLATES | Messages, TemplateId\u002FTemplateAlias |\n| List templates | POSTMARK_LIST_TEMPLATES | Count, Offset, TemplateType |\n| Get template details | POSTMARK_GET_TEMPLATE | TemplateId |\n| Edit template | POSTMARK_EDIT_TEMPLATE | TemplateId, Name, Subject, HtmlBody |\n| Validate template | POSTMARK_VALIDATE_TEMPLATE | TemplateId, TemplateModel |\n| Delivery stats | POSTMARK_GET_DELIVERY_STATS | (none or date filters) |\n| Outbound overview | POSTMARK_GET_OUTBOUND_OVERVIEW | fromdate, todate, tag |\n| Get bounces | POSTMARK_GET_BOUNCES | count, offset, type, emailFilter |\n| Get spam complaints | POSTMARK_GET_SPAM_COMPLAINTS | count, offset, fromdate, todate |\n| Tracked email counts | POSTMARK_GET_TRACKED_EMAIL_COUNTS | fromdate, todate, tag |\n| Get server config | POSTMARK_GET_SERVER | (none) |\n| Edit server config | POSTMARK_EDIT_SERVER | Name, TrackOpens, TrackLinks |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Postmark Automation via Rube MCP\n\nAutomate Postmark transactional email operations through Composio's Postmark toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Postmark connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `postmark`\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 `postmark`\n3. If connection is not ACTIVE, follow the returned auth link to complete Postmark authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Templated Batch Emails\n\n**When to use**: User wants to send templated emails to multiple recipients in one call\n\n**Tool sequence**:\n1. `POSTMARK_LIST_TEMPLATES` - Find available templates and their IDs [Prerequisite]\n2. `POSTMARK_VALIDATE_TEMPLATE` - Validate template with model data before sending [Optional]\n3. `POSTMARK_SEND_BATCH_WITH_TEMPLATES` - Send batch emails using a template [Required]\n\n**Key parameters**:\n- `TemplateId` or `TemplateAlias`: Identifier for the template to use\n- `Messages`: Array of message objects with `From`, `To`, `TemplateModel`\n- `TemplateModel`: Key-value pairs matching template variables\n\n**Pitfalls**:\n- Maximum 500 messages per batch call\n- Either `TemplateId` or `TemplateAlias` is required, not both\n- `TemplateModel` keys must match template variable names exactly (case-sensitive)\n- Sender address must be a verified Sender Signature or from a verified domain\n\n### 2. Manage Email Templates\n\n**When to use**: User wants to create, edit, or inspect email templates\n\n**Tool sequence**:\n1. `POSTMARK_LIST_TEMPLATES` - List all templates with IDs and names [Required]\n2. `POSTMARK_GET_TEMPLATE` - Get full template details including HTML\u002Ftext body [Optional]\n3. `POSTMARK_EDIT_TEMPLATE` - Update template content or settings [Optional]\n4. `POSTMARK_VALIDATE_TEMPLATE` - Test template rendering with sample data [Optional]\n\n**Key parameters**:\n- `TemplateId`: Numeric template ID for GET\u002FEDIT operations\n- `Name`: Template display name\n- `Subject`: Email subject line (supports template variables)\n- `HtmlBody`: HTML content of the template\n- `TextBody`: Plain text fallback content\n- `TemplateType`: 'Standard' or 'Layout'\n\n**Pitfalls**:\n- Template IDs are numeric integers, not strings\n- Editing a template replaces the entire content; include all fields you want to keep\n- Layout templates wrap Standard templates; changing a layout affects all linked templates\n- Validate before sending to catch missing variables early\n\n### 3. Monitor Delivery Statistics\n\n**When to use**: User wants to check email delivery health, open\u002Fclick rates, or outbound overview\n\n**Tool sequence**:\n1. `POSTMARK_GET_DELIVERY_STATS` - Get bounce counts by type [Required]\n2. `POSTMARK_GET_OUTBOUND_OVERVIEW` - Get sent\u002Fopened\u002Fclicked\u002Fbounced summary [Required]\n3. `POSTMARK_GET_TRACKED_EMAIL_COUNTS` - Get tracked email volume over time [Optional]\n\n**Key parameters**:\n- `fromdate`: Start date for filtering stats (YYYY-MM-DD)\n- `todate`: End date for filtering stats (YYYY-MM-DD)\n- `tag`: Filter stats by message tag\n- `messagestreamid`: Filter by message stream (e.g., 'outbound', 'broadcast')\n\n**Pitfalls**:\n- Date parameters use YYYY-MM-DD format without time component\n- Stats are aggregated; individual message tracking requires separate API calls\n- `messagestreamid` defaults to all streams if not specified\n\n### 4. Manage Bounces and Complaints\n\n**When to use**: User wants to review bounced emails or spam complaints\n\n**Tool sequence**:\n1. `POSTMARK_GET_BOUNCES` - List bounced messages with details [Required]\n2. `POSTMARK_GET_SPAM_COMPLAINTS` - List spam complaint records [Optional]\n3. `POSTMARK_GET_DELIVERY_STATS` - Get bounce summary counts [Optional]\n\n**Key parameters**:\n- `count`: Number of records to return per page\n- `offset`: Pagination offset for results\n- `type`: Bounce type filter (e.g., 'HardBounce', 'SoftBounce', 'SpamNotification')\n- `fromdate`\u002F`todate`: Date range filters\n- `emailFilter`: Filter by recipient email address\n\n**Pitfalls**:\n- Bounce types include: HardBounce, SoftBounce, SpamNotification, SpamComplaint, Transient, and others\n- Hard bounces indicate permanent delivery failures; these addresses should be removed\n- Spam complaints affect sender reputation; monitor regularly\n- Pagination uses `count` and `offset`, not page tokens\n\n### 5. Configure Server Settings\n\n**When to use**: User wants to view or modify Postmark server configuration\n\n**Tool sequence**:\n1. `POSTMARK_GET_SERVER` - Retrieve current server settings [Required]\n2. `POSTMARK_EDIT_SERVER` - Update server configuration [Optional]\n\n**Key parameters**:\n- `Name`: Server display name\n- `SmtpApiActivated`: Enable\u002Fdisable SMTP API access\n- `BounceHookUrl`: Webhook URL for bounce notifications\n- `InboundHookUrl`: Webhook URL for inbound email processing\n- `TrackOpens`: Enable\u002Fdisable open tracking\n- `TrackLinks`: Link tracking mode ('None', 'HtmlAndText', 'HtmlOnly', 'TextOnly')\n\n**Pitfalls**:\n- Server edits affect all messages sent through that server\n- Webhook URLs must be publicly accessible HTTPS endpoints\n- Changing `SmtpApiActivated` affects SMTP relay access immediately\n- Track settings apply to future messages only, not retroactively\n\n## Common Patterns\n\n### Template Variable Resolution\n\n```\n1. Call POSTMARK_GET_TEMPLATE with TemplateId\n2. Inspect HtmlBody\u002FTextBody for {{variable}} placeholders\n3. Build TemplateModel dict with matching keys\n4. Call POSTMARK_VALIDATE_TEMPLATE to verify rendering\n```\n\n### Pagination\n\n- Set `count` for results per page (varies by endpoint)\n- Use `offset` to skip previously fetched results\n- Increment offset by count each page until results returned \u003C count\n- Total records may be returned in response metadata\n\n## Known Pitfalls\n\n**Authentication**:\n- Postmark uses server-level API tokens, not account-level\n- Each server has its own token; ensure correct server context\n- Sender addresses must be verified Sender Signatures or from verified domains\n\n**Rate Limits**:\n- Batch send limited to 500 messages per call\n- API rate limits vary by endpoint; implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Template IDs are always numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send batch templated emails | POSTMARK_SEND_BATCH_WITH_TEMPLATES | Messages, TemplateId\u002FTemplateAlias |\n| List templates | POSTMARK_LIST_TEMPLATES | Count, Offset, TemplateType |\n| Get template details | POSTMARK_GET_TEMPLATE | TemplateId |\n| Edit template | POSTMARK_EDIT_TEMPLATE | TemplateId, Name, Subject, HtmlBody |\n| Validate template | POSTMARK_VALIDATE_TEMPLATE | TemplateId, TemplateModel |\n| Delivery stats | POSTMARK_GET_DELIVERY_STATS | (none or date filters) |\n| Outbound overview | POSTMARK_GET_OUTBOUND_OVERVIEW | fromdate, todate, tag |\n| Get bounces | POSTMARK_GET_BOUNCES | count, offset, type, emailFilter |\n| Get spam complaints | POSTMARK_GET_SPAM_COMPLAINTS | count, offset, fromdate, todate |\n| Tracked email counts | POSTMARK_GET_TRACKED_EMAIL_COUNTS | fromdate, todate, tag |\n| Get server config | POSTMARK_GET_SERVER | (none) |\n| Edit server config | POSTMARK_EDIT_SERVER | Name, TrackOpens, TrackLinks |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fpostmark-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill postmark-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill postmark-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill postmark-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fpostmark-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]