{"owner":"ebertti","repo":"awesome-telegram","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md","AGENTS.md"],"skills":{"CLAUDE.md":"# CLAUDE.md — Guidelines for AI Agents (awesome-telegram)\n\nThis file provides instructions for Claude and other AI agents when reviewing pull requests, evaluating contributions, or helping maintain this repository.\n\n---\n\n## Purpose of this list\n\nA curated collection of Telegram-related resources: bots, libraries, tools, groups, channels, and integrations. The key criterion is **relevance to Telegram** — not exclusivity. Multi-platform tools are welcome as long as they have meaningful Telegram support.\n\n---\n\n## Acceptance Criteria\n\n### ✅ Accept if:\n- The entry is related to Telegram in some way (bots, libraries, tools, integrations, channels, groups)\n- It has a valid link (t.me, GitHub, website, etc.)\n- The description is a single concise sentence\n- It follows the formatting rules below\n- It is placed at the bottom of the correct section\n\n### ⚠️ Request changes if:\n- The description is missing, vague, or marketing-heavy\n- The description is longer than one sentence\n- The format uses `-` instead of `–` (em dash)\n- The entry is not placed at the bottom of the relevant section\n- The PR title is \"Update README.md\" or similarly generic\n- A link is missing (ask for project page, t.me, or website)\n- The bot handle does not match the project branding\n\n### ❌ Close/Reject if:\n- The entry provides access to copyright-infringing content (e.g., unlicensed streaming links)\n- The entry is a crypto trading bot that requests API keys via Telegram (security risk)\n- The content appears to be self-promotion of paid/adult/gated content groups\n- The PR title explicitly violates contributing guidelines (e.g., \"Update README.md\" adding low-quality content)\n\n### Notes:\n- **Public source code is NOT required** — closed-source bots and tools are welcome\n- **Multi-platform tools are welcome** — if Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`\n- **Geographic niche is OK** — region-specific tools (e.g., alerts for a specific country) are acceptable\n\n---\n\n## Format Rules\n\n### Entry format:\n```\n* [Name](link) – Single sentence description.\n```\n\n- Use `–` (em dash, U+2013), not `-` (hyphen)\n- One entry per line\n- Add new entries at the **bottom** of the relevant section\n- No trailing punctuation style inconsistency — match the existing list style\n\n### For open-source entries, optionally link the source:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) Single sentence description.\n```\n\n---\n\n## Section Placement\n\n| Entry type | Section |\n|---|---|\n| Telegram bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Python libraries | `### Bot Libs > #### Python` |\n| JS/TS/Node libraries | `### Bot Libs > #### Javascript/Typescript/Node` |\n| Other language libraries | appropriate `### Bot Libs` subsection |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools (Telegram + others) | `## Multi-platform Tools` |\n| Telegram themes | `## Themes` |\n| Telegram groups | `## Groups` |\n| Telegram channels | `## Channels` |\n| Bot stores/directories | `## Bot Stores` or `## Telegram Directory` |\n| Security-focused channels | `## Security` |\n\n---\n\n## PR Review Checklist\n\nWhen reviewing a PR, check:\n\n1. [ ] Does the entry relate to Telegram?\n2. [ ] Is there a valid link?\n3. [ ] Is the description a single concise sentence?\n4. [ ] Does it use `–` (em dash)?\n5. [ ] Is it placed at the bottom of the correct section?\n6. [ ] Is the PR title meaningful (not \"Update README.md\")?\n7. [ ] Are there any copyright or safety concerns?\n8. [ ] If multi-platform, is it in `## Multi-platform Tools`?\n\n---\n\n## Suggested Comment Templates\n\n### Requesting a shorter description:\n> The description is a bit long for this list — each entry should be a single concise sentence.\n> Suggested: `* [Name](link) – <one sentence>.`\n\n### Requesting a link:\n> Could you add a link to the project page or website?\n\n### Requesting description clarity:\n> Could you update the description to explain what the bot/tool actually does in one sentence?\n\n### Closing for copyright:\n> This entry raises copyright concerns (e.g., provides unlicensed streaming or download links). We cannot include it.\n\n### Closing for safety:\n> Crypto trading bots that request API keys via Telegram raise safety concerns for our users. We cannot include this entry.\n\n","AGENTS.md":"# AGENTS.md — PR Review Rules for AI Agents\n\nThis file defines the rules that AI agents (automated reviewers, bots, Claude, etc.) should follow when evaluating pull requests to this repository.\n\n---\n\n## What this repository is\n\nA curated list of Telegram-related resources: bots, tools, libraries, channels, groups, and integrations.\n\n**The core criterion is: does this have a meaningful relation to Telegram?**\nMulti-platform tools are welcome. Closed-source projects are welcome. The entry just needs to be useful to someone in the Telegram ecosystem.\n\n---\n\n## Acceptance Rules\n\n### ✅ ACCEPT (or approve after minor fixes) if:\n\n- Entry is related to Telegram (can also support other platforms)\n- Has a valid link (t.me, GitHub, website, etc.)\n- Description is a single concise sentence\n- Uses em dash `–` (not hyphen `-`)\n- Added at the bottom of the correct section\n- PR title is descriptive (not \"Update README.md\")\n\n### ⚠️ REQUEST CHANGES if:\n\n| Issue | What to ask |\n|---|---|\n| Description is missing or vague | Ask for a one-sentence description of what it does |\n| Description is too long / marketing-heavy | Suggest a trimmed single-sentence version |\n| Uses `-` instead of `–` | Ask to replace with em dash |\n| No link provided | Ask for project page, t.me, or website |\n| Bot handle does not match branding | Ask to clarify / reconcile |\n| Wrong section placement | Point to the correct section |\n| Multi-platform tool placed in `## Tools` | Ask to move to `## Multi-platform Tools` |\n\n### ❌ CLOSE/REJECT if:\n\n| Reason | Example |\n|---|---|\n| Copyright-infringing content | Bot providing unlicensed streaming/download links |\n| Crypto trading bot requesting API keys | High risk of scam/phishing for users |\n| Self-promotion of paid/adult gated content | Private VIP content groups |\n| PR title is \"Update README.md\" AND content is low quality | Violates contributing guidelines |\n\n---\n\n## Format Reference\n\n```\n* [Name](https://link.to/project) – One sentence description.\n```\n\nWith open-source link:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) One sentence description.\n```\n\n---\n\n## Section Reference\n\n| What | Where |\n|---|---|\n| Bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Bot libraries (by language) | `### Bot Libs > #### <Language>` |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools with Telegram support | `## Multi-platform Tools` |\n| Themes | `## Themes` |\n| Groups | `## Groups` |\n| Channels | `## Channels` |\n| Bot stores / directories | `## Bot Stores` / `## Telegram Directory` |\n| Security channels | `## Security` |\n\n---\n\n## Important Notes\n\n- **Source code is NOT required.** Closed-source bots, tools, and services are accepted.\n- **Multi-platform is OK.** If Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`.\n- **Niche/regional tools are OK.** Location-specific tools (e.g., alerts for a specific country) are accepted.\n- **One PR = one entry.** Each PR should add a single entry to the list.\n- **New entries go at the bottom of their section.**\n\n"},"files":{"CLAUDE.md":"# CLAUDE.md — Guidelines for AI Agents (awesome-telegram)\n\nThis file provides instructions for Claude and other AI agents when reviewing pull requests, evaluating contributions, or helping maintain this repository.\n\n---\n\n## Purpose of this list\n\nA curated collection of Telegram-related resources: bots, libraries, tools, groups, channels, and integrations. The key criterion is **relevance to Telegram** — not exclusivity. Multi-platform tools are welcome as long as they have meaningful Telegram support.\n\n---\n\n## Acceptance Criteria\n\n### ✅ Accept if:\n- The entry is related to Telegram in some way (bots, libraries, tools, integrations, channels, groups)\n- It has a valid link (t.me, GitHub, website, etc.)\n- The description is a single concise sentence\n- It follows the formatting rules below\n- It is placed at the bottom of the correct section\n\n### ⚠️ Request changes if:\n- The description is missing, vague, or marketing-heavy\n- The description is longer than one sentence\n- The format uses `-` instead of `–` (em dash)\n- The entry is not placed at the bottom of the relevant section\n- The PR title is \"Update README.md\" or similarly generic\n- A link is missing (ask for project page, t.me, or website)\n- The bot handle does not match the project branding\n\n### ❌ Close/Reject if:\n- The entry provides access to copyright-infringing content (e.g., unlicensed streaming links)\n- The entry is a crypto trading bot that requests API keys via Telegram (security risk)\n- The content appears to be self-promotion of paid/adult/gated content groups\n- The PR title explicitly violates contributing guidelines (e.g., \"Update README.md\" adding low-quality content)\n\n### Notes:\n- **Public source code is NOT required** — closed-source bots and tools are welcome\n- **Multi-platform tools are welcome** — if Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`\n- **Geographic niche is OK** — region-specific tools (e.g., alerts for a specific country) are acceptable\n\n---\n\n## Format Rules\n\n### Entry format:\n```\n* [Name](link) – Single sentence description.\n```\n\n- Use `–` (em dash, U+2013), not `-` (hyphen)\n- One entry per line\n- Add new entries at the **bottom** of the relevant section\n- No trailing punctuation style inconsistency — match the existing list style\n\n### For open-source entries, optionally link the source:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) Single sentence description.\n```\n\n---\n\n## Section Placement\n\n| Entry type | Section |\n|---|---|\n| Telegram bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Python libraries | `### Bot Libs > #### Python` |\n| JS/TS/Node libraries | `### Bot Libs > #### Javascript/Typescript/Node` |\n| Other language libraries | appropriate `### Bot Libs` subsection |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools (Telegram + others) | `## Multi-platform Tools` |\n| Telegram themes | `## Themes` |\n| Telegram groups | `## Groups` |\n| Telegram channels | `## Channels` |\n| Bot stores/directories | `## Bot Stores` or `## Telegram Directory` |\n| Security-focused channels | `## Security` |\n\n---\n\n## PR Review Checklist\n\nWhen reviewing a PR, check:\n\n1. [ ] Does the entry relate to Telegram?\n2. [ ] Is there a valid link?\n3. [ ] Is the description a single concise sentence?\n4. [ ] Does it use `–` (em dash)?\n5. [ ] Is it placed at the bottom of the correct section?\n6. [ ] Is the PR title meaningful (not \"Update README.md\")?\n7. [ ] Are there any copyright or safety concerns?\n8. [ ] If multi-platform, is it in `## Multi-platform Tools`?\n\n---\n\n## Suggested Comment Templates\n\n### Requesting a shorter description:\n> The description is a bit long for this list — each entry should be a single concise sentence.\n> Suggested: `* [Name](link) – <one sentence>.`\n\n### Requesting a link:\n> Could you add a link to the project page or website?\n\n### Requesting description clarity:\n> Could you update the description to explain what the bot/tool actually does in one sentence?\n\n### Closing for copyright:\n> This entry raises copyright concerns (e.g., provides unlicensed streaming or download links). We cannot include it.\n\n### Closing for safety:\n> Crypto trading bots that request API keys via Telegram raise safety concerns for our users. We cannot include this entry.\n\n","AGENTS.md":"# AGENTS.md — PR Review Rules for AI Agents\n\nThis file defines the rules that AI agents (automated reviewers, bots, Claude, etc.) should follow when evaluating pull requests to this repository.\n\n---\n\n## What this repository is\n\nA curated list of Telegram-related resources: bots, tools, libraries, channels, groups, and integrations.\n\n**The core criterion is: does this have a meaningful relation to Telegram?**\nMulti-platform tools are welcome. Closed-source projects are welcome. The entry just needs to be useful to someone in the Telegram ecosystem.\n\n---\n\n## Acceptance Rules\n\n### ✅ ACCEPT (or approve after minor fixes) if:\n\n- Entry is related to Telegram (can also support other platforms)\n- Has a valid link (t.me, GitHub, website, etc.)\n- Description is a single concise sentence\n- Uses em dash `–` (not hyphen `-`)\n- Added at the bottom of the correct section\n- PR title is descriptive (not \"Update README.md\")\n\n### ⚠️ REQUEST CHANGES if:\n\n| Issue | What to ask |\n|---|---|\n| Description is missing or vague | Ask for a one-sentence description of what it does |\n| Description is too long / marketing-heavy | Suggest a trimmed single-sentence version |\n| Uses `-` instead of `–` | Ask to replace with em dash |\n| No link provided | Ask for project page, t.me, or website |\n| Bot handle does not match branding | Ask to clarify / reconcile |\n| Wrong section placement | Point to the correct section |\n| Multi-platform tool placed in `## Tools` | Ask to move to `## Multi-platform Tools` |\n\n### ❌ CLOSE/REJECT if:\n\n| Reason | Example |\n|---|---|\n| Copyright-infringing content | Bot providing unlicensed streaming/download links |\n| Crypto trading bot requesting API keys | High risk of scam/phishing for users |\n| Self-promotion of paid/adult gated content | Private VIP content groups |\n| PR title is \"Update README.md\" AND content is low quality | Violates contributing guidelines |\n\n---\n\n## Format Reference\n\n```\n* [Name](https://link.to/project) – One sentence description.\n```\n\nWith open-source link:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) One sentence description.\n```\n\n---\n\n## Section Reference\n\n| What | Where |\n|---|---|\n| Bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Bot libraries (by language) | `### Bot Libs > #### <Language>` |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools with Telegram support | `## Multi-platform Tools` |\n| Themes | `## Themes` |\n| Groups | `## Groups` |\n| Channels | `## Channels` |\n| Bot stores / directories | `## Bot Stores` / `## Telegram Directory` |\n| Security channels | `## Security` |\n\n---\n\n## Important Notes\n\n- **Source code is NOT required.** Closed-source bots, tools, and services are accepted.\n- **Multi-platform is OK.** If Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`.\n- **Niche/regional tools are OK.** Location-specific tools (e.g., alerts for a specific country) are accepted.\n- **One PR = one entry.** Each PR should add a single entry to the list.\n- **New entries go at the bottom of their section.**\n\n"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# CLAUDE.md — Guidelines for AI Agents (awesome-telegram)\n\nThis file provides instructions for Claude and other AI agents when reviewing pull requests, evaluating contributions, or helping maintain this repository.\n\n---\n\n## Purpose of this list\n\nA curated collection of Telegram-related resources: bots, libraries, tools, groups, channels, and integrations. The key criterion is **relevance to Telegram** — not exclusivity. Multi-platform tools are welcome as long as they have meaningful Telegram support.\n\n---\n\n## Acceptance Criteria\n\n### ✅ Accept if:\n- The entry is related to Telegram in some way (bots, libraries, tools, integrations, channels, groups)\n- It has a valid link (t.me, GitHub, website, etc.)\n- The description is a single concise sentence\n- It follows the formatting rules below\n- It is placed at the bottom of the correct section\n\n### ⚠️ Request changes if:\n- The description is missing, vague, or marketing-heavy\n- The description is longer than one sentence\n- The format uses `-` instead of `–` (em dash)\n- The entry is not placed at the bottom of the relevant section\n- The PR title is \"Update README.md\" or similarly generic\n- A link is missing (ask for project page, t.me, or website)\n- The bot handle does not match the project branding\n\n### ❌ Close/Reject if:\n- The entry provides access to copyright-infringing content (e.g., unlicensed streaming links)\n- The entry is a crypto trading bot that requests API keys via Telegram (security risk)\n- The content appears to be self-promotion of paid/adult/gated content groups\n- The PR title explicitly violates contributing guidelines (e.g., \"Update README.md\" adding low-quality content)\n\n### Notes:\n- **Public source code is NOT required** — closed-source bots and tools are welcome\n- **Multi-platform tools are welcome** — if Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`\n- **Geographic niche is OK** — region-specific tools (e.g., alerts for a specific country) are acceptable\n\n---\n\n## Format Rules\n\n### Entry format:\n```\n* [Name](link) – Single sentence description.\n```\n\n- Use `–` (em dash, U+2013), not `-` (hyphen)\n- One entry per line\n- Add new entries at the **bottom** of the relevant section\n- No trailing punctuation style inconsistency — match the existing list style\n\n### For open-source entries, optionally link the source:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) Single sentence description.\n```\n\n---\n\n## Section Placement\n\n| Entry type | Section |\n|---|---|\n| Telegram bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Python libraries | `### Bot Libs > #### Python` |\n| JS/TS/Node libraries | `### Bot Libs > #### Javascript/Typescript/Node` |\n| Other language libraries | appropriate `### Bot Libs` subsection |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools (Telegram + others) | `## Multi-platform Tools` |\n| Telegram themes | `## Themes` |\n| Telegram groups | `## Groups` |\n| Telegram channels | `## Channels` |\n| Bot stores/directories | `## Bot Stores` or `## Telegram Directory` |\n| Security-focused channels | `## Security` |\n\n---\n\n## PR Review Checklist\n\nWhen reviewing a PR, check:\n\n1. [ ] Does the entry relate to Telegram?\n2. [ ] Is there a valid link?\n3. [ ] Is the description a single concise sentence?\n4. [ ] Does it use `–` (em dash)?\n5. [ ] Is it placed at the bottom of the correct section?\n6. [ ] Is the PR title meaningful (not \"Update README.md\")?\n7. [ ] Are there any copyright or safety concerns?\n8. [ ] If multi-platform, is it in `## Multi-platform Tools`?\n\n---\n\n## Suggested Comment Templates\n\n### Requesting a shorter description:\n> The description is a bit long for this list — each entry should be a single concise sentence.\n> Suggested: `* [Name](link) – <one sentence>.`\n\n### Requesting a link:\n> Could you add a link to the project page or website?\n\n### Requesting description clarity:\n> Could you update the description to explain what the bot/tool actually does in one sentence?\n\n### Closing for copyright:\n> This entry raises copyright concerns (e.g., provides unlicensed streaming or download links). We cannot include it.\n\n### Closing for safety:\n> Crypto trading bots that request API keys via Telegram raise safety concerns for our users. We cannot include this entry.\n\n","category":"root","tokens":1084},{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS.md — PR Review Rules for AI Agents\n\nThis file defines the rules that AI agents (automated reviewers, bots, Claude, etc.) should follow when evaluating pull requests to this repository.\n\n---\n\n## What this repository is\n\nA curated list of Telegram-related resources: bots, tools, libraries, channels, groups, and integrations.\n\n**The core criterion is: does this have a meaningful relation to Telegram?**\nMulti-platform tools are welcome. Closed-source projects are welcome. The entry just needs to be useful to someone in the Telegram ecosystem.\n\n---\n\n## Acceptance Rules\n\n### ✅ ACCEPT (or approve after minor fixes) if:\n\n- Entry is related to Telegram (can also support other platforms)\n- Has a valid link (t.me, GitHub, website, etc.)\n- Description is a single concise sentence\n- Uses em dash `–` (not hyphen `-`)\n- Added at the bottom of the correct section\n- PR title is descriptive (not \"Update README.md\")\n\n### ⚠️ REQUEST CHANGES if:\n\n| Issue | What to ask |\n|---|---|\n| Description is missing or vague | Ask for a one-sentence description of what it does |\n| Description is too long / marketing-heavy | Suggest a trimmed single-sentence version |\n| Uses `-` instead of `–` | Ask to replace with em dash |\n| No link provided | Ask for project page, t.me, or website |\n| Bot handle does not match branding | Ask to clarify / reconcile |\n| Wrong section placement | Point to the correct section |\n| Multi-platform tool placed in `## Tools` | Ask to move to `## Multi-platform Tools` |\n\n### ❌ CLOSE/REJECT if:\n\n| Reason | Example |\n|---|---|\n| Copyright-infringing content | Bot providing unlicensed streaming/download links |\n| Crypto trading bot requesting API keys | High risk of scam/phishing for users |\n| Self-promotion of paid/adult gated content | Private VIP content groups |\n| PR title is \"Update README.md\" AND content is low quality | Violates contributing guidelines |\n\n---\n\n## Format Reference\n\n```\n* [Name](https://link.to/project) – One sentence description.\n```\n\nWith open-source link:\n```\n* [Name](https://t.me/botname) – [Open Source](https://github.com/user/repo) One sentence description.\n```\n\n---\n\n## Section Reference\n\n| What | Where |\n|---|---|\n| Bots | `## Bots` |\n| Inline bots | `### Inline Bots` |\n| Games | `### Games` |\n| Bot libraries (by language) | `### Bot Libs > #### <Language>` |\n| Telegram-specific tools | `## Tools` |\n| Multi-platform tools with Telegram support | `## Multi-platform Tools` |\n| Themes | `## Themes` |\n| Groups | `## Groups` |\n| Channels | `## Channels` |\n| Bot stores / directories | `## Bot Stores` / `## Telegram Directory` |\n| Security channels | `## Security` |\n\n---\n\n## Important Notes\n\n- **Source code is NOT required.** Closed-source bots, tools, and services are accepted.\n- **Multi-platform is OK.** If Telegram is one of several supported platforms, place the entry in `## Multi-platform Tools`.\n- **Niche/regional tools are OK.** Location-specific tools (e.g., alerts for a specific country) are accepted.\n- **One PR = one entry.** Each PR should add a single entry to the list.\n- **New entries go at the bottom of their section.**\n\n","category":"root","tokens":778}]}