[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSSYPVBEYA04DMJEXZFHKY":3,"skill-same:01M6FSSYPVBEYA04DMJEXZFHKY":74},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6FSSYPVBEYA04DMJEXZFHKY","telegram-automation",null,"Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos\u002Fdocuments, and handle bot commands. Always search tools first for current schemas.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Ftelegram-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","telegram automation","telegram","first","via","commands","composio","community","photos","manage","automate","MCP","Tools","messages","search","share","tasks","documents","bot","2026-11-10 10:12:30",false,"---\nname: telegram-automation\ndescription: \"Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos\u002Fdocuments, and handle bot commands. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Telegram Automation via Rube MCP\n\nAutomate Telegram operations through Composio's Telegram toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Telegram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n- Telegram Bot Token required (created via @BotFather)\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 `telegram`\n3. If connection is not ACTIVE, follow the returned auth link to configure the Telegram bot\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Messages\n\n**When to use**: User wants to send text messages to a Telegram chat\n\n**Tool sequence**:\n1. `TELEGRAM_GET_ME` - Verify bot identity and connection [Prerequisite]\n2. `TELEGRAM_GET_CHAT` - Get chat details and verify access [Optional]\n3. `TELEGRAM_SEND_MESSAGE` - Send a text message [Required]\n\n**Key parameters**:\n- `chat_id`: Numeric chat ID or channel username (e.g., '@channelname')\n- `text`: Message text content\n- `parse_mode`: 'HTML' or 'MarkdownV2' for formatting\n- `disable_notification`: Send silently without notification sound\n- `reply_to_message_id`: Message ID to reply to\n\n**Pitfalls**:\n- Bot must be a member of the chat\u002Fgroup to send messages\n- MarkdownV2 requires escaping special characters: `_*[]()~>#+-=|{}.!`\n- HTML mode supports limited tags: `\u003Cb>`, `\u003Ci>`, `\u003Ccode>`, `\u003Cpre>`, `\u003Ca>`\n- Messages have a 4096 character limit; split longer content\n\n### 2. Send Photos and Documents\n\n**When to use**: User wants to share images or files in a Telegram chat\n\n**Tool sequence**:\n1. `TELEGRAM_SEND_PHOTO` - Send an image [Optional]\n2. `TELEGRAM_SEND_DOCUMENT` - Send a file\u002Fdocument [Optional]\n\n**Key parameters**:\n- `chat_id`: Target chat ID\n- `photo`: Photo URL or file_id (for SEND_PHOTO)\n- `document`: Document URL or file_id (for SEND_DOCUMENT)\n- `caption`: Optional caption for the media\n\n**Pitfalls**:\n- Photo captions have a 1024 character limit\n- Document captions also have a 1024 character limit\n- Files up to 50MB can be sent via bot API\n- Photos are compressed by Telegram; use SEND_DOCUMENT for uncompressed images\n\n### 3. Manage Chats\n\n**When to use**: User wants to get chat information or manage chat settings\n\n**Tool sequence**:\n1. `TELEGRAM_GET_CHAT` - Get detailed chat information [Required]\n2. `TELEGRAM_GET_CHAT_ADMINISTRATORS` - List chat admins [Optional]\n3. `TELEGRAM_GET_CHAT_MEMBERS_COUNT` - Get member count [Optional]\n4. `TELEGRAM_EXPORT_CHAT_INVITE_LINK` - Generate invite link [Optional]\n\n**Key parameters**:\n- `chat_id`: Target chat ID or username\n\n**Pitfalls**:\n- Bot must be an administrator to export invite links\n- GET_CHAT returns different fields for private chats vs groups vs channels\n- Member count may be approximate for very large groups\n- Admin list does not include regular members\n\n### 4. Edit and Delete Messages\n\n**When to use**: User wants to modify or remove previously sent messages\n\n**Tool sequence**:\n1. `TELEGRAM_EDIT_MESSAGE` - Edit a sent message [Optional]\n2. `TELEGRAM_DELETE_MESSAGE` - Delete a message [Optional]\n\n**Key parameters**:\n- `chat_id`: Chat where the message is located\n- `message_id`: ID of the message to edit or delete\n- `text`: New text content (for edit)\n\n**Pitfalls**:\n- Bots can only edit their own messages\n- Messages can only be deleted within 48 hours of sending\n- In groups, bots with delete permissions can delete any message\n- Editing a message removes its 'edited' timestamp history\n\n### 5. Forward Messages and Get Updates\n\n**When to use**: User wants to forward messages or retrieve recent updates\n\n**Tool sequence**:\n1. `TELEGRAM_FORWARD_MESSAGE` - Forward a message to another chat [Optional]\n2. `TELEGRAM_GET_UPDATES` - Get recent bot updates\u002Fmessages [Optional]\n3. `TELEGRAM_GET_CHAT_HISTORY` - Get chat message history [Optional]\n\n**Key parameters**:\n- `from_chat_id`: Source chat for forwarding\n- `chat_id`: Destination chat for forwarding\n- `message_id`: Message to forward\n- `offset`: Update offset for GET_UPDATES\n- `limit`: Number of updates to retrieve\n\n**Pitfalls**:\n- Forwarded messages show the original sender attribution\n- GET_UPDATES returns a limited window of recent updates\n- Chat history access may be limited by bot permissions and chat type\n- Use offset to avoid processing the same update twice\n\n### 6. Manage Bot Commands\n\n**When to use**: User wants to set or update bot command menu\n\n**Tool sequence**:\n1. `TELEGRAM_SET_MY_COMMANDS` - Set the bot's command list [Required]\n2. `TELEGRAM_ANSWER_CALLBACK_QUERY` - Respond to inline button presses [Optional]\n\n**Key parameters**:\n- `commands`: Array of command objects with `command` and `description`\n- `callback_query_id`: ID of the callback query to answer\n\n**Pitfalls**:\n- Commands must start with '\u002F' and be lowercase\n- Command descriptions have a 256 character limit\n- Callback queries must be answered within 10 seconds or they expire\n- Setting commands replaces the entire command list\n\n## Common Patterns\n\n### Chat ID Resolution\n\n**From username**:\n```\n1. Use '@username' format as chat_id (for public channels\u002Fgroups)\n2. For private chats, numeric chat_id is required\n3. Call GET_CHAT with username to retrieve numeric ID\n```\n\n**From GET_UPDATES**:\n```\n1. Call TELEGRAM_GET_UPDATES\n2. Extract chat.id from message objects\n3. Use numeric chat_id in subsequent calls\n```\n\n### Message Formatting\n\n- Use `parse_mode: 'HTML'` for `\u003Cb>bold\u003C\u002Fb>`, `\u003Ci>italic\u003C\u002Fi>`, `\u003Ccode>code\u003C\u002Fcode>`\n- Use `parse_mode: 'MarkdownV2'` for `*bold*`, `_italic_`, `` `code` ``\n- Escape special chars in MarkdownV2: `_ * [ ] ( ) ~ > # + - = | { } . !`\n- Omit parse_mode for plain text without formatting\n\n## Known Pitfalls\n\n**Bot Permissions**:\n- Bots must be added to groups\u002Fchannels to interact\n- Admin permissions needed for: deleting messages, exporting invite links, managing members\n- Bots cannot initiate conversations; users must start them first\n\n**Rate Limits**:\n- 30 messages per second to the same group\n- 20 messages per minute to the same user in groups\n- Bulk operations should implement delays between calls\n- API returns 429 Too Many Requests when limits are hit\n\n**Chat Types**:\n- Private chat: One-on-one with the bot\n- Group: Multi-user chat (bot must be added)\n- Supergroup: Enhanced group with admin features\n- Channel: Broadcast-only (bot must be admin to post)\n\n**Message Limits**:\n- Text messages: 4096 characters max\n- Captions: 1024 characters max\n- File uploads: 50MB max via bot API\n- Inline keyboard buttons: 8 per row\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Verify bot | TELEGRAM_GET_ME | (none) |\n| Send message | TELEGRAM_SEND_MESSAGE | chat_id, text, parse_mode |\n| Send photo | TELEGRAM_SEND_PHOTO | chat_id, photo, caption |\n| Send document | TELEGRAM_SEND_DOCUMENT | chat_id, document, caption |\n| Edit message | TELEGRAM_EDIT_MESSAGE | chat_id, message_id, text |\n| Delete message | TELEGRAM_DELETE_MESSAGE | chat_id, message_id |\n| Forward message | TELEGRAM_FORWARD_MESSAGE | chat_id, from_chat_id, message_id |\n| Get chat info | TELEGRAM_GET_CHAT | chat_id |\n| Get chat admins | TELEGRAM_GET_CHAT_ADMINISTRATORS | chat_id |\n| Get member count | TELEGRAM_GET_CHAT_MEMBERS_COUNT | chat_id |\n| Export invite link | TELEGRAM_EXPORT_CHAT_INVITE_LINK | chat_id |\n| Get updates | TELEGRAM_GET_UPDATES | offset, limit |\n| Get chat history | TELEGRAM_GET_CHAT_HISTORY | chat_id |\n| Set bot commands | TELEGRAM_SET_MY_COMMANDS | commands |\n| Answer callback | TELEGRAM_ANSWER_CALLBACK_QUERY | callback_query_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Telegram Automation via Rube MCP\n\nAutomate Telegram operations through Composio's Telegram toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Telegram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n- Telegram Bot Token required (created via @BotFather)\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 `telegram`\n3. If connection is not ACTIVE, follow the returned auth link to configure the Telegram bot\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Messages\n\n**When to use**: User wants to send text messages to a Telegram chat\n\n**Tool sequence**:\n1. `TELEGRAM_GET_ME` - Verify bot identity and connection [Prerequisite]\n2. `TELEGRAM_GET_CHAT` - Get chat details and verify access [Optional]\n3. `TELEGRAM_SEND_MESSAGE` - Send a text message [Required]\n\n**Key parameters**:\n- `chat_id`: Numeric chat ID or channel username (e.g., '@channelname')\n- `text`: Message text content\n- `parse_mode`: 'HTML' or 'MarkdownV2' for formatting\n- `disable_notification`: Send silently without notification sound\n- `reply_to_message_id`: Message ID to reply to\n\n**Pitfalls**:\n- Bot must be a member of the chat\u002Fgroup to send messages\n- MarkdownV2 requires escaping special characters: `_*[]()~>#+-=|{}.!`\n- HTML mode supports limited tags: `\u003Cb>`, `\u003Ci>`, `\u003Ccode>`, `\u003Cpre>`, `\u003Ca>`\n- Messages have a 4096 character limit; split longer content\n\n### 2. Send Photos and Documents\n\n**When to use**: User wants to share images or files in a Telegram chat\n\n**Tool sequence**:\n1. `TELEGRAM_SEND_PHOTO` - Send an image [Optional]\n2. `TELEGRAM_SEND_DOCUMENT` - Send a file\u002Fdocument [Optional]\n\n**Key parameters**:\n- `chat_id`: Target chat ID\n- `photo`: Photo URL or file_id (for SEND_PHOTO)\n- `document`: Document URL or file_id (for SEND_DOCUMENT)\n- `caption`: Optional caption for the media\n\n**Pitfalls**:\n- Photo captions have a 1024 character limit\n- Document captions also have a 1024 character limit\n- Files up to 50MB can be sent via bot API\n- Photos are compressed by Telegram; use SEND_DOCUMENT for uncompressed images\n\n### 3. Manage Chats\n\n**When to use**: User wants to get chat information or manage chat settings\n\n**Tool sequence**:\n1. `TELEGRAM_GET_CHAT` - Get detailed chat information [Required]\n2. `TELEGRAM_GET_CHAT_ADMINISTRATORS` - List chat admins [Optional]\n3. `TELEGRAM_GET_CHAT_MEMBERS_COUNT` - Get member count [Optional]\n4. `TELEGRAM_EXPORT_CHAT_INVITE_LINK` - Generate invite link [Optional]\n\n**Key parameters**:\n- `chat_id`: Target chat ID or username\n\n**Pitfalls**:\n- Bot must be an administrator to export invite links\n- GET_CHAT returns different fields for private chats vs groups vs channels\n- Member count may be approximate for very large groups\n- Admin list does not include regular members\n\n### 4. Edit and Delete Messages\n\n**When to use**: User wants to modify or remove previously sent messages\n\n**Tool sequence**:\n1. `TELEGRAM_EDIT_MESSAGE` - Edit a sent message [Optional]\n2. `TELEGRAM_DELETE_MESSAGE` - Delete a message [Optional]\n\n**Key parameters**:\n- `chat_id`: Chat where the message is located\n- `message_id`: ID of the message to edit or delete\n- `text`: New text content (for edit)\n\n**Pitfalls**:\n- Bots can only edit their own messages\n- Messages can only be deleted within 48 hours of sending\n- In groups, bots with delete permissions can delete any message\n- Editing a message removes its 'edited' timestamp history\n\n### 5. Forward Messages and Get Updates\n\n**When to use**: User wants to forward messages or retrieve recent updates\n\n**Tool sequence**:\n1. `TELEGRAM_FORWARD_MESSAGE` - Forward a message to another chat [Optional]\n2. `TELEGRAM_GET_UPDATES` - Get recent bot updates\u002Fmessages [Optional]\n3. `TELEGRAM_GET_CHAT_HISTORY` - Get chat message history [Optional]\n\n**Key parameters**:\n- `from_chat_id`: Source chat for forwarding\n- `chat_id`: Destination chat for forwarding\n- `message_id`: Message to forward\n- `offset`: Update offset for GET_UPDATES\n- `limit`: Number of updates to retrieve\n\n**Pitfalls**:\n- Forwarded messages show the original sender attribution\n- GET_UPDATES returns a limited window of recent updates\n- Chat history access may be limited by bot permissions and chat type\n- Use offset to avoid processing the same update twice\n\n### 6. Manage Bot Commands\n\n**When to use**: User wants to set or update bot command menu\n\n**Tool sequence**:\n1. `TELEGRAM_SET_MY_COMMANDS` - Set the bot's command list [Required]\n2. `TELEGRAM_ANSWER_CALLBACK_QUERY` - Respond to inline button presses [Optional]\n\n**Key parameters**:\n- `commands`: Array of command objects with `command` and `description`\n- `callback_query_id`: ID of the callback query to answer\n\n**Pitfalls**:\n- Commands must start with '\u002F' and be lowercase\n- Command descriptions have a 256 character limit\n- Callback queries must be answered within 10 seconds or they expire\n- Setting commands replaces the entire command list\n\n## Common Patterns\n\n### Chat ID Resolution\n\n**From username**:\n```\n1. Use '@username' format as chat_id (for public channels\u002Fgroups)\n2. For private chats, numeric chat_id is required\n3. Call GET_CHAT with username to retrieve numeric ID\n```\n\n**From GET_UPDATES**:\n```\n1. Call TELEGRAM_GET_UPDATES\n2. Extract chat.id from message objects\n3. Use numeric chat_id in subsequent calls\n```\n\n### Message Formatting\n\n- Use `parse_mode: 'HTML'` for `\u003Cb>bold\u003C\u002Fb>`, `\u003Ci>italic\u003C\u002Fi>`, `\u003Ccode>code\u003C\u002Fcode>`\n- Use `parse_mode: 'MarkdownV2'` for `*bold*`, `_italic_`, `` `code` ``\n- Escape special chars in MarkdownV2: `_ * [ ] ( ) ~ > # + - = | { } . !`\n- Omit parse_mode for plain text without formatting\n\n## Known Pitfalls\n\n**Bot Permissions**:\n- Bots must be added to groups\u002Fchannels to interact\n- Admin permissions needed for: deleting messages, exporting invite links, managing members\n- Bots cannot initiate conversations; users must start them first\n\n**Rate Limits**:\n- 30 messages per second to the same group\n- 20 messages per minute to the same user in groups\n- Bulk operations should implement delays between calls\n- API returns 429 Too Many Requests when limits are hit\n\n**Chat Types**:\n- Private chat: One-on-one with the bot\n- Group: Multi-user chat (bot must be added)\n- Supergroup: Enhanced group with admin features\n- Channel: Broadcast-only (bot must be admin to post)\n\n**Message Limits**:\n- Text messages: 4096 characters max\n- Captions: 1024 characters max\n- File uploads: 50MB max via bot API\n- Inline keyboard buttons: 8 per row\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Verify bot | TELEGRAM_GET_ME | (none) |\n| Send message | TELEGRAM_SEND_MESSAGE | chat_id, text, parse_mode |\n| Send photo | TELEGRAM_SEND_PHOTO | chat_id, photo, caption |\n| Send document | TELEGRAM_SEND_DOCUMENT | chat_id, document, caption |\n| Edit message | TELEGRAM_EDIT_MESSAGE | chat_id, message_id, text |\n| Delete message | TELEGRAM_DELETE_MESSAGE | chat_id, message_id |\n| Forward message | TELEGRAM_FORWARD_MESSAGE | chat_id, from_chat_id, message_id |\n| Get chat info | TELEGRAM_GET_CHAT | chat_id |\n| Get chat admins | TELEGRAM_GET_CHAT_ADMINISTRATORS | chat_id |\n| Get member count | TELEGRAM_GET_CHAT_MEMBERS_COUNT | chat_id |\n| Export invite link | TELEGRAM_EXPORT_CHAT_INVITE_LINK | chat_id |\n| Get updates | TELEGRAM_GET_UPDATES | offset, limit |\n| Get chat history | TELEGRAM_GET_CHAT_HISTORY | chat_id |\n| Set bot commands | TELEGRAM_SET_MY_COMMANDS | commands |\n| Answer callback | TELEGRAM_ANSWER_CALLBACK_QUERY | callback_query_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":48,"source":31,"requires":49,"description":7},"unknown",{"mcp":50},[51],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Ftelegram-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add reikiplanet\u002Fdaoskills --skill telegram-automation",{"tool":66,"command":67},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill telegram-automation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill telegram-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Ftelegram-automation\u002FSKILL.md",true,[],[75,101,113,128,148,171],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":43},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[82,83,84,85,86,87,31,88,89,90,91,92,93,94,95,96,97,98,99,100],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[108,109,99,110,111,31,89,90,91,85,112,86],"ar","vr ar","interaction","requirements","performance",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":43},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[115,120,121,122,123,124,31,125,91,126,127,85],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":43},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[135,136,137,138,139,31,140,141,142,143,125,144,145,146,147],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":43},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,31,91,85,163,86,164,165,166,167,168,169,170],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":43},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[178,179,180,181,182,183,184,185,168,125,186,187,188,31,189,190,191,165,192,193],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]