@techwavedev/agi-agent-kit 1.3.5 → 1.4.2

package/templates/skills/extended/frontend/telegram-bot-builder/SKILL.md

@@ -1,290 +0,0 @@
----
-name: telegram-bot-builder
-description: "Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot."
-source: vibeship-spawner-skills (Apache 2.0)
----
-
-# Telegram Bot Builder
-
-**Role**: Telegram Bot Architect
-
-You build bots that people actually use daily. You understand that bots
-should feel like helpful assistants, not clunky interfaces. You know
-the Telegram ecosystem deeply - what's possible, what's popular, and
-what makes money. You design conversations that feel natural.
-
-## Capabilities
-
-- Telegram Bot API
-- Bot architecture
-- Command design
-- Inline keyboards
-- Bot monetization
-- User onboarding
-- Bot analytics
-- Webhook management
-
-## Patterns
-
-### Bot Architecture
-
-Structure for maintainable Telegram bots
-
-**When to use**: When starting a new bot project
-
-```python
-## Bot Architecture
-
-### Stack Options
-| Language | Library | Best For |
-|----------|---------|----------|
-| Node.js | telegraf | Most projects |
-| Node.js | grammY | TypeScript, modern |
-| Python | python-telegram-bot | Quick prototypes |
-| Python | aiogram | Async, scalable |
-
-### Basic Telegraf Setup
-```javascript
-import { Telegraf } from 'telegraf';
-
-const bot = new Telegraf(process.env.BOT_TOKEN);
-
-// Command handlers
-bot.start((ctx) => ctx.reply('Welcome!'));
-bot.help((ctx) => ctx.reply('How can I help?'));
-
-// Text handler
-bot.on('text', (ctx) => {
-  ctx.reply(`You said: ${ctx.message.text}`);
-});
-
-// Launch
-bot.launch();
-
-// Graceful shutdown
-process.once('SIGINT', () => bot.stop('SIGINT'));
-process.once('SIGTERM', () => bot.stop('SIGTERM'));
-```
-
-### Project Structure
-```
-telegram-bot/
-├── src/
-│   ├── bot.js           # Bot initialization
-│   ├── commands/        # Command handlers
-│   │   ├── start.js
-│   │   ├── help.js
-│   │   └── settings.js
-│   ├── handlers/        # Message handlers
-│   ├── keyboards/       # Inline keyboards
-│   ├── middleware/      # Auth, logging
-│   └── services/        # Business logic
-├── .env
-└── package.json
-```
-```
-
-### Inline Keyboards
-
-Interactive button interfaces
-
-**When to use**: When building interactive bot flows
-
-```python
-## Inline Keyboards
-
-### Basic Keyboard
-```javascript
-import { Markup } from 'telegraf';
-
-bot.command('menu', (ctx) => {
-  ctx.reply('Choose an option:', Markup.inlineKeyboard([
-    [Markup.button.callback('Option 1', 'opt_1')],
-    [Markup.button.callback('Option 2', 'opt_2')],
-    [
-      Markup.button.callback('Yes', 'yes'),
-      Markup.button.callback('No', 'no'),
-    ],
-  ]));
-});
-
-// Handle button clicks
-bot.action('opt_1', (ctx) => {
-  ctx.answerCbQuery('You chose Option 1');
-  ctx.editMessageText('You selected Option 1');
-});
-```
-
-### Keyboard Patterns
-| Pattern | Use Case |
-|---------|----------|
-| Single column | Simple menus |
-| Multi column | Yes/No, pagination |
-| Grid | Category selection |
-| URL buttons | Links, payments |
-
-### Pagination
-```javascript
-function getPaginatedKeyboard(items, page, perPage = 5) {
-  const start = page * perPage;
-  const pageItems = items.slice(start, start + perPage);
-
-  const buttons = pageItems.map(item =>
-    [Markup.button.callback(item.name, `item_${item.id}`)]
-  );
-
-  const nav = [];
-  if (page > 0) nav.push(Markup.button.callback('◀️', `page_${page-1}`));
-  if (start + perPage < items.length) nav.push(Markup.button.callback('▶️', `page_${page+1}`));
-
-  return Markup.inlineKeyboard([...buttons, nav]);
-}
-```
-```
-
-### Bot Monetization
-
-Making money from Telegram bots
-
-**When to use**: When planning bot revenue
-
-```javascript
-## Bot Monetization
-
-### Revenue Models
-| Model | Example | Complexity |
-|-------|---------|------------|
-| Freemium | Free basic, paid premium | Medium |
-| Subscription | Monthly access | Medium |
-| Per-use | Pay per action | Low |
-| Ads | Sponsored messages | Low |
-| Affiliate | Product recommendations | Low |
-
-### Telegram Payments
-```javascript
-// Create invoice
-bot.command('buy', (ctx) => {
-  ctx.replyWithInvoice({
-    title: 'Premium Access',
-    description: 'Unlock all features',
-    payload: 'premium_monthly',
-    provider_token: process.env.PAYMENT_TOKEN,
-    currency: 'USD',
-    prices: [{ label: 'Premium', amount: 999 }], // $9.99
-  });
-});
-
-// Handle successful payment
-bot.on('successful_payment', (ctx) => {
-  const payment = ctx.message.successful_payment;
-  // Activate premium for user
-  await activatePremium(ctx.from.id);
-  ctx.reply('🎉 Premium activated!');
-});
-```
-
-### Freemium Strategy
-```
-Free tier:
-- 10 uses per day
-- Basic features
-- Ads shown
-
-Premium ($5/month):
-- Unlimited uses
-- Advanced features
-- No ads
-- Priority support
-```
-
-### Usage Limits
-```javascript
-async function checkUsage(userId) {
-  const usage = await getUsage(userId);
-  const isPremium = await checkPremium(userId);
-
-  if (!isPremium && usage >= 10) {
-    return { allowed: false, message: 'Daily limit reached. Upgrade?' };
-  }
-  return { allowed: true };
-}
-```
-```
-
-## Anti-Patterns
-
-### ❌ Blocking Operations
-
-**Why bad**: Telegram has timeout limits.
-Users think bot is dead.
-Poor experience.
-Requests pile up.
-
-**Instead**: Acknowledge immediately.
-Process in background.
-Send update when done.
-Use typing indicator.
-
-### ❌ No Error Handling
-
-**Why bad**: Users get no response.
-Bot appears broken.
-Debugging nightmare.
-Lost trust.
-
-**Instead**: Global error handler.
-Graceful error messages.
-Log errors for debugging.
-Rate limiting.
-
-### ❌ Spammy Bot
-
-**Why bad**: Users block the bot.
-Telegram may ban.
-Annoying experience.
-Low retention.
-
-**Instead**: Respect user attention.
-Consolidate messages.
-Allow notification control.
-Quality over quantity.
-
-## Related Skills
-
-Works well with: `telegram-mini-app`, `backend`, `ai-wrapper-product`, `workflow-automation`
-
-
----
-
-## 🧠 AGI Framework Integration
-
-> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**
-> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)
-
-### Qdrant Memory Integration
-
-Before executing complex tasks with this skill:
-```bash
-python3 execution/memory_manager.py auto --query "<task summary>"
-```
-- **Cache hit?** Use cached response directly — no need to re-process.
-- **Memory match?** Inject `context_chunks` into your reasoning.
-- **No match?** Proceed normally, then store results:
-```bash
-python3 execution/memory_manager.py store \
-  --content "Description of what was decided/solved" \
-  --type decision \
-  --tags telegram-bot-builder <relevant-tags>
-```
-
-### Agent Team Collaboration
-
-- This skill can be invoked by the `orchestrator` agent via intelligent routing.
-- In **Agent Teams mode**, results are shared via Qdrant shared memory for cross-agent context.
-- In **Subagent mode**, this skill runs in isolation with its own memory namespace.
-
-### Local LLM Support
-
-When available, use local Ollama models for embedding and lightweight inference:
-- Embeddings: `nomic-embed-text` via Qdrant memory system
-- Lightweight analysis: Local models reduce API costs for repetitive patterns

package/templates/skills/extended/frontend/using-superpowers/SKILL.md

@@ -1,123 +0,0 @@
----
-name: using-superpowers
-description: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
----
-
-<EXTREMELY-IMPORTANT>
-If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
-
-IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
-
-This is not negotiable. This is not optional. You cannot rationalize your way out of this.
-</EXTREMELY-IMPORTANT>
-
-## How to Access Skills
-
-**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
-
-**In other environments:** Check your platform's documentation for how skills are loaded.
-
-# Using Skills
-
-## The Rule
-
-**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
-
-```dot
-digraph skill_flow {
-    "User message received" [shape=doublecircle];
-    "Might any skill apply?" [shape=diamond];
-    "Invoke Skill tool" [shape=box];
-    "Announce: 'Using [skill] to [purpose]'" [shape=box];
-    "Has checklist?" [shape=diamond];
-    "Create TodoWrite todo per item" [shape=box];
-    "Follow skill exactly" [shape=box];
-    "Respond (including clarifications)" [shape=doublecircle];
-
-    "User message received" -> "Might any skill apply?";
-    "Might any skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
-    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
-    "Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
-    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
-    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
-    "Has checklist?" -> "Follow skill exactly" [label="no"];
-    "Create TodoWrite todo per item" -> "Follow skill exactly";
-}
-```
-
-## Red Flags
-
-These thoughts mean STOP—you're rationalizing:
-
-| Thought | Reality |
-|---------|---------|
-| "This is just a simple question" | Questions are tasks. Check for skills. |
-| "I need more context first" | Skill check comes BEFORE clarifying questions. |
-| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
-| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
-| "Let me gather information first" | Skills tell you HOW to gather information. |
-| "This doesn't need a formal skill" | If a skill exists, use it. |
-| "I remember this skill" | Skills evolve. Read current version. |
-| "This doesn't count as a task" | Action = task. Check for skills. |
-| "The skill is overkill" | Simple things become complex. Use it. |
-| "I'll just do this one thing first" | Check BEFORE doing anything. |
-| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
-| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
-
-## Skill Priority
-
-When multiple skills could apply, use this order:
-
-1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
-2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution
-
-"Let's build X" → brainstorming first, then implementation skills.
-"Fix this bug" → debugging first, then domain-specific skills.
-
-## Skill Types
-
-**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.
-
-**Flexible** (patterns): Adapt principles to context.
-
-The skill itself tells you which.
-
-## User Instructions
-
-Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
-
-
----
-
-## 🧠 AGI Framework Integration
-
-> **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)**
-> Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills)
-
-### Qdrant Memory Integration
-
-Before executing complex tasks with this skill:
-```bash
-python3 execution/memory_manager.py auto --query "<task summary>"
-```
-- **Cache hit?** Use cached response directly — no need to re-process.
-- **Memory match?** Inject `context_chunks` into your reasoning.
-- **No match?** Proceed normally, then store results:
-```bash
-python3 execution/memory_manager.py store \
-  --content "Description of what was decided/solved" \
-  --type decision \
-  --tags using-superpowers <relevant-tags>
-```
-
-### Agent Team Collaboration
-
-- This skill can be invoked by the `orchestrator` agent via intelligent routing.
-- In **Agent Teams mode**, results are shared via Qdrant shared memory for cross-agent context.
-- In **Subagent mode**, this skill runs in isolation with its own memory namespace.
-
-### Local LLM Support
-
-When available, use local Ollama models for embedding and lightweight inference:
-- Embeddings: `nomic-embed-text` via Qdrant memory system
-- Lightweight analysis: Local models reduce API costs for repetitive patterns

package/templates/skills/extended/gaming/audio-transcriber/CHANGELOG.md

@@ -1,137 +0,0 @@
-# Changelog - audio-transcriber
-
-All notable changes to the audio-transcriber skill will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
----
-
-## [1.1.0] - 2026-02-03
-
-### ✨ Added
-
-- **Intelligent Prompt Workflow** (Step 3b) - Complete integration with prompt-engineer skill
-  - **Scenario A**: User-provided prompts are automatically improved with prompt-engineer
-    - Displays both original and improved versions side-by-side
-    - Single confirmation: "Usar versão melhorada? [s/n]"
-  - **Scenario B**: Auto-generation when no prompt provided
-    - Analyzes transcript and suggests document type (ata, resumo, notas)
-    - Shows suggestion and asks confirmation
-    - Generates complete structured prompt (RISEN/RODES/STAR)
-    - Shows preview and asks final confirmation
-    - Falls back to DEFAULT_MEETING_PROMPT if declined
-
-- **LLM Integration** - Process transcripts with Claude CLI or GitHub Copilot CLI
-  - Priority: Claude > GitHub Copilot > None (transcript-only mode)
-  - Step 0b: CLI detection logic documented
-  - Timeout handling (5 minutes default)
-  - Graceful fallback if CLI unavailable
-
-- **Progress Indicators** - Visual feedback during long operations
-  - `tqdm` progress bar for Whisper transcription segments
-  - `rich` spinner for LLM processing
-  - Clear status messages at each step
-
-- **Timestamp-based File Naming** - Avoid overwriting previous transcriptions
-  - Format: `transcript-YYYYMMDD-HHMMSS.md`
-  - Format: `ata-YYYYMMDD-HHMMSS.md`
-  - Prevents data loss from repeated runs
-
-- **Automatic Cleanup** - Remove temporary files after processing
-  - Deletes `metadata.json` and `transcription.json` automatically
-  - `--keep-temp` flag to preserve if needed
-  - Clean output directory
-
-- **Rich Terminal UI** - Beautiful output with `rich` library
-  - Formatted panels for prompt previews
-  - Color-coded status messages (green=success, yellow=warning, red=error)
-  - Spinner animations for long-running tasks
-
-- **Dual Output Support** - Generate both transcript and processed ata
-  - `transcript-*.md` - Raw transcription with timestamps
-  - `ata-*.md` - Intelligent summary/meeting minutes (if LLM available)
-  - User can decline LLM processing to get transcript-only
-
-### 🔧 Changed
-
-- **SKILL.md** - Major documentation updates
-  - Added Step 0b (CLI Detection)
-  - Updated Step 2 (Progress Indicators)
-  - Added Step 3b (Intelligent Prompt Workflow with 150+ lines)
-  - Updated version to 1.1.0
-  - Added detailed workflow diagrams for both scenarios
-
-- **install-requirements.sh** - Added UI libraries
-  - Now installs `tqdm` and `rich` packages
-  - Graceful fallback if installation fails
-  - Updated success messages
-
-- **Python Implementation** - Complete refactor
-  - Created `scripts/transcribe.py` (516 lines)
-  - Functions: `detect_cli_tool()`, `invoke_prompt_engineer()`, `handle_prompt_workflow()`, `process_with_llm()`, `transcribe_audio()`, `save_outputs()`, `cleanup_temp_files()`
-  - Command-line arguments: `--prompt`, `--model`, `--output-dir`, `--keep-temp`
-  - Auto-installs `rich` and `tqdm` if missing
-
-### 🐛 Fixed
-
-- **User prompts no longer ignored** - v1.0.0 completely ignored custom prompts
-  - Now processes all prompts (custom or auto-generated) with LLM
-  - Improves simple prompts into structured frameworks
-
-- **Temporary files cleanup** - v1.0.0 left `metadata.json` and `transcription.json` as trash
-  - Now automatically removed after processing
-  - Clean output directory
-
-- **File overwriting** - v1.0.0 used same filename (e.g., `meeting.md`) every time
-  - Now uses timestamp to prevent data loss
-  - Each run creates unique files
-
-- **Missing ata/summary** - v1.0.0 only generated raw transcript
-  - Now generates intelligent ata/resumo using LLM
-  - Respects user's prompt instructions
-
-- **No progress feedback** - v1.0.0 had silent processing (users didn't know if it froze)
-  - Now shows progress bar for transcription
-  - Shows spinner for LLM processing
-  - Clear status messages throughout
-
-### 📝 Notes
-
-- **Backward Compatibility:** Fully compatible with v1.0.0 workflows
-- **Requires:** Python 3.8+, faster-whisper OR whisper, tqdm, rich
-- **Optional:** Claude CLI or GitHub Copilot CLI for intelligent processing
-- **Optional:** prompt-engineer skill for automatic prompt generation
-
-### 🔗 Related Issues
-
-- Fixes #1: Prompt do usuário RISEN ignorado
-- Fixes #2: Arquivos temporários (metadata.json, transcription.json) deixados como lixo
-- Fixes #3: Output incompleto (apenas transcript RAW, sem ata)
-- Fixes #4: Falta de indicador de progresso visual
-- Fixes #5: Formato de saída sem timestamp
-
----
-
-## [1.0.0] - 2026-02-02
-
-### ✨ Initial Release
-
-- Audio transcription using Faster-Whisper or OpenAI Whisper
-- Automatic language detection
-- Speaker diarization (basic)
-- Voice Activity Detection (VAD)
-- Markdown output with metadata table
-- Installation script for dependencies
-- Example scripts for basic transcription
-- Support for multiple audio formats (MP3, WAV, M4A, OGG, FLAC, WEBM)
-- FFmpeg integration for format conversion
-- Zero-configuration philosophy
-
-### 📝 Known Limitations (Fixed in v1.1.0)
-
-- User prompts ignored (no LLM integration)
-- Only raw transcript generated (no ata/summary)
-- Temporary files not cleaned up
-- No progress indicators
-- Files overwritten on repeated runs