メニュー
Formats all Telegram bot replies to be short, scannable, and properly styled with MarkdownV2. Use when replying to Telegram messages via the Telegram MCP plugin — ensures bold, emojis, bullet points, and correct special character escaping.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
Competitor content gap analysis — extracts ALL comments from competitor and your own YouTube videos, identifies what audiences want but aren't getting, ranks gaps by engagement, and proposes video ideas. Use when the user says "scoop," "content gap," "analyze competitor videos," "what should my next video be about," "find content gaps," or "competitor analysis."
Create KPI docs, compensation structures, screening questions, and hiring templates for any contractor role. Use this skill whenever the user wants to hire someone, set KPIs, define compensation, create a job post, write screening questions, or build a hiring doc — for ANY role including community managers, YouTube managers, producers, marketers, developers, VAs, or any contractor. Also trigger when the user says "set KPI", "hiring doc", "job post", "comp structure", "screening questions", or "Fiverr post".
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific features.
| name | telegram-formatting |
| description | Formats all Telegram bot replies to be short, scannable, and properly styled with MarkdownV2. Use when replying to Telegram messages via the Telegram MCP plugin — ensures bold, emojis, bullet points, and correct special character escaping. |
Ensures every Telegram reply is short, concise, and mobile-friendly using MarkdownV2.
Apply this skill whenever replying via mcp__plugin_telegram_telegram__reply. Every reply must use format: "markdownv2".
| Rule | Requirement |
|---|---|
| Length | Under ~800 chars when possible |
| Format | Always set format: "markdownv2" |
| Structure | Emojis as section headers + bullet points |
| Emphasis | Bold key terms and outcomes |
| Tone | Direct, no filler, no preamble |
| Entity | Syntax |
|---|---|
| Bold | *bold text* |
| Italic | _italic text_ |
| Underline | __underline__ |
| Strikethrough | ~strikethrough~ |
| Spoiler | ||spoiler|| |
| Inline code | `code` |
| Pre block | ```pre``` |
| Link | [text](URL) |
| Bold italic | *_bold italic_* |
These characters MUST be escaped with \ when they appear outside formatting entities:
_ * [ ] ( ) ~ ` > # + - = | { } . !
| Context | What to escape |
|---|---|
| Plain text | All 18 special chars listed above |
Inside (...) of links | ) and \ only |
| Inside code/pre | ` and \ only |
Done! must be Done\!file.txt must be file\.txtA - B must be A \- Bkey=val must be key\=val(test) must be \(test\)✅ *Done\!* Brief outcome summary
📋 *What changed:*
• Item one
• Item two
⚡ *Next:* What happens now
| Don't | Do |
|---|---|
| Wall of text | Bullets with emoji headers |
| Repeat what user said | Jump to the answer |
| Plain text format | Always MarkdownV2 |
| Unescaped special chars | Escape every . ! - ( ) etc. |
| Long explanations | Max 3-5 bullet points per section |