skill-library-mcp 1.0.0

package/skills/youtube-summarizer/SKILL.md

@@ -0,0 +1,411 @@
+---
+name: youtube-summarizer
+description: "Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks"
+version: 1.2.1
+author: Eric Andrade
+created: 2025-02-01
+updated: 2026-02-04
+platforms: [github-copilot-cli, claude-code, codex]
+category: content
+tags: [video, summarization, transcription, youtube, content-analysis]
+risk: safe
+---
+
+# youtube-summarizer
+
+## Purpose
+
+This skill extracts transcripts from YouTube videos and generates comprehensive, verbose summaries using the STAR + R-I-S-E framework. It validates video availability, extracts transcripts using the `youtube-transcript-api` Python library, and produces detailed documentation capturing all insights, arguments, and key points.
+
+The skill is designed for users who need thorough content analysis and reference documentation from educational videos, lectures, tutorials, or informational content.
+
+## When to Use This Skill
+
+This skill should be used when:
+
+- User provides a YouTube video URL and wants a detailed summary
+- User needs to document video content for reference without rewatching
+- User wants to extract insights, key points, and arguments from educational content
+- User needs transcripts from YouTube videos for analysis
+- User asks to "summarize", "resume", or "extract content" from YouTube videos
+- User wants comprehensive documentation prioritizing completeness over brevity
+
+## Step 0: Discovery & Setup
+
+Before processing videos, validate the environment and dependencies:
+
+```bash
+# Check if youtube-transcript-api is installed
+python3 -c "import youtube_transcript_api" 2>/dev/null
+if [ $? -ne 0 ]; then
+    echo "⚠️  youtube-transcript-api not found"
+    # Offer to install
+fi
+
+# Check Python availability
+if ! command -v python3 &>/dev/null; then
+    echo "❌ Python 3 is required but not installed"
+    exit 1
+fi
+```
+
+**Ask the user if dependency is missing:**
+
+```
+youtube-transcript-api is required but not installed.
+
+Would you like to install it now?
+- [ ] Yes - Install with pip (pip install youtube-transcript-api)
+- [ ] No - I'll install it manually
+```
+
+**If user selects "Yes":**
+
+```bash
+pip install youtube-transcript-api
+```
+
+**Verify installation:**
+
+```bash
+python3 -c "import youtube_transcript_api; print('✅ youtube-transcript-api installed successfully')"
+```
+
+## Main Workflow
+
+### Progress Tracking Guidelines
+
+Throughout the workflow, display a visual progress gauge before each step to keep the user informed. The gauge format is:
+
+```bash
+echo "[████░░░░░░░░░░░░░░░░] 20% - Step 1/5: Validating URL"
+```
+
+**Format specifications:**
+- 20 characters wide (use █ for filled, ░ for empty)
+- Percentage increments: Step 1=20%, Step 2=40%, Step 3=60%, Step 4=80%, Step 5=100%
+- Step counter showing current/total (e.g., "Step 3/5")
+- Brief description of current phase
+
+**Display the initial status box before Step 1:**
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║     📹  YOUTUBE SUMMARIZER - Processing Video                ║
+╠══════════════════════════════════════════════════════════════╣
+║ → Step 1: Validating URL                 [IN PROGRESS]       ║
+║ ○ Step 2: Checking Availability                              ║
+║ ○ Step 3: Extracting Transcript                              ║
+║ ○ Step 4: Generating Summary                                 ║
+║ ○ Step 5: Formatting Output                                  ║
+╠══════════════════════════════════════════════════════════════╣
+║ Progress: ██████░░░░░░░░░░░░░░░░░░░░░░░░  20%               ║
+╚══════════════════════════════════════════════════════════════╝
+```
+
+### Step 1: Validate YouTube URL
+
+**Objective:** Extract video ID and validate URL format.
+
+**Supported URL Formats:**
+- `https://www.youtube.com/watch?v=VIDEO_ID`
+- `https://youtube.com/watch?v=VIDEO_ID`
+- `https://youtu.be/VIDEO_ID`
+- `https://m.youtube.com/watch?v=VIDEO_ID`
+
+**Actions:**
+
+```bash
+# Extract video ID using regex or URL parsing
+URL="$USER_PROVIDED_URL"
+
+# Pattern 1: youtube.com/watch?v=VIDEO_ID
+if echo "$URL" | grep -qE 'youtube\.com/watch\?v='; then
+    VIDEO_ID=$(echo "$URL" | sed -E 's/.*[?&]v=([^&]+).*/\1/')
+# Pattern 2: youtu.be/VIDEO_ID  
+elif echo "$URL" | grep -qE 'youtu\.be/'; then
+    VIDEO_ID=$(echo "$URL" | sed -E 's/.*youtu\.be\/([^?]+).*/\1/')
+else
+    echo "❌ Invalid YouTube URL format"
+    exit 1
+fi
+
+echo "📹 Video ID extracted: $VIDEO_ID"
+```
+
+**If URL is invalid:**
+
+```
+❌ Invalid YouTube URL
+
+Please provide a valid YouTube URL in one of these formats:
+- https://www.youtube.com/watch?v=VIDEO_ID
+- https://youtu.be/VIDEO_ID
+
+Example: https://www.youtube.com/watch?v=dQw4w9WgXcQ
+```
+
+### Step 2: Check Video & Transcript Availability
+
+**Progress:**
+```bash
+echo "[████████░░░░░░░░░░░░] 40% - Step 2/5: Checking Availability"
+```
+
+**Objective:** Verify video exists and transcript is accessible.
+
+**Actions:**
+
+```python
+from youtube_transcript_api import YouTubeTranscriptApi, TranscriptsDisabled, NoTranscriptFound
+import sys
+
+video_id = sys.argv[1]
+
+try:
+    # Get list of available transcripts
+    transcript_list = YouTubeTranscriptApi.list_transcripts(video_id)
+    
+    print(f"✅ Video accessible: {video_id}")
+    print("📝 Available transcripts:")
+    
+    for transcript in transcript_list:
+        print(f"  - {transcript.language} ({transcript.language_code})")
+        if transcript.is_generated:
+            print("    [Auto-generated]")
+    
+except TranscriptsDisabled:
+    print(f"❌ Transcripts are disabled for video {video_id}")
+    sys.exit(1)
+    
+except NoTranscriptFound:
+    print(f"❌ No transcript found for video {video_id}")
+    sys.exit(1)
+    
+except Exception as e:
+    print(f"❌ Error accessing video: {e}")
+    sys.exit(1)
+```
+
+**Error Handling:**
+
+| Error | Message | Action |
+|-------|---------|--------|
+| Video not found | "❌ Video does not exist or is private" | Ask user to verify URL |
+| Transcripts disabled | "❌ Transcripts are disabled for this video" | Cannot proceed |
+| No transcript available | "❌ No transcript found (not auto-generated or manually added)" | Cannot proceed |
+| Private/restricted video | "❌ Video is private or restricted" | Ask for public video |
+
+### Step 3: Extract Transcript
+
+**Progress:**
+```bash
+echo "[████████████░░░░░░░░] 60% - Step 3/5: Extracting Transcript"
+```
+
+**Objective:** Retrieve transcript in preferred language.
+
+**Actions:**
+
+```python
+from youtube_transcript_api import YouTubeTranscriptApi
+
+video_id = "VIDEO_ID"
+
+try:
+    # Try to get transcript in user's preferred language first
+    # Fall back to English if not available
+    transcript = YouTubeTranscriptApi.get_transcript(
+        video_id, 
+        languages=['pt', 'en']  # Prefer Portuguese, fallback to English
+    )
+    
+    # Combine transcript segments into full text
+    full_text = " ".join([entry['text'] for entry in transcript])
+    
+    # Get video metadata
+    from youtube_transcript_api import YouTubeTranscriptApi
+    transcript_list = YouTubeTranscriptApi.list_transcripts(video_id)
+    
+    print("✅ Transcript extracted successfully")
+    print(f"📊 Transcript length: {len(full_text)} characters")
+    
+    # Save to temporary file for processing
+    with open(f"/tmp/transcript_{video_id}.txt", "w") as f:
+        f.write(full_text)
+    
+except Exception as e:
+    print(f"❌ Error extracting transcript: {e}")
+    exit(1)
+```
+
+**Transcript Processing:**
+
+- Combine all transcript segments into coherent text
+- Preserve punctuation and formatting where available
+- Remove duplicate or overlapping segments (if auto-generated artifacts)
+- Store in temporary file for analysis
+
+### Step 4: Generate Comprehensive Summary
+
+**Progress:**
+```bash
+echo "[████████████████░░░░] 80% - Step 4/5: Generating Summary"
+```
+
+**Objective:** Apply enhanced STAR + R-I-S-E prompt to create detailed summary.
+
+**Prompt Applied:**
+
+Use the enhanced prompt from Phase 2 (STAR + R-I-S-E framework) with the extracted transcript as input.
+
+**Actions:**
+
+1. Load the full transcript text
+2. Apply the comprehensive summarization prompt
+3. Use AI model (Claude/GPT) to generate structured summary
+4. Ensure output follows the defined structure:
+   - Header with video metadata
+   - Executive synthesis
+   - Detailed section-by-section breakdown
+   - Key insights and conclusions
+   - Concepts and terminology
+   - Resources and references
+
+**Implementation:**
+
+```bash
+# Use the transcript file as input to the AI prompt
+TRANSCRIPT_FILE="/tmp/transcript_${VIDEO_ID}.txt"
+
+# The AI agent will:
+# 1. Read the transcript
+# 2. Apply the STAR + R-I-S-E summarization framework
+# 3. Generate comprehensive Markdown output
+# 4. Structure with headers, lists, and highlights
+
+Read "$TRANSCRIPT_FILE"  # Read transcript into context
+```
+
+Then apply the full summarization prompt (from enhanced version in Phase 2).
+
+### Step 5: Format and Present Output
+
+**Progress:**
+```bash
+echo "[████████████████████] 100% - Step 5/5: Formatting Output"
+```
+
+**Objective:** Deliver the summary in clean, well-structured Markdown.
+
+**Output Structure:**
+
+```markdown
+# [Video Title]
+
+**Canal:** [Channel Name]  
+**Duração:** [Duration]  
+**URL:** [https://youtube.com/watch?v=VIDEO_ID]  
+**Data de Publicação:** [Date if available]
+
+
+## 📝 Detailed Summary
+
+### [Topic 1]
+
+[Comprehensive explanation with examples, data, quotes...]
+
+#### [Subtopic 1.1]
+
+[Detailed breakdown...]
+
+### [Topic 2]
+
+[Continued detailed analysis...]
+
+
+## 📚 Concepts and Terminology
+
+- **[Term 1]:** [Definition and context]
+- **[Term 2]:** [Definition and context]
+
+
+## 📌 Conclusion
+
+[Final synthesis and takeaways]
+
+
+### **Example 2: Missing Dependency**
+
+**User Input:**
+```
+claude> summarize this youtube video https://youtu.be/abc123
+```
+
+**Skill Response:**
+
+```
+⚠️  youtube-transcript-api not installed
+
+This skill requires the Python library 'youtube-transcript-api'.
+
+Would you like me to install it now?
+- [ ] Yes - Install with pip
+- [ ] No - I'll install manually
+```
+
+**User selects "Yes":**
+
+```bash
+$ pip install youtube-transcript-api
+Successfully installed youtube-transcript-api-0.6.1
+
+✅ Installation complete! Proceeding with video summary...
+```
+
+
+### **Example 4: Invalid URL**
+
+**User Input:**
+```
+claude> summarize youtube video www.youtube.com/some-video
+```
+
+**Skill Response:**
+
+```
+❌ Invalid YouTube URL format
+
+Expected format examples:
+- https://www.youtube.com/watch?v=VIDEO_ID
+- https://youtu.be/VIDEO_ID
+
+Please provide a valid YouTube video URL.
+```
+
+
+## 📊 Executive Summary
+
+This video provides a comprehensive introduction to the fundamental concepts of Artificial Intelligence (AI), designed for beginners and professionals who want to understand the technical foundations and practical applications of modern AI. The instructor covers everything from basic definitions to machine learning algorithms, using practical examples and visualizations to facilitate understanding.
+
+[... continued detailed summary ...]
+```
+
+**Save Options:**
+
+```
+What would you like to save?
+→ Summary + raw transcript
+
+✅ File saved: resumo-exemplo123-2026-02-01.md (includes raw transcript)
+[████████████████████] 100% - ✓ Processing complete!
+```
+
+
+Welcome to this comprehensive tutorial on machine learning fundamentals. In today's video, we'll explore the core concepts that power modern AI systems...
+```
+
+
+**Version:** 1.2.0
+**Last Updated:** 2026-02-02
+**Maintained By:** Eric Andrade

package/skills/zapier-make-patterns/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: zapier-make-patterns
+description: "No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power "
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# Zapier & Make Patterns
+
+You are a no-code automation architect who has built thousands of Zaps and
+Scenarios for businesses of all sizes. You've seen automations that save
+companies 40% of their time, and you've debugged disasters where bad data
+flowed through 12 connected apps.
+
+Your core insight: No-code is powerful but not unlimited. You know exactly
+when a workflow belongs in Zapier (simple, fast, maximum integrations),
+when it belongs in Make (complex branching, data transformation, budget),
+and when it needs to g
+
+## Capabilities
+
+- zapier
+- make
+- integromat
+- no-code-automation
+- zaps
+- scenarios
+- workflow-builders
+- business-process-automation
+
+## Patterns
+
+### Basic Trigger-Action Pattern
+
+Single trigger leads to one or more actions
+
+### Multi-Step Sequential Pattern
+
+Chain of actions executed in order
+
+### Conditional Branching Pattern
+
+Different actions based on conditions
+
+## Anti-Patterns
+
+### ❌ Text in Dropdown Fields
+
+### ❌ No Error Handling
+
+### ❌ Hardcoded Values
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Issue | critical | # ALWAYS use dropdowns to select, don't type |
+| Issue | critical | # Prevention: |
+| Issue | high | # Understand the math: |
+| Issue | high | # When a Zap breaks after app update: |
+| Issue | high | # Immediate fix: |
+| Issue | medium | # Handle duplicates: |
+| Issue | medium | # Understand operation counting: |
+| Issue | medium | # Best practices: |
+
+## Related Skills
+
+Works well with: `workflow-automation`, `agent-tool-builder`, `backend`, `api-designer`

package/skills/zendesk-automation/SKILL.md

@@ -0,0 +1,215 @@
+---
+name: zendesk-automation
+description: "Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Zendesk Automation via Rube MCP
+
+Automate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## 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 `zendesk`
+3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Search Tickets
+
+**When to use**: User wants to view, filter, or search support tickets
+
+**Tool sequence**:
+1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]
+2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]
+
+**Key parameters**:
+- `page`: Page number (1-based)
+- `per_page`: Results per page (max 100)
+- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')
+- `sort_order`: 'asc' or 'desc'
+- `ticket_id`: Ticket ID for single retrieval
+
+**Pitfalls**:
+- LIST uses `page`/`per_page` pagination, NOT offset-based; check `next_page` in response
+- Maximum 100 results per page; iterate with page numbers until `next_page` is null
+- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'
+- Ticket comments and audits are included in GET_BY_ID but not in LIST responses
+
+### 2. Create and Update Tickets
+
+**When to use**: User wants to create new tickets or modify existing ones
+
+**Tool sequence**:
+1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester/assignee [Prerequisite]
+2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]
+3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]
+4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]
+
+**Key parameters**:
+- `subject`: Ticket subject line
+- `description`: Ticket body (for creation; becomes first comment)
+- `priority`: 'urgent', 'high', 'normal', 'low'
+- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'
+- `type`: 'problem', 'incident', 'question', 'task'
+- `assignee_id`: Agent user ID to assign
+- `requester_id`: Requester user ID
+- `tags`: Array of tag strings
+- `ticket_id`: Ticket ID (for update/delete)
+
+**Pitfalls**:
+- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them
+- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts
+- DELETE is permanent and irreversible; tickets cannot be recovered
+- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation
+- Closed tickets cannot be updated; create a follow-up ticket instead
+
+### 3. Reply to Tickets
+
+**When to use**: User wants to add comments or replies to tickets
+
+**Tool sequence**:
+1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]
+2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply/comment [Required]
+
+**Key parameters**:
+- `ticket_id`: Ticket ID to reply to
+- `body`: Reply text content
+- `public`: Boolean; true for public reply, false for internal note
+- `author_id`: Author user ID (defaults to authenticated user)
+
+**Pitfalls**:
+- Set `public: false` for internal notes visible only to agents
+- Default is public reply which sends email to requester
+- HTML is supported in body text
+- Replying can also update ticket status simultaneously
+
+### 4. Manage Users
+
+**When to use**: User wants to find or create Zendesk users (agents, end-users)
+
+**Tool sequence**:
+1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]
+2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]
+3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]
+
+**Key parameters**:
+- `query`: Search string (matches name, email, phone, etc.)
+- `name`: User's full name (required for creation)
+- `email`: User's email address
+- `role`: 'end-user', 'agent', or 'admin'
+- `verified`: Whether email is verified
+
+**Pitfalls**:
+- User search is fuzzy; may return partial matches
+- Creating a user with an existing email returns the existing user (upsert behavior)
+- Agent and admin roles may require specific plan features
+
+### 5. Manage Organizations
+
+**When to use**: User wants to list, create, or manage organizations
+
+**Tool sequence**:
+1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]
+2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]
+3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]
+4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]
+5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]
+
+**Key parameters**:
+- `name`: Organization name (unique, required for creation)
+- `organization_id`: Organization ID for get/update
+- `details`: Organization details text
+- `notes`: Internal notes
+- `domain_names`: Array of associated domains
+- `tags`: Array of tag strings
+
+**Pitfalls**:
+- Organization names must be unique; duplicate names cause creation errors
+- Tags on UPDATE REPLACE existing tags (same behavior as tickets)
+- Domain names can be used for automatic user association
+
+## Common Patterns
+
+### Pagination
+
+**List endpoints**:
+- Use `page` (1-based) and `per_page` (max 100)
+- Check `next_page` URL in response; null means last page
+- `count` field gives total results
+
+### Ticket Lifecycle
+
+```
+new -> open -> pending -> solved -> closed
+                  |          ^
+                  v          |
+                hold --------+
+```
+
+- `new`: Unassigned ticket
+- `open`: Assigned, being worked on
+- `pending`: Waiting for customer response
+- `hold`: Waiting for internal action
+- `solved`: Resolved, can be reopened
+- `closed`: Permanently closed, cannot be modified
+
+### User Search for Assignment
+
+```
+1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)
+2. Extract user ID from results
+3. Use user ID as assignee_id in ticket creation/update
+```
+
+## Known Pitfalls
+
+**Tags Behavior**:
+- Tags on update REPLACE all existing tags
+- Always fetch current tags first and merge before updating
+- Tags are lowercase, no spaces (use underscores)
+
+**Safe Updates**:
+- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts
+- Returns 409 if ticket was modified since the stamp
+
+**Deletion**:
+- Ticket deletion is permanent and irreversible
+- Consider setting status to 'closed' instead of deleting
+- Deleted tickets cannot be recovered via API
+
+**Rate Limits**:
+- Default: 400 requests per minute
+- Varies by plan tier
+- 429 responses include Retry-After header
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |
+| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |
+| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |
+| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |
+| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |
+| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |
+| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |
+| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |
+| My profile | ZENDESK_GET_ABOUT_ME | (none) |
+| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |
+| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |
+| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |
+| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |
+| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |