@ngxtm/devkit 3.14.0 → 3.16.0

package/skills/tailwind-patterns/SKILL.md

@@ -1,13 +1,19 @@
 ---
 name: tailwind-patterns
-description: Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture.
+description: "Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture."
 allowed-tools: Read, Write, Edit, Glob, Grep
+risk: unknown
+source: community
 ---
 
 # Tailwind CSS Patterns (v4 - 2025)
 
 > Modern utility-first CSS with CSS-native configuration.
 
+## When to Use
+
+Use this skill when configuring Tailwind v4, using CSS-first theme and design tokens, or implementing container queries and modern Tailwind patterns.
+
 ---
 
 ## 1. Tailwind v4 Architecture

package/skills/tavily-web/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: tavily-web
-description: Web search, content extraction, crawling, and research capabilities using Tavily API
+description: "Web search, content extraction, crawling, and research capabilities using Tavily API"
+risk: unknown
+source: community
 ---
 
 # tavily-web

package/skills/tdd-orchestrator/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: tdd-orchestrator
-description: Master TDD orchestrator specializing in red-green-refactor
+description: "Master TDD orchestrator specializing in red-green-refactor"
   discipline, multi-agent workflow coordination, and comprehensive test-driven
   development practices. Enforces TDD best practices across teams with
   AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD
   implementation and governance.
 metadata:
   model: opus
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/tdd-workflow/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: tdd-workflow
-description: Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
+description: "Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle."
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash
+risk: unknown
+source: community
 ---
 
 # TDD Workflow
@@ -147,3 +149,6 @@ Every test follows:
 ---
 
 > **Remember:** The test is the specification. If you can't write a test, you don't understand the requirement.
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/tdd-workflows-tdd-cycle/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: tdd-workflows-tdd-cycle
 description: "Use when working with tdd workflows tdd cycle"
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/tdd-workflows-tdd-green/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: tdd-workflows-tdd-green
-description: Implement the minimal code needed to make failing tests pass in the TDD green phase.
+description: "Implement the minimal code needed to make failing tests pass in the TDD green phase."
+risk: unknown
+source: community
 ---
 
 # Green Phase: Simple function

package/skills/tdd-workflows-tdd-red/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: tdd-workflows-tdd-red
-description: Generate failing tests for the TDD red phase to define expected behavior and edge cases.
+description: "Generate failing tests for the TDD red phase to define expected behavior and edge cases."
+risk: unknown
+source: community
 ---
 
 Write comprehensive failing tests following TDD red phase principles.

package/skills/tdd-workflows-tdd-refactor/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: tdd-workflows-tdd-refactor
 description: "Use when working with tdd workflows tdd refactor"
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/team-collaboration-issue/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: team-collaboration-issue
 description: "You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an"
+risk: unknown
+source: community
 ---
 
 # GitHub Issue Resolution Expert

package/skills/team-collaboration-standup-notes/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: team-collaboration-standup-notes
 description: "You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns."
+risk: unknown
+source: community
 ---
 
 # Standup Notes Generator

package/skills/team-collaboration-standup-notes/resources/implementation-playbook.md

@@ -266,7 +266,7 @@ obsidian_get_recent_periodic_notes --period daily --limit 2 | \
 • Need staging database access for migration testing - @infra-team
 
 ## 📎 Links
-• [PR #789](link) | [JIRA Sprint Board](link)
+• PR #789 | JIRA Sprint Board
 ```
 
 **Thread-Based Standup:**
@@ -351,7 +351,7 @@ From standup notes, automatically extract:
 • Taking tomorrow afternoon off (dentist appointment) - Will post morning standup but limited availability after 12pm
 • Mobile responsiveness research doc started: [Link to Notion doc]
 
-📎 [Sprint Board](link) | [My Active PRs](link)
+📎 Sprint Board | My Active PRs
 ```
 
 ### Example 2: AI-Generated Standup from Git History
@@ -527,7 +527,7 @@ jira issues list --assignee currentUser() --status "In Progress"
 • Heads up: Deploying migration to staging at noon, expect ~10min downtime
 
 **🔗 Links**
-• [Active PRs](link) | [Sprint Board](link) | [Migration Runbook](link)
+• Active PRs | Sprint Board | Migration Runbook
 
 ---
 👀 = I've read this | 🤝 = I can help with something | 💬 = Reply in thread

package/skills/team-composition-analysis/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: team-composition-analysis
-description: This skill should be used when the user asks to "plan team
+description: "This skill should be used when the user asks to \\\"plan team"
   structure", "determine hiring needs", "design org chart", "calculate
   compensation", "plan equity allocation", or requests organizational design and
   headcount planning for a startup.
 metadata:
   version: 1.0.0
+risk: unknown
+source: community
 ---
 
 # Team Composition Analysis

package/skills/telegram-automation/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: telegram-automation
+description: "Automate Telegram tasks via Rube MCP (Composio): send messages, manage chats, share photos/documents, and handle bot commands. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Telegram Automation via Rube MCP
+
+Automate Telegram operations through Composio's Telegram toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Telegram connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+- Telegram Bot Token required (created via @BotFather)
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `telegram`
+3. If connection is not ACTIVE, follow the returned auth link to configure the Telegram bot
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Send Messages
+
+**When to use**: User wants to send text messages to a Telegram chat
+
+**Tool sequence**:
+1. `TELEGRAM_GET_ME` - Verify bot identity and connection [Prerequisite]
+2. `TELEGRAM_GET_CHAT` - Get chat details and verify access [Optional]
+3. `TELEGRAM_SEND_MESSAGE` - Send a text message [Required]
+
+**Key parameters**:
+- `chat_id`: Numeric chat ID or channel username (e.g., '@channelname')
+- `text`: Message text content
+- `parse_mode`: 'HTML' or 'MarkdownV2' for formatting
+- `disable_notification`: Send silently without notification sound
+- `reply_to_message_id`: Message ID to reply to
+
+**Pitfalls**:
+- Bot must be a member of the chat/group to send messages
+- MarkdownV2 requires escaping special characters: `_*[]()~>#+-=|{}.!`
+- HTML mode supports limited tags: `<b>`, `<i>`, `<code>`, `<pre>`, `<a>`
+- Messages have a 4096 character limit; split longer content
+
+### 2. Send Photos and Documents
+
+**When to use**: User wants to share images or files in a Telegram chat
+
+**Tool sequence**:
+1. `TELEGRAM_SEND_PHOTO` - Send an image [Optional]
+2. `TELEGRAM_SEND_DOCUMENT` - Send a file/document [Optional]
+
+**Key parameters**:
+- `chat_id`: Target chat ID
+- `photo`: Photo URL or file_id (for SEND_PHOTO)
+- `document`: Document URL or file_id (for SEND_DOCUMENT)
+- `caption`: Optional caption for the media
+
+**Pitfalls**:
+- Photo captions have a 1024 character limit
+- Document captions also have a 1024 character limit
+- Files up to 50MB can be sent via bot API
+- Photos are compressed by Telegram; use SEND_DOCUMENT for uncompressed images
+
+### 3. Manage Chats
+
+**When to use**: User wants to get chat information or manage chat settings
+
+**Tool sequence**:
+1. `TELEGRAM_GET_CHAT` - Get detailed chat information [Required]
+2. `TELEGRAM_GET_CHAT_ADMINISTRATORS` - List chat admins [Optional]
+3. `TELEGRAM_GET_CHAT_MEMBERS_COUNT` - Get member count [Optional]
+4. `TELEGRAM_EXPORT_CHAT_INVITE_LINK` - Generate invite link [Optional]
+
+**Key parameters**:
+- `chat_id`: Target chat ID or username
+
+**Pitfalls**:
+- Bot must be an administrator to export invite links
+- GET_CHAT returns different fields for private chats vs groups vs channels
+- Member count may be approximate for very large groups
+- Admin list does not include regular members
+
+### 4. Edit and Delete Messages
+
+**When to use**: User wants to modify or remove previously sent messages
+
+**Tool sequence**:
+1. `TELEGRAM_EDIT_MESSAGE` - Edit a sent message [Optional]
+2. `TELEGRAM_DELETE_MESSAGE` - Delete a message [Optional]
+
+**Key parameters**:
+- `chat_id`: Chat where the message is located
+- `message_id`: ID of the message to edit or delete
+- `text`: New text content (for edit)
+
+**Pitfalls**:
+- Bots can only edit their own messages
+- Messages can only be deleted within 48 hours of sending
+- In groups, bots with delete permissions can delete any message
+- Editing a message removes its 'edited' timestamp history
+
+### 5. Forward Messages and Get Updates
+
+**When to use**: User wants to forward messages or retrieve recent updates
+
+**Tool sequence**:
+1. `TELEGRAM_FORWARD_MESSAGE` - Forward a message to another chat [Optional]
+2. `TELEGRAM_GET_UPDATES` - Get recent bot updates/messages [Optional]
+3. `TELEGRAM_GET_CHAT_HISTORY` - Get chat message history [Optional]
+
+**Key parameters**:
+- `from_chat_id`: Source chat for forwarding
+- `chat_id`: Destination chat for forwarding
+- `message_id`: Message to forward
+- `offset`: Update offset for GET_UPDATES
+- `limit`: Number of updates to retrieve
+
+**Pitfalls**:
+- Forwarded messages show the original sender attribution
+- GET_UPDATES returns a limited window of recent updates
+- Chat history access may be limited by bot permissions and chat type
+- Use offset to avoid processing the same update twice
+
+### 6. Manage Bot Commands
+
+**When to use**: User wants to set or update bot command menu
+
+**Tool sequence**:
+1. `TELEGRAM_SET_MY_COMMANDS` - Set the bot's command list [Required]
+2. `TELEGRAM_ANSWER_CALLBACK_QUERY` - Respond to inline button presses [Optional]
+
+**Key parameters**:
+- `commands`: Array of command objects with `command` and `description`
+- `callback_query_id`: ID of the callback query to answer
+
+**Pitfalls**:
+- Commands must start with '/' and be lowercase
+- Command descriptions have a 256 character limit
+- Callback queries must be answered within 10 seconds or they expire
+- Setting commands replaces the entire command list
+
+## Common Patterns
+
+### Chat ID Resolution
+
+**From username**:
+```
+1. Use '@username' format as chat_id (for public channels/groups)
+2. For private chats, numeric chat_id is required
+3. Call GET_CHAT with username to retrieve numeric ID
+```
+
+**From GET_UPDATES**:
+```
+1. Call TELEGRAM_GET_UPDATES
+2. Extract chat.id from message objects
+3. Use numeric chat_id in subsequent calls
+```
+
+### Message Formatting
+
+- Use `parse_mode: 'HTML'` for `<b>bold</b>`, `<i>italic</i>`, `<code>code</code>`
+- Use `parse_mode: 'MarkdownV2'` for `*bold*`, `_italic_`, `` `code` ``
+- Escape special chars in MarkdownV2: `_ * [ ] ( ) ~ > # + - = | { } . !`
+- Omit parse_mode for plain text without formatting
+
+## Known Pitfalls
+
+**Bot Permissions**:
+- Bots must be added to groups/channels to interact
+- Admin permissions needed for: deleting messages, exporting invite links, managing members
+- Bots cannot initiate conversations; users must start them first
+
+**Rate Limits**:
+- 30 messages per second to the same group
+- 20 messages per minute to the same user in groups
+- Bulk operations should implement delays between calls
+- API returns 429 Too Many Requests when limits are hit
+
+**Chat Types**:
+- Private chat: One-on-one with the bot
+- Group: Multi-user chat (bot must be added)
+- Supergroup: Enhanced group with admin features
+- Channel: Broadcast-only (bot must be admin to post)
+
+**Message Limits**:
+- Text messages: 4096 characters max
+- Captions: 1024 characters max
+- File uploads: 50MB max via bot API
+- Inline keyboard buttons: 8 per row
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Verify bot | TELEGRAM_GET_ME | (none) |
+| Send message | TELEGRAM_SEND_MESSAGE | chat_id, text, parse_mode |
+| Send photo | TELEGRAM_SEND_PHOTO | chat_id, photo, caption |
+| Send document | TELEGRAM_SEND_DOCUMENT | chat_id, document, caption |
+| Edit message | TELEGRAM_EDIT_MESSAGE | chat_id, message_id, text |
+| Delete message | TELEGRAM_DELETE_MESSAGE | chat_id, message_id |
+| Forward message | TELEGRAM_FORWARD_MESSAGE | chat_id, from_chat_id, message_id |
+| Get chat info | TELEGRAM_GET_CHAT | chat_id |
+| Get chat admins | TELEGRAM_GET_CHAT_ADMINISTRATORS | chat_id |
+| Get member count | TELEGRAM_GET_CHAT_MEMBERS_COUNT | chat_id |
+| Export invite link | TELEGRAM_EXPORT_CHAT_INVITE_LINK | chat_id |
+| Get updates | TELEGRAM_GET_UPDATES | offset, limit |
+| Get chat history | TELEGRAM_GET_CHAT_HISTORY | chat_id |
+| Set bot commands | TELEGRAM_SET_MY_COMMANDS | commands |
+| Answer callback | TELEGRAM_ANSWER_CALLBACK_QUERY | callback_query_id |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/telegram-bot-builder/SKILL.md

@@ -1,7 +1,8 @@
 ---
 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."
+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 strategie..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Telegram Bot Builder
@@ -252,3 +253,6 @@ Quality over quantity.
 ## Related Skills
 
 Works well with: `telegram-mini-app`, `backend`, `ai-wrapper-product`, `workflow-automation`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/telegram-mini-app/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: telegram-mini-app
-description: "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app."
+description: "Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and build..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Telegram Mini App
@@ -277,3 +278,6 @@ Optimistic updates.
 ## Related Skills
 
 Works well with: `telegram-bot-builder`, `frontend`, `blockchain-defi`, `viral-generator-builder`
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/temporal-python-pro/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: temporal-python-pro
-description: Master Temporal workflow orchestration with Python SDK. Implements
+description: "Master Temporal workflow orchestration with Python SDK. Implements"
   durable workflows, saga patterns, and distributed transactions. Covers
   async/await, testing strategies, and production deployment. Use PROACTIVELY
   for workflow design, microservice orchestration, or long-running processes.
 metadata:
   model: inherit
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/skills/temporal-python-testing/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: temporal-python-testing
-description: Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
+description: "Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal wor..."
+risk: unknown
+source: community
 ---
 
 # Temporal Python Testing Strategies

package/skills/terraform-infrastructure/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: terraform-infrastructure
+description: "Terraform infrastructure as code workflow for provisioning cloud resources, creating reusable modules, and managing infrastructure at scale."
+source: personal
+risk: safe
+domain: cloud-devops
+category: granular-workflow-bundle
+version: 1.0.0
+---
+
+# Terraform Infrastructure Workflow
+
+## Overview
+
+Specialized workflow for infrastructure as code using Terraform including resource provisioning, module creation, state management, and multi-environment deployments.
+
+## When to Use This Workflow
+
+Use this workflow when:
+- Provisioning cloud infrastructure
+- Creating Terraform modules
+- Managing multi-environment infra
+- Implementing IaC best practices
+- Setting up Terraform workflows
+
+## Workflow Phases
+
+### Phase 1: Terraform Setup
+
+#### Skills to Invoke
+- `terraform-skill` - Terraform basics
+- `terraform-specialist` - Advanced Terraform
+
+#### Actions
+1. Initialize Terraform
+2. Configure backend
+3. Set up providers
+4. Configure variables
+5. Create outputs
+
+#### Copy-Paste Prompts
+```
+Use @terraform-skill to set up Terraform project
+```
+
+### Phase 2: Resource Provisioning
+
+#### Skills to Invoke
+- `terraform-module-library` - Terraform modules
+- `cloud-architect` - Cloud architecture
+
+#### Actions
+1. Design infrastructure
+2. Create resource definitions
+3. Configure networking
+4. Set up compute
+5. Add storage
+
+#### Copy-Paste Prompts
+```
+Use @terraform-module-library to provision cloud resources
+```
+
+### Phase 3: Module Creation
+
+#### Skills to Invoke
+- `terraform-module-library` - Module creation
+
+#### Actions
+1. Design module interface
+2. Create module structure
+3. Define variables/outputs
+4. Add documentation
+5. Test module
+
+#### Copy-Paste Prompts
+```
+Use @terraform-module-library to create reusable Terraform module
+```
+
+### Phase 4: State Management
+
+#### Skills to Invoke
+- `terraform-specialist` - State management
+
+#### Actions
+1. Configure remote backend
+2. Set up state locking
+3. Implement workspaces
+4. Configure state access
+5. Set up backup
+
+#### Copy-Paste Prompts
+```
+Use @terraform-specialist to configure Terraform state
+```
+
+### Phase 5: Multi-Environment
+
+#### Skills to Invoke
+- `terraform-specialist` - Multi-environment
+
+#### Actions
+1. Design environment structure
+2. Create environment configs
+3. Set up variable files
+4. Configure isolation
+5. Test deployments
+
+#### Copy-Paste Prompts
+```
+Use @terraform-specialist to set up multi-environment Terraform
+```
+
+### Phase 6: CI/CD Integration
+
+#### Skills to Invoke
+- `cicd-automation-workflow-automate` - CI/CD
+- `github-actions-templates` - GitHub Actions
+
+#### Actions
+1. Create CI pipeline
+2. Configure plan/apply
+3. Set up approvals
+4. Add validation
+5. Test pipeline
+
+#### Copy-Paste Prompts
+```
+Use @cicd-automation-workflow-automate to create Terraform CI/CD
+```
+
+### Phase 7: Security
+
+#### Skills to Invoke
+- `secrets-management` - Secrets management
+- `terraform-specialist` - Security
+
+#### Actions
+1. Configure secrets
+2. Set up encryption
+3. Implement policies
+4. Add compliance
+5. Audit access
+
+#### Copy-Paste Prompts
+```
+Use @secrets-management to secure Terraform secrets
+```
+
+## Quality Gates
+
+- [ ] Resources provisioned
+- [ ] Modules working
+- [ ] State configured
+- [ ] Multi-env tested
+- [ ] CI/CD working
+- [ ] Security verified
+
+## Related Workflow Bundles
+
+- `cloud-devops` - Cloud/DevOps
+- `kubernetes-deployment` - Kubernetes
+- `aws-infrastructure` - AWS specific

package/skills/terraform-module-library/SKILL.md

@@ -1,6 +1,8 @@
 ---
 name: terraform-module-library
-description: Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
+description: "Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, ..."
+risk: unknown
+source: community
 ---
 
 # Terraform Module Library