npm - @caddis/cli - Versions diffs - 0.4.10 → 0.4.12 - Mend

@caddis/cli 0.4.10 → 0.4.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (73) hide show

package/bundles/antigravity-plugin-extras/skills/lead-research-assistant/SKILL.md DELETED Viewed

@@ -1,200 +0,0 @@
----
-name: lead-research-assistant
-context: fork
-description: Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
----
-# Lead Research Assistant
-This skill helps you identify and qualify potential leads for your business by analyzing your product/service, understanding your ideal customer profile, and providing actionable outreach strategies.
-## When to Use This Skill
-- Finding potential customers or clients for your product/service
-- Building a list of companies to reach out to for partnerships
-- Identifying target accounts for sales outreach
-- Researching companies that match your ideal customer profile
-- Preparing for business development activities
-## What This Skill Does
-1. **Understands Your Business**: Analyzes your product/service, value proposition, and target market
-2. **Identifies Target Companies**: Finds companies that match your ideal customer profile based on:
-   - Industry and sector
-   - Company size and location
-   - Technology stack and tools they use
-   - Growth stage and funding
-   - Pain points your product solves
-3. **Prioritizes Leads**: Ranks companies based on fit score and relevance
-4. **Provides Contact Strategies**: Suggests how to approach each lead with personalized messaging
-5. **Enriches Data**: Gathers relevant information about decision-makers and company context
-## How to Use
-### Basic Usage
-Simply describe your product/service and what you're looking for:
-```
-I'm building [product description]. Find me 10 companies in [location/industry]
-that would be good leads for this.
-```
-### With Your Codebase
-For even better results, run this from your product's source code directory:
-```
-Look at what I'm building in this repository and identify the top 10 companies
-in [location/industry] that would benefit from this product.
-```
-### Advanced Usage
-For more targeted research:
-```
-My product: [description]
-Ideal customer profile:
-- Industry: [industry]
-- Company size: [size range]
-- Location: [location]
-- Current pain points: [pain points]
-- Technologies they use: [tech stack]
-Find me 20 qualified leads with contact strategies for each.
-```
-## Instructions
-When a user requests lead research:
-1. **Understand the Product/Service**
-   - If in a code directory, analyze the codebase to understand the product
-   - Ask clarifying questions about the value proposition
-   - Identify key features and benefits
-   - Understand what problems it solves
-2. **Define Ideal Customer Profile**
-   - Determine target industries and sectors
-   - Identify company size ranges
-   - Consider geographic preferences
-   - Understand relevant pain points
-   - Note any technology requirements
-3. **Research and Identify Leads**
-   - Search for companies matching the criteria
-   - Look for signals of need (job postings, tech stack, recent news)
-   - Consider growth indicators (funding, expansion, hiring)
-   - Identify companies with complementary products/services
-   - Check for budget indicators
-4. **Prioritize and Score**
-   - Create a fit score (1-10) for each lead
-   - Consider factors like:
-     - Alignment with ICP
-     - Signals of immediate need
-     - Budget availability
-     - Competitive landscape
-     - Timing indicators
-5. **Provide Actionable Output**
-   For each lead, provide:
-   - **Company Name** and website
-   - **Why They're a Good Fit**: Specific reasons based on their business
-   - **Priority Score**: 1-10 with explanation
-   - **Decision Maker**: Role/title to target (e.g., "VP of Engineering")
-   - **Contact Strategy**: Personalized approach suggestions
-   - **Value Proposition**: How your product solves their specific problem
-   - **Conversation Starters**: Specific points to mention in outreach
-   - **LinkedIn URL**: If available, for easy connection
-6. **Format the Output**
-   Present results in a clear, scannable format:
-   ```markdown
-   # Lead Research Results
-   ## Summary
-   - Total leads found: [X]
-   - High priority (8-10): [X]
-   - Medium priority (5-7): [X]
-   - Average fit score: [X]
-   ---
-   ## Lead 1: [Company Name]
-   **Website**: [URL]
-   **Priority Score**: [X/10]
-   **Industry**: [Industry]
-   **Size**: [Employee count/revenue range]
-   **Why They're a Good Fit**:
-   [2-3 specific reasons based on their business]
-   **Target Decision Maker**: [Role/Title]
-   **LinkedIn**: [URL if available]
-   **Value Proposition for Them**:
-   [Specific benefit for this company]
-   **Outreach Strategy**:
-   [Personalized approach - mention specific pain points, recent company news, or relevant context]
-   **Conversation Starters**:
-   - [Specific point 1]
-   - [Specific point 2]
-   ---
-   [Repeat for each lead]
-   ```
-7. **Offer Next Steps**
-   - Suggest saving results to a CSV for CRM import
-   - Offer to draft personalized outreach messages
-   - Recommend prioritization based on timing
-   - Suggest follow-up research for top leads
-## Examples
-### Example 1: From Lenny's Newsletter
-**User**: "I'm building a tool that masks sensitive data in AI coding assistant queries. Find potential leads."
-**Output**: Creates a prioritized list of companies that:
-- Use AI coding assistants (Copilot, Cursor, etc.)
-- Handle sensitive data (fintech, healthcare, legal)
-- Have evidence in their GitHub repos of using coding agents
-- May have accidentally exposed sensitive data in code
-- Includes LinkedIn URLs of relevant decision-makers
-### Example 2: Local Business
-**User**: "I run a consulting practice for remote team productivity. Find me 10 companies in the Bay Area that recently went remote."
-**Output**: Identifies companies that:
-- Recently posted remote job listings
-- Announced remote-first policies
-- Are hiring distributed teams
-- Show signs of remote work challenges
-- Provides personalized outreach strategies for each
-## Tips for Best Results
-- **Be specific** about your product and its unique value
-- **Run from your codebase** if applicable for automatic context
-- **Provide context** about your ideal customer profile
-- **Specify constraints** like industry, location, or company size
-- **Request follow-up** research on promising leads for deeper insights
-## Related Use Cases
-- Drafting personalized outreach emails after identifying leads
-- Building a CRM-ready CSV of qualified prospects
-- Researching specific companies in detail
-- Analyzing competitor customer bases
-- Identifying partnership opportunities

package/bundles/antigravity-plugin-extras/skills/meeting-insights-analyzer/SKILL.md DELETED Viewed

@@ -1,328 +0,0 @@
----
-name: meeting-insights-analyzer
-context: fork
-description: Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
----
-# Meeting Insights Analyzer
-This skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.
-## When to Use This Skill
-- Analyzing your communication patterns across multiple meetings
-- Getting feedback on your leadership and facilitation style
-- Identifying when you avoid difficult conversations
-- Understanding your speaking habits and filler words
-- Tracking improvement in communication skills over time
-- Preparing for performance reviews with concrete examples
-- Coaching team members on their communication style
-## What This Skill Does
-1. **Pattern Recognition**: Identifies recurring behaviors across meetings like:
-   - Conflict avoidance or indirect communication
-   - Speaking ratios and turn-taking
-   - Question-asking vs. statement-making patterns
-   - Active listening indicators
-   - Decision-making approaches
-2. **Communication Analysis**: Evaluates communication effectiveness:
-   - Clarity and directness
-   - Use of filler words and hedging language
-   - Tone and sentiment patterns
-   - Meeting control and facilitation
-3. **Actionable Feedback**: Provides specific, timestamped examples with:
-   - What happened
-   - Why it matters
-   - How to improve
-4. **Trend Tracking**: Compares patterns over time when analyzing multiple meetings
-## How to Use
-### Basic Setup
-1. Download your meeting transcripts to a folder (e.g., `~/meetings/`)
-2. Navigate to that folder in Claude Code
-3. Ask for the analysis you want
-### Quick Start Examples
-```
-Analyze all meetings in this folder and tell me when I avoided conflict.
-```
-```
-Look at my meetings from the past month and identify my communication patterns.
-```
-```
-Compare my facilitation style between these two meeting folders.
-```
-### Advanced Analysis
-```
-Analyze all transcripts in this folder and:
-1. Identify when I interrupted others
-2. Calculate my speaking ratio
-3. Find moments I avoided giving direct feedback
-4. Track my use of filler words
-5. Show examples of good active listening
-```
-## Instructions
-When a user requests meeting analysis:
-1. **Discover Available Data**
-   - Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)
-   - Check if files contain speaker labels and timestamps
-   - Confirm the date range of meetings
-   - Identify the user's name/identifier in transcripts
-2. **Clarify Analysis Goals**
-   If not specified, ask what they want to learn:
-   - Specific behaviors (conflict avoidance, interruptions, filler words)
-   - Communication effectiveness (clarity, directness, listening)
-   - Meeting facilitation skills
-   - Speaking patterns and ratios
-   - Growth areas for improvement
-3. **Analyze Patterns**
-   For each requested insight:
-   **Conflict Avoidance**:
-   - Look for hedging language ("maybe", "kind of", "I think")
-   - Indirect phrasing instead of direct requests
-   - Changing subject when tension arises
-   - Agreeing without commitment ("yeah, but...")
-   - Not addressing obvious problems
-   **Speaking Ratios**:
-   - Calculate percentage of meeting spent speaking
-   - Count interruptions (by and of the user)
-   - Measure average speaking turn length
-   - Track question vs. statement ratios
-   **Filler Words**:
-   - Count "um", "uh", "like", "you know", "actually", etc.
-   - Note frequency per minute or per speaking turn
-   - Identify situations where they increase (nervous, uncertain)
-   **Active Listening**:
-   - Questions that reference others' previous points
-   - Paraphrasing or summarizing others' ideas
-   - Building on others' contributions
-   - Asking clarifying questions
-   **Leadership & Facilitation**:
-   - Decision-making approach (directive vs. collaborative)
-   - How disagreements are handled
-   - Inclusion of quieter participants
-   - Time management and agenda control
-   - Follow-up and action item clarity
-4. **Provide Specific Examples**
-   For each pattern found, include:
-   ```markdown
-   ### [Pattern Name]
-   **Finding**: [One-sentence summary of the pattern]
-   **Frequency**: [X times across Y meetings]
-   **Examples**:
-   1. **[Meeting Name/Date]** - [Timestamp]
-      **What Happened**:
-      > [Actual quote from transcript]
-      **Why This Matters**:
-      [Explanation of the impact or missed opportunity]
-      **Better Approach**:
-      [Specific alternative phrasing or behavior]
-   [Repeat for 2-3 strongest examples]
-   ```
-5. **Synthesize Insights**
-   After analyzing all patterns, provide:
-   ```markdown
-   # Meeting Insights Summary
-   **Analysis Period**: [Date range]
-   **Meetings Analyzed**: [X meetings]
-   **Total Duration**: [X hours]
-   ## Key Patterns Identified
-   ### 1. [Primary Pattern]
-   - **Observed**: [What you saw]
-   - **Impact**: [Why it matters]
-   - **Recommendation**: [How to improve]
-   ### 2. [Second Pattern]
-   [Same structure]
-   ## Communication Strengths
-   1. [Strength 1 with example]
-   2. [Strength 2 with example]
-   3. [Strength 3 with example]
-   ## Growth Opportunities
-   1. **[Area 1]**: [Specific, actionable advice]
-   2. **[Area 2]**: [Specific, actionable advice]
-   3. **[Area 3]**: [Specific, actionable advice]
-   ## Speaking Statistics
-   - Average speaking time: [X% of meeting]
-   - Questions asked: [X per meeting average]
-   - Filler words: [X per minute]
-   - Interruptions: [X given / Y received per meeting]
-   ## Next Steps
-   [3-5 concrete actions to improve communication]
-   ```
-6. **Offer Follow-Up Options**
-   - Track these same metrics in future meetings
-   - Deep dive into specific meetings or patterns
-   - Compare to industry benchmarks
-   - Create a personal communication development plan
-   - Generate a summary for performance reviews
-## Examples
-### Example 1: Conflict Avoidance Analysis (Inspired by Dan Shipper)
-**User**: "I download all of my meeting recordings and put them in a folder. Tell me all the times I've subtly avoided conflict."
-**Output**:
-```markdown
-# Conflict Avoidance Patterns
-Found 23 instances across 15 meetings where you used indirect
-communication or avoided addressing tensions directly.
-## Pattern: Hedging on Critical Feedback
-**Frequency**: 8 times across 7 meetings
-**Example 1: 1:1 with Sarah** - 00:14:32
-**What Happened**:
-> "So, I was thinking... maybe we could, like, potentially
-> consider looking at the timeline again? I mean, if you
-> think that makes sense. But whatever you think is best!"
-**Why This Matters**:
-You needed to address that Sarah's project was behind schedule,
-but the hedging language ("maybe", "potentially", "if you think")
-and the deflection at the end ("whatever you think") made it easy
-for her to miss the urgency.
-**Better Approach**:
-"Sarah, the project is two weeks behind schedule. We need to
-discuss what's blocking progress and create a new timeline
-today."
-[Additional examples...]
-## Recommendations
-1. **Name the issue directly** in the first sentence
-2. **Remove hedging words** like "maybe," "kind of," "sort of"
-3. **Ask specific questions** instead of hinting
-4. **Schedule difficult conversations** instead of raising them casually
-```
-### Example 2: Leadership Facilitation
-**User**: "Analyze my team meetings and tell me about my facilitation style."
-**Output**: Provides insights on:
-- How much you speak vs. team members (60% vs. 40%)
-- Whether you ask questions or make statements (3:1 ratio)
-- How you handle disagreements (tendency to resolve too quickly)
-- Who speaks least and whether you draw them in
-- Examples of good and missed facilitation moments
-### Example 3: Personal Development Tracking
-**User**: "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."
-**Output**: Creates a comparative analysis showing:
-- Decrease in interruptions (8 per meeting → 3 per meeting)
-- Increase in clarifying questions (2 → 7 per meeting)
-- Improvement in building on others' ideas
-- Specific examples showing the difference
-- Remaining areas for growth
-## Setup Tips
-### Getting Meeting Transcripts
-**From Granola** (free with Lenny's newsletter subscription):
-- Granola auto-transcribes your meetings
-- Export transcripts to a folder: [Instructions on how]
-- Point Claude Code to that folder
-**From Zoom**:
-- Enable cloud recording with transcription
-- Download VTT or SRT files after meetings
-- Store in a dedicated folder
-**From Google Meet**:
-- Use Google Docs auto-transcription
-- Save transcript docs to a folder
-- Download as .txt files or give Claude Code access
-**From Fireflies.ai, Otter.ai, etc.**:
-- Export transcripts in bulk
-- Store in a local folder
-- Run analysis on the folder
-### Best Practices
-1. **Consistent naming**: Use `YYYY-MM-DD - Meeting Name.txt` format
-2. **Regular analysis**: Review monthly or quarterly for trends
-3. **Specific queries**: Ask about one behavior at a time for depth
-4. **Privacy**: Keep sensitive meeting data local
-5. **Action-oriented**: Focus on one improvement area at a time
-## Common Analysis Requests
-- "When do I avoid difficult conversations?"
-- "How often do I interrupt others?"
-- "What's my speaking vs. listening ratio?"
-- "Do I ask good questions?"
-- "How do I handle disagreement?"
-- "Am I inclusive of all voices?"
-- "Do I use too many filler words?"
-- "How clear are my action items?"
-- "Do I stay on agenda or get sidetracked?"
-- "How has my communication changed over time?"
-## Related Use Cases
-- Creating a personal development plan from insights
-- Preparing performance review materials with examples
-- Coaching direct reports on their communication
-- Analyzing customer calls for sales or support patterns
-- Studying negotiation tactics and outcomes

package/bundles/antigravity-plugin-extras/skills/notebooklm/AUTHENTICATION.md DELETED Viewed

@@ -1,154 +0,0 @@
-# Authentication Architecture
-## Overview
-This skill uses a **hybrid authentication approach** that combines the best of both worlds:
-1. **Persistent Browser Profile** (`user_data_dir`) for consistent browser fingerprinting
-2. **Manual Cookie Injection** from `state.json` for reliable session cookie persistence
-## Why This Approach?
-### The Problem
-Playwright/Patchright has a known bug ([#36139](https://github.com/microsoft/playwright/issues/36139)) where **session cookies** (cookies without an `Expires` attribute) do not persist correctly when using `launch_persistent_context()` with `user_data_dir`.
-**What happens:**
-- ✅ Persistent cookies (with `Expires` date) → Saved correctly to browser profile
-- ❌ Session cookies (without `Expires`) → **Lost after browser restarts**
-**Impact:**
-- Some Google auth cookies are session cookies
-- Users experience random authentication failures
-- "Works on my machine" syndrome (depends on which cookies Google uses)
-### TypeScript vs Python
-The **MCP Server** (TypeScript) can work around this by passing `storage_state` as a parameter:
-```typescript
-// TypeScript - works!
-const context = await chromium.launchPersistentContext(userDataDir, {
-  storageState: "state.json",  // ← Loads cookies including session cookies
-  channel: "chrome"
-});
-```
-But **Python's Playwright API doesn't support this** ([#14949](https://github.com/microsoft/playwright/issues/14949)):
-```python
-# Python - NOT SUPPORTED!
-context = playwright.chromium.launch_persistent_context(
-    user_data_dir=profile_dir,
-    storage_state="state.json",  # ← Parameter not available in Python!
-    channel="chrome"
-)
-```
-## Our Solution: Hybrid Approach
-We use a **two-phase authentication system**:
-### Phase 1: Setup (`auth_manager.py setup`)
-1. Launch persistent context with `user_data_dir`
-2. User logs in manually
-3. **Save state to TWO places:**
-   - Browser profile directory (automatic, for fingerprint + persistent cookies)
-   - `state.json` file (explicit save, for session cookies)
-```python
-context = playwright.chromium.launch_persistent_context(
-    user_data_dir="browser_profile/",
-    channel="chrome"
-)
-# User logs in...
-context.storage_state(path="state.json")  # Save all cookies
-```
-### Phase 2: Runtime (`ask_question.py`)
-1. Launch persistent context with `user_data_dir` (loads fingerprint + persistent cookies)
-2. **Manually inject cookies** from `state.json` (adds session cookies)
-```python
-# Step 1: Launch with browser profile
-context = playwright.chromium.launch_persistent_context(
-    user_data_dir="browser_profile/",
-    channel="chrome"
-)
-# Step 2: Manually inject cookies from state.json
-with open("state.json", 'r') as f:
-    state = json.load(f)
-    context.add_cookies(state['cookies'])  # ← Workaround for session cookies!
-```
-## Benefits
-| Feature | Our Approach | Pure `user_data_dir` | Pure `storage_state` |
-|---------|--------------|----------------------|----------------------|
-| **Browser Fingerprint Consistency** | ✅ Same across restarts | ✅ Same | ❌ Changes each time |
-| **Session Cookie Persistence** | ✅ Manual injection | ❌ Lost (bug) | ✅ Native support |
-| **Persistent Cookie Persistence** | ✅ Automatic | ✅ Automatic | ✅ Native support |
-| **Google Trust** | ✅ High (same browser) | ✅ High | ❌ Low (new browser) |
-| **Cross-platform Reliability** | ✅ Chrome required | ⚠️ Chromium issues | ✅ Portable |
-| **Cache Performance** | ✅ Keeps cache | ✅ Keeps cache | ❌ No cache |
-## File Structure
-```
-~/.claude/skills/notebooklm/data/
-├── auth_info.json              # Metadata about authentication
-├── browser_state/
-│   ├── state.json             # Cookies + localStorage (for manual injection)
-│   └── browser_profile/       # Chrome user profile (for fingerprint + cache)
-│       ├── Default/
-│       │   ├── Cookies        # Persistent cookies only (session cookies missing!)
-│       │   ├── Local Storage/
-│       │   └── Cache/
-│       └── ...
-```
-## Why `state.json` is Critical
-Even though we use `user_data_dir`, we **still need `state.json`** because:
-1. **Session cookies** are not saved to the browser profile (Playwright bug)
-2. **Manual injection** is the only reliable way to load session cookies
-3. **Validation** - we can check if cookies are expired before launching
-## Code References
-**Setup:** `scripts/auth_manager.py:94-120`
-- Lines 100-113: Launch persistent context with `channel="chrome"`
-- Line 167: Save to `state.json` via `context.storage_state()`
-**Runtime:** `scripts/ask_question.py:77-118`
-- Lines 86-99: Launch persistent context
-- Lines 101-118: Manual cookie injection workaround
-**Validation:** `scripts/auth_manager.py:236-298`
-- Lines 262-275: Launch persistent context
-- Lines 277-287: Manual cookie injection for validation
-## Related Issues
-- [microsoft/playwright#36139](https://github.com/microsoft/playwright/issues/36139) - Session cookies not persisting
-- [microsoft/playwright#14949](https://github.com/microsoft/playwright/issues/14949) - Storage state with persistent context
-- [StackOverflow Question](https://stackoverflow.com/questions/79641481/) - Session cookie persistence issue
-## Future Improvements
-If Playwright adds support for `storage_state` parameter in Python's `launch_persistent_context()`, we can simplify to:
-```python
-# Future (when Python API supports it):
-context = playwright.chromium.launch_persistent_context(
-    user_data_dir="browser_profile/",
-    storage_state="state.json",  # ← Would handle everything automatically!
-    channel="chrome"
-)
-```
-Until then, our hybrid approach is the most reliable solution.