@stephen-lord/docs 1.0.0

package/dist/awesome-claude-skills/langsmith-fetch/SKILL.md

@@ -0,0 +1,485 @@
+---
+name: langsmith-fetch
+description: Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
+---
+
+# LangSmith Fetch - Agent Debugging Skill
+
+Debug LangChain and LangGraph agents by fetching execution traces directly from LangSmith Studio in your terminal.
+
+## When to Use This Skill
+
+Automatically activate when user mentions:
+- 🐛 "Debug my agent" or "What went wrong?"
+- 🔍 "Show me recent traces" or "What happened?"
+- ❌ "Check for errors" or "Why did it fail?"
+- 💾 "Analyze memory operations" or "Check LTM"
+- 📊 "Review agent performance" or "Check token usage"
+- 🔧 "What tools were called?" or "Show execution flow"
+
+## Prerequisites
+
+### 1. Install langsmith-fetch
+```bash
+pip install langsmith-fetch
+```
+
+### 2. Set Environment Variables
+```bash
+export LANGSMITH_API_KEY="your_langsmith_api_key"
+export LANGSMITH_PROJECT="your_project_name"
+```
+
+**Verify setup:**
+```bash
+echo $LANGSMITH_API_KEY
+echo $LANGSMITH_PROJECT
+```
+
+## Core Workflows
+
+### Workflow 1: Quick Debug Recent Activity
+
+**When user asks:** "What just happened?" or "Debug my agent"
+
+**Execute:**
+```bash
+langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty
+```
+
+**Analyze and report:**
+1. ✅ Number of traces found
+2. ⚠️ Any errors or failures
+3. 🛠️ Tools that were called
+4. ⏱️ Execution times
+5. 💰 Token usage
+
+**Example response format:**
+```
+Found 3 traces in the last 5 minutes:
+
+Trace 1: ✅ Success
+- Agent: memento
+- Tools: recall_memories, create_entities
+- Duration: 2.3s
+- Tokens: 1,245
+
+Trace 2: ❌ Error
+- Agent: cypher
+- Error: "Neo4j connection timeout"
+- Duration: 15.1s
+- Failed at: search_nodes tool
+
+Trace 3: ✅ Success
+- Agent: memento
+- Tools: store_memory
+- Duration: 1.8s
+- Tokens: 892
+
+💡 Issue found: Trace 2 failed due to Neo4j timeout. Recommend checking database connection.
+```
+
+---
+
+### Workflow 2: Deep Dive Specific Trace
+
+**When user provides:** Trace ID or says "investigate that error"
+
+**Execute:**
+```bash
+langsmith-fetch trace <trace-id> --format json
+```
+
+**Analyze JSON and report:**
+1. 🎯 What the agent was trying to do
+2. 🛠️ Which tools were called (in order)
+3. ✅ Tool results (success/failure)
+4. ❌ Error messages (if any)
+5. 💡 Root cause analysis
+6. 🔧 Suggested fix
+
+**Example response format:**
+```
+Deep Dive Analysis - Trace abc123
+
+Goal: User asked "Find all projects in Neo4j"
+
+Execution Flow:
+1. ✅ search_nodes(query: "projects")
+   → Found 24 nodes
+
+2. ❌ get_node_details(node_id: "proj_123")
+   → Error: "Node not found"
+   → This is the failure point
+
+3. ⏹️ Execution stopped
+
+Root Cause:
+The search_nodes tool returned node IDs that no longer exist in the database,
+possibly due to recent deletions.
+
+Suggested Fix:
+1. Add error handling in get_node_details tool
+2. Filter deleted nodes in search results
+3. Update cache invalidation strategy
+
+Token Usage: 1,842 tokens ($0.0276)
+Execution Time: 8.7 seconds
+```
+
+---
+
+### Workflow 3: Export Debug Session
+
+**When user says:** "Save this session" or "Export traces"
+
+**Execute:**
+```bash
+# Create session folder with timestamp
+SESSION_DIR="langsmith-debug/session-$(date +%Y%m%d-%H%M%S)"
+mkdir -p "$SESSION_DIR"
+
+# Export traces
+langsmith-fetch traces "$SESSION_DIR/traces" --last-n-minutes 30 --limit 50 --include-metadata
+
+# Export threads (conversations)
+langsmith-fetch threads "$SESSION_DIR/threads" --limit 20
+```
+
+**Report:**
+```
+✅ Session exported successfully!
+
+Location: langsmith-debug/session-20251224-143022/
+- Traces: 42 files
+- Threads: 8 files
+
+You can now:
+1. Review individual trace files
+2. Share folder with team
+3. Analyze with external tools
+4. Archive for future reference
+
+Session size: 2.3 MB
+```
+
+---
+
+### Workflow 4: Error Detection
+
+**When user asks:** "Show me errors" or "What's failing?"
+
+**Execute:**
+```bash
+# Fetch recent traces
+langsmith-fetch traces --last-n-minutes 30 --limit 50 --format json > recent-traces.json
+
+# Search for errors
+grep -i "error\|failed\|exception" recent-traces.json
+```
+
+**Analyze and report:**
+1. 📊 Total errors found
+2. ❌ Error types and frequency
+3. 🕐 When errors occurred
+4. 🎯 Which agents/tools failed
+5. 💡 Common patterns
+
+**Example response format:**
+```
+Error Analysis - Last 30 Minutes
+
+Total Traces: 50
+Failed Traces: 7 (14% failure rate)
+
+Error Breakdown:
+1. Neo4j Connection Timeout (4 occurrences)
+   - Agent: cypher
+   - Tool: search_nodes
+   - First occurred: 14:32
+   - Last occurred: 14:45
+   - Pattern: Happens during peak load
+
+2. Memory Store Failed (2 occurrences)
+   - Agent: memento
+   - Tool: store_memory
+   - Error: "Pinecone rate limit exceeded"
+   - Occurred: 14:38, 14:41
+
+3. Tool Not Found (1 occurrence)
+   - Agent: sqlcrm
+   - Attempted tool: "export_report" (doesn't exist)
+   - Occurred: 14:35
+
+💡 Recommendations:
+1. Add retry logic for Neo4j timeouts
+2. Implement rate limiting for Pinecone
+3. Fix sqlcrm tool configuration
+```
+
+---
+
+## Common Use Cases
+
+### Use Case 1: "Agent Not Responding"
+
+**User says:** "My agent isn't doing anything"
+
+**Steps:**
+1. Check if traces exist:
+   ```bash
+   langsmith-fetch traces --last-n-minutes 5 --limit 5
+   ```
+
+2. **If NO traces found:**
+   - Tracing might be disabled
+   - Check: `LANGCHAIN_TRACING_V2=true` in environment
+   - Check: `LANGCHAIN_API_KEY` is set
+   - Verify agent actually ran
+
+3. **If traces found:**
+   - Review for errors
+   - Check execution time (hanging?)
+   - Verify tool calls completed
+
+---
+
+### Use Case 2: "Wrong Tool Called"
+
+**User says:** "Why did it use the wrong tool?"
+
+**Steps:**
+1. Get the specific trace
+2. Review available tools at execution time
+3. Check agent's reasoning for tool selection
+4. Examine tool descriptions/instructions
+5. Suggest prompt or tool config improvements
+
+---
+
+### Use Case 3: "Memory Not Working"
+
+**User says:** "Agent doesn't remember things"
+
+**Steps:**
+1. Search for memory operations:
+   ```bash
+   langsmith-fetch traces --last-n-minutes 10 --limit 20 --format raw | grep -i "memory\|recall\|store"
+   ```
+
+2. Check:
+   - Were memory tools called?
+   - Did recall return results?
+   - Were memories actually stored?
+   - Are retrieved memories being used?
+
+---
+
+### Use Case 4: "Performance Issues"
+
+**User says:** "Agent is too slow"
+
+**Steps:**
+1. Export with metadata:
+   ```bash
+   langsmith-fetch traces ./perf-analysis --last-n-minutes 30 --limit 50 --include-metadata
+   ```
+
+2. Analyze:
+   - Execution time per trace
+   - Tool call latencies
+   - Token usage (context size)
+   - Number of iterations
+   - Slowest operations
+
+3. Identify bottlenecks and suggest optimizations
+
+---
+
+## Output Format Guide
+
+### Pretty Format (Default)
+```bash
+langsmith-fetch traces --limit 5 --format pretty
+```
+**Use for:** Quick visual inspection, showing to users
+
+### JSON Format
+```bash
+langsmith-fetch traces --limit 5 --format json
+```
+**Use for:** Detailed analysis, syntax-highlighted review
+
+### Raw Format
+```bash
+langsmith-fetch traces --limit 5 --format raw
+```
+**Use for:** Piping to other commands, automation
+
+---
+
+## Advanced Features
+
+### Time-Based Filtering
+```bash
+# After specific timestamp
+langsmith-fetch traces --after "2025-12-24T13:00:00Z" --limit 20
+
+# Last N minutes (most common)
+langsmith-fetch traces --last-n-minutes 60 --limit 100
+```
+
+### Include Metadata
+```bash
+# Get extra context
+langsmith-fetch traces --limit 10 --include-metadata
+
+# Metadata includes: agent type, model, tags, environment
+```
+
+### Concurrent Fetching (Faster)
+```bash
+# Speed up large exports
+langsmith-fetch traces ./output --limit 100 --concurrent 10
+```
+
+---
+
+## Troubleshooting
+
+### "No traces found matching criteria"
+
+**Possible causes:**
+1. No agent activity in the timeframe
+2. Tracing is disabled
+3. Wrong project name
+4. API key issues
+
+**Solutions:**
+```bash
+# 1. Try longer timeframe
+langsmith-fetch traces --last-n-minutes 1440 --limit 50
+
+# 2. Check environment
+echo $LANGSMITH_API_KEY
+echo $LANGSMITH_PROJECT
+
+# 3. Try fetching threads instead
+langsmith-fetch threads --limit 10
+
+# 4. Verify tracing is enabled in your code
+# Check for: LANGCHAIN_TRACING_V2=true
+```
+
+### "Project not found"
+
+**Solution:**
+```bash
+# View current config
+langsmith-fetch config show
+
+# Set correct project
+export LANGSMITH_PROJECT="correct-project-name"
+
+# Or configure permanently
+langsmith-fetch config set project "your-project-name"
+```
+
+### Environment variables not persisting
+
+**Solution:**
+```bash
+# Add to shell config file (~/.bashrc or ~/.zshrc)
+echo 'export LANGSMITH_API_KEY="your_key"' >> ~/.bashrc
+echo 'export LANGSMITH_PROJECT="your_project"' >> ~/.bashrc
+
+# Reload shell config
+source ~/.bashrc
+```
+
+---
+
+## Best Practices
+
+### 1. Regular Health Checks
+```bash
+# Quick check after making changes
+langsmith-fetch traces --last-n-minutes 5 --limit 5
+```
+
+### 2. Organized Storage
+```
+langsmith-debug/
+├── sessions/
+│   ├── 2025-12-24/
+│   └── 2025-12-25/
+├── error-cases/
+└── performance-tests/
+```
+
+### 3. Document Findings
+When you find bugs:
+1. Export the problematic trace
+2. Save to `error-cases/` folder
+3. Note what went wrong in a README
+4. Share trace ID with team
+
+### 4. Integration with Development
+```bash
+# Before committing code
+langsmith-fetch traces --last-n-minutes 10 --limit 5
+
+# If errors found
+langsmith-fetch trace <error-id> --format json > pre-commit-error.json
+```
+
+---
+
+## Quick Reference
+
+```bash
+# Most common commands
+
+# Quick debug
+langsmith-fetch traces --last-n-minutes 5 --limit 5 --format pretty
+
+# Specific trace
+langsmith-fetch trace <trace-id> --format pretty
+
+# Export session
+langsmith-fetch traces ./debug-session --last-n-minutes 30 --limit 50
+
+# Find errors
+langsmith-fetch traces --last-n-minutes 30 --limit 50 --format raw | grep -i error
+
+# With metadata
+langsmith-fetch traces --limit 10 --include-metadata
+```
+
+---
+
+## Resources
+
+- **LangSmith Fetch CLI:** https://github.com/langchain-ai/langsmith-fetch
+- **LangSmith Studio:** https://smith.langchain.com/
+- **LangChain Docs:** https://docs.langchain.com/
+- **This Skill Repo:** https://github.com/OthmanAdi/langsmith-fetch-skill
+
+---
+
+## Notes for Claude
+
+- Always check if `langsmith-fetch` is installed before running commands
+- Verify environment variables are set
+- Use `--format pretty` for human-readable output
+- Use `--format json` when you need to parse and analyze data
+- When exporting sessions, create organized folder structures
+- Always provide clear analysis and actionable insights
+- If commands fail, help troubleshoot configuration issues
+
+---
+
+**Version:** 0.1.0
+**Author:** Ahmad Othman Ammar Adi
+**License:** MIT
+**Repository:** https://github.com/OthmanAdi/langsmith-fetch-skill

package/dist/awesome-claude-skills/lead-research-assistant/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: lead-research-assistant
+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