telegram-ads
01Plugin Claude Code
Telegram Ads plugin for Claude Code (local Playwright MCP, not a hosted server).
Plugin Claude Code
Telegram Ads plugin for Claude Code (local Playwright MCP, not a hosted server).
Plugin Claude Code
Operate ads.telegram.org from the agent: typed tools, Playwright login, read-only watcher. MCP is a local stdio process — not a hosted server.
Skill Claude CodeCodex
Operational end-to-end workflow for creating a new Telegram Ads campaign: estimate effective CPM, validate the draft via checkAdPost, save a server-side draft with screenshot, present an approval request, then submit createad with confirmationid. Use when the operator asks to 'create an ad', 'launch a campaign'…
Skill Claude CodeCodex
Operational format for Telegram Ads reports delivered to the operator: structure, sections, field conventions, currency notation, common tables, and the 'never say X' rules. Use whenever producing a Telegram Ads summary (snapshot, inspectad, accountdiagnosis, custom report) for the operator consumption. Pairs with…
Skill Claude CodeCodex
Operational workflow for handling Telegram Ads moderation outcomes: read rejection reason, classify the policy category, propose a policy-compliant rewrite of the creative, re-validate the rewrite, and submit the edit (or a fresh create) for re-review. Use when an ad is declined, when the operator asks 'why was it…
Skill Claude CodeCodex
An installation and setup procedure for a Telegram Ads watcher, a tool that regularly reads advertising-account data. It connects the watcher to Hermes in read-only mode and can perform separately approved checks against a real account.
Skill Claude CodeCodex
Operational workflow for inspecting and switching between Telegram Ads cabinets: status check, login state, list cabinets, select active account, read balance and recent transactions. Use when the operator asks to inspect/select/switch a cabinet, check login, view account balance, or 'which cabinet am I on'.
Skill Claude CodeCodex
Autonomous Telegram Ads growth operator — campaign research, validation, watcher, decision, and reporting loop.
Skill Claude CodeCodex
Operate ads.telegram.org through the typed telegramads tool layer: review cabinets and campaigns, snapshot accounts, prepare and validate ad drafts, analyze rejections, and run CPM / budget / start / stop / create / delete lifecycle actions through a strict human-approval flow. Use whenever the task involves Telegram…
Skill Claude CodeCodex
A planning and operations workflow for Telegram Ads campaigns promoting Telegram bots or channels. It covers ad text, targeting, bids, budgets, performance, rejected ads, and recommendations, with approval required for actions affecting live advertising.
Skill Claude CodeCodex
A skill for writing Telegram Ads copy that follows strict moderation and format rules, including a 160-character, single-line limit.
Skill Claude CodeCodex
Operational procedure for estimating the effective CPM of a Telegram Ads draft by stacking the UI-declared creative-option surcharges (showpicture +30%, custom emoji +50%, photo +50%, video +80%). Use when the operator asks 'how much will this ad really cost per 1000 views?', 'estimate CPM with modifiers', 'effective…
Skill Claude CodeCodex
Live operational pitfalls and confirmed happy path for creating Telegram Ads via typed telegramads tools (STARS/TON cabinets, channel placement tests, confirmation mint, post-create verification, watcher registration). Use when creating/submitting ads, debugging createad confirmation, prepareaddraft screenshots…
Skill Claude CodeCodex
Design and ship a Telegram Ads post-action watcher event-loop layer (V2/V3-style) on top of hermestelegramads.watcher — wrapper-not-duplicate discipline, closed-set envelopes, deny-all mutation guards, secret-redacted safe summaries, flag-off-by-default routing. Current state: V2.9 (shipped 2026-06-17, commit…
Skill Claude CodeCodex
Enable the in-process Telegram Ads watcher runtime on a live hermes-gateway- service. Pre-flight checks (clean tree + expected commits + env flags already applied), minimal systemd/env change, post-restart verification (PID, baseline tick, V1 login/session active, V2/V2.7 bridge loaded, mini-report route config…