mirror of
https://github.com/ComposioHQ/awesome-claude-skills.git
synced 2026-08-28 05:27:39 +00:00
Merge branch 'master' into add-connect-skill
This commit is contained in:
Prathit
GitHub
commit
cb8d96a837
5 changed files with 999 additions and 7 deletions
|
|
@ -146,6 +146,12 @@
|
|||
"source": "./raffle-winner-picker",
|
||||
"category": "productivity-organization"
|
||||
},
|
||||
{
|
||||
"name": "tailored-resume-generator",
|
||||
"description": "Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances.",
|
||||
"source": "./tailored-resume-generator",
|
||||
"category": "productivity-organization"
|
||||
},
|
||||
{
|
||||
"name": "document-skills-docx",
|
||||
"description": "Skills for working with Microsoft Word documents including creation, editing, and formatting using DOCX format.",
|
||||
|
|
|
|||
14
README.md
14
README.md
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
<p align="center">
|
||||
<a href="https://platform.composio.dev/?utm_source=Github&utm_medium=Youtube&utm_campaign=2025-11&utm_content=AwesomeSkills">
|
||||
<img width="1280" height="640" alt="Composio banner" src="https://github.com/user-attachments/assets/adb3f57a-2706-4329-856f-059a32059d48">
|
||||
<img width="1280" height="640" alt="Composio banner" src="https://github.com/user-attachments/assets/e91255af-e4ba-4d71-b1a8-bd081e8a234a">
|
||||
</a>
|
||||
|
||||
|
||||
|
|
@ -62,10 +62,7 @@ exit
|
|||
claude
|
||||
```
|
||||
|
||||
Then ask:
|
||||
```
|
||||
Send me a test email at your@email.com
|
||||
```
|
||||
> **Want skills that do more than generate text?** Claude can send emails, create issues, post to Slack, and take actions across 1000+ apps. [See how →](./connect/)
|
||||
|
||||
If you receive the email, Claude is now connected to 500+ apps.
|
||||
|
||||
|
|
@ -108,7 +105,7 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
|
|||
|
||||
### Development & Code Tools
|
||||
|
||||
- [artifacts-builder](https://github.com/anthropics/skills/tree/main/web-artifacts-builder) - Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
|
||||
- [artifacts-builder](https://github.com/anthropics/skills/tree/main/skills/web-artifacts-builder) - Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
|
||||
- [aws-skills](https://github.com/zxkane/aws-skills) - AWS development with CDK best practices, cost optimization MCP servers, and serverless/event-driven architecture patterns.
|
||||
- [Changelog Generator](./changelog-generator/) - Automatically creates user-facing changelogs from git commits by analyzing history and transforming technical commits into customer-friendly release notes.
|
||||
- [Claude Code Terminal Title](https://github.com/bluzername/claude-code-terminal-title) - Gives each Claud-Code terminal window a dynamic title that describes the work being done so you don't lose track of what window is doing what.
|
||||
|
|
@ -116,18 +113,20 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
|
|||
- [FFUF Web Fuzzing](https://github.com/jthack/ffuf_claude_skill) - Integrates the ffuf web fuzzer so Claude can run fuzzing tasks and analyze results for vulnerabilities. *By [@jthack](https://github.com/jthack)*
|
||||
- [finishing-a-development-branch](https://github.com/obra/superpowers/tree/main/skills/finishing-a-development-branch) - Guides completion of development work by presenting clear options and handling chosen workflow.
|
||||
- [iOS Simulator](https://github.com/conorluddy/ios-simulator-skill) - Enables Claude to interact with iOS Simulator for testing and debugging iOS applications. *By [@conorluddy](https://github.com/conorluddy)*
|
||||
- [LangSmith Fetch](./langsmith-fetch/) - Debug LangChain and LangGraph agents by automatically fetching and analyzing execution traces from LangSmith Studio. First AI observability skill for Claude Code. *By [@OthmanAdi](https://github.com/OthmanAdi)*
|
||||
- [MCP Builder](./mcp-builder/) - Guides creation of high-quality MCP (Model Context Protocol) servers for integrating external APIs and services with LLMs using Python or TypeScript.
|
||||
- [move-code-quality-skill](https://github.com/1NickPappas/move-code-quality-skill) - Analyzes Move language packages against the official Move Book Code Quality Checklist for Move 2024 Edition compliance and best practices.
|
||||
- [Playwright Browser Automation](https://github.com/lackeyjb/playwright-skill) - Model-invoked Playwright automation for testing and validating web applications. *By [@lackeyjb](https://github.com/lackeyjb)*
|
||||
- [prompt-engineering](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/customaize-agent/skills/prompt-engineering) - Teaches well-known prompt engineering techniques and patterns, including Anthropic best practices and agent persuasion principles.
|
||||
- [pypict-claude-skill](https://github.com/omkamal/pypict-claude-skill) - Design comprehensive test cases using PICT (Pairwise Independent Combinatorial Testing) for requirements or code, generating optimized test suites with pairwise coverage.
|
||||
- [reddit-fetch](https://github.com/ykdojo/claude-code-tips/tree/main/skills/reddit-fetch) - Fetches Reddit content via Gemini CLI when WebFetch is blocked or returns 403 errors.
|
||||
- [Skill Creator](./skill-creator/) - Provides guidance for creating effective Claude Skills that extend capabilities with specialized knowledge, workflows, and tool integrations.
|
||||
- [Skill Seekers](https://github.com/yusufkaraaslan/Skill_Seekers) - Automatically converts any documentation website into a Claude AI skill in minutes. *By [@yusufkaraaslan](https://github.com/yusufkaraaslan)*
|
||||
- [software-architecture](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/ddd/skills/software-architecture) - Implements design patterns including Clean Architecture, SOLID principles, and comprehensive software design best practices.
|
||||
- [subagent-driven-development](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/sadd/skills/subagent-driven-development) - Dispatches independent subagents for individual tasks with code review checkpoints between iterations for rapid, controlled development.
|
||||
- [test-driven-development](https://github.com/obra/superpowers/tree/main/skills/test-driven-development) - Use when implementing any feature or bugfix, before writing implementation code.
|
||||
- [using-git-worktrees](https://github.com/obra/superpowers/blob/main/skills/using-git-worktrees/) - Creates isolated git worktrees with smart directory selection and safety verification.
|
||||
- [Connect Apps](./connect-apps/) - Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
|
||||
- [Connect](./connect/) - Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
|
||||
- [Webapp Testing](./webapp-testing/) - Tests local web applications using Playwright for verifying frontend functionality, debugging UI behavior, and capturing screenshots.
|
||||
|
||||
### Data & Analysis
|
||||
|
|
@ -170,6 +169,7 @@ Claude Skills are customizable workflows that teach Claude how to perform specif
|
|||
- [kaizen](https://github.com/NeoLabHQ/context-engineering-kit/tree/master/plugins/kaizen/skills/kaizen) - Applies continuous improvement methodology with multiple analytical approaches, based on Japanese Kaizen philosophy and Lean methodology.
|
||||
- [n8n-skills](https://github.com/haunchen/n8n-skills) - Enables AI assistants to directly understand and operate n8n workflows.
|
||||
- [Raffle Winner Picker](./raffle-winner-picker/) - Randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests with cryptographically secure randomness.
|
||||
- [Tailored Resume Generator](./tailored-resume-generator/) - Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances.
|
||||
- [ship-learn-next](https://github.com/michalparkola/tapestry-skills-for-claude-code/tree/main/ship-learn-next) - Skill to help iterate on what to build or learn next, based on feedback loops.
|
||||
- [tapestry](https://github.com/michalparkola/tapestry-skills-for-claude-code/tree/main/tapestry) - Interlink and summarize related documents into knowledge networks.
|
||||
|
||||
|
|
|
|||
156
connect/SKILL.md
Normal file
156
connect/SKILL.md
Normal file
|
|
@ -0,0 +1,156 @@
|
|||
---
|
||||
name: connect
|
||||
description: Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
|
||||
---
|
||||
|
||||
# Connect
|
||||
|
||||
Connect Claude to any app. Stop generating text about what you could do - actually do it.
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
Use this skill when you need Claude to:
|
||||
|
||||
- **Send that email** instead of drafting it
|
||||
- **Create that issue** instead of describing it
|
||||
- **Post that message** instead of suggesting it
|
||||
- **Update that database** instead of explaining how
|
||||
|
||||
## What Changes
|
||||
|
||||
| Without Connect | With Connect |
|
||||
|-----------------|--------------|
|
||||
| "Here's a draft email..." | Sends the email |
|
||||
| "You should create an issue..." | Creates the issue |
|
||||
| "Post this to Slack..." | Posts it |
|
||||
| "Add this to Notion..." | Adds it |
|
||||
|
||||
## Supported Apps
|
||||
|
||||
**1000+ integrations** including:
|
||||
|
||||
- **Email:** Gmail, Outlook, SendGrid
|
||||
- **Chat:** Slack, Discord, Teams, Telegram
|
||||
- **Dev:** GitHub, GitLab, Jira, Linear
|
||||
- **Docs:** Notion, Google Docs, Confluence
|
||||
- **Data:** Sheets, Airtable, PostgreSQL
|
||||
- **CRM:** HubSpot, Salesforce, Pipedrive
|
||||
- **Storage:** Drive, Dropbox, S3
|
||||
- **Social:** Twitter, LinkedIn, Reddit
|
||||
|
||||
## Setup
|
||||
|
||||
### 1. Get API Key
|
||||
|
||||
Get your free key at [platform.composio.dev](https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills)
|
||||
|
||||
### 2. Set Environment Variable
|
||||
|
||||
```bash
|
||||
export COMPOSIO_API_KEY="your-key"
|
||||
```
|
||||
|
||||
### 3. Install
|
||||
|
||||
```bash
|
||||
pip install composio # Python
|
||||
npm install @composio/core # TypeScript
|
||||
```
|
||||
|
||||
Done. Claude can now connect to any app.
|
||||
|
||||
## Examples
|
||||
|
||||
### Send Email
|
||||
```
|
||||
Email sarah@acme.com - Subject: "Shipped!" Body: "v2.0 is live, let me know if issues"
|
||||
```
|
||||
|
||||
### Create GitHub Issue
|
||||
```
|
||||
Create issue in my-org/repo: "Mobile timeout bug" with label:bug
|
||||
```
|
||||
|
||||
### Post to Slack
|
||||
```
|
||||
Post to #engineering: "Deploy complete - v2.4.0 live"
|
||||
```
|
||||
|
||||
### Chain Actions
|
||||
```
|
||||
Find GitHub issues labeled "bug" from this week, summarize, post to #bugs on Slack
|
||||
```
|
||||
|
||||
## How It Works
|
||||
|
||||
Uses Composio Tool Router:
|
||||
|
||||
1. **You ask** Claude to do something
|
||||
2. **Tool Router finds** the right tool (1000+ options)
|
||||
3. **OAuth handled** automatically
|
||||
4. **Action executes** and returns result
|
||||
|
||||
### Code
|
||||
|
||||
```python
|
||||
from composio import Composio
|
||||
from claude_agent_sdk.client import ClaudeSDKClient
|
||||
from claude_agent_sdk.types import ClaudeAgentOptions
|
||||
import os
|
||||
|
||||
composio = Composio(api_key=os.environ["COMPOSIO_API_KEY"])
|
||||
session = composio.create(user_id="user_123")
|
||||
|
||||
options = ClaudeAgentOptions(
|
||||
system_prompt="You can take actions in external apps.",
|
||||
mcp_servers={
|
||||
"composio": {
|
||||
"type": "http",
|
||||
"url": session.mcp.url,
|
||||
"headers": {"x-api-key": os.environ["COMPOSIO_API_KEY"]},
|
||||
}
|
||||
},
|
||||
)
|
||||
|
||||
async with ClaudeSDKClient(options) as client:
|
||||
await client.query("Send Slack message to #general: Hello!")
|
||||
```
|
||||
|
||||
## Auth Flow
|
||||
|
||||
First time using an app:
|
||||
```
|
||||
To send emails, I need Gmail access.
|
||||
Authorize here: https://...
|
||||
Say "connected" when done.
|
||||
```
|
||||
|
||||
Connection persists after that.
|
||||
|
||||
## Framework Support
|
||||
|
||||
| Framework | Install |
|
||||
|-----------|---------|
|
||||
| Claude Agent SDK | `pip install composio claude-agent-sdk` |
|
||||
| OpenAI Agents | `pip install composio openai-agents` |
|
||||
| Vercel AI | `npm install @composio/core @composio/vercel` |
|
||||
| LangChain | `pip install composio-langchain` |
|
||||
| Any MCP Client | Use `session.mcp.url` |
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
- **Auth required** → Click link, authorize, say "connected"
|
||||
- **Action failed** → Check permissions in target app
|
||||
- **Tool not found** → Be specific: "Slack #general" not "send message"
|
||||
|
||||
---
|
||||
|
||||
<p align="center">
|
||||
<b>Join 20,000+ developers building agents that ship</b>
|
||||
</p>
|
||||
|
||||
<p align="center">
|
||||
<a href="https://platform.composio.dev/?utm_source=Github&utm_content=AwesomeSkills">
|
||||
<img src="https://img.shields.io/badge/Get_Started_Free-4F46E5?style=for-the-badge" alt="Get Started"/>
|
||||
</a>
|
||||
</p>
|
||||
485
langsmith-fetch/SKILL.md
Normal file
485
langsmith-fetch/SKILL.md
Normal file
|
|
@ -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
|
||||
345
tailored-resume-generator/SKILL.md
Normal file
345
tailored-resume-generator/SKILL.md
Normal file
|
|
@ -0,0 +1,345 @@
|
|||
---
|
||||
name: tailored-resume-generator
|
||||
description: Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
|
||||
---
|
||||
|
||||
# Tailored Resume Generator
|
||||
|
||||
## When to Use This Skill
|
||||
|
||||
- Applying for a specific job position
|
||||
- Customizing your resume for different industries or roles
|
||||
- Highlighting relevant experience for career transitions
|
||||
- Optimizing your resume for ATS (Applicant Tracking Systems)
|
||||
- Creating multiple resume versions for different job applications
|
||||
- Emphasizing specific skills mentioned in job postings
|
||||
|
||||
## What This Skill Does
|
||||
|
||||
1. **Analyzes Job Descriptions**: Extracts key requirements, skills, qualifications, and keywords from job postings
|
||||
2. **Identifies Priorities**: Determines what employers value most based on the job description language and structure
|
||||
3. **Tailors Content**: Reorganizes and emphasizes relevant experience, skills, and achievements
|
||||
4. **Optimizes Keywords**: Incorporates ATS-friendly keywords naturally throughout the resume
|
||||
5. **Formats Professionally**: Creates clean, professional resume layouts suitable for various formats
|
||||
6. **Provides Recommendations**: Suggests improvements and highlights gaps to address
|
||||
|
||||
## How to Use
|
||||
|
||||
### Basic Usage
|
||||
Provide a job description and your background information:
|
||||
|
||||
```
|
||||
I'm applying for this job:
|
||||
|
||||
[paste job description]
|
||||
|
||||
Here's my background:
|
||||
- 5 years as software engineer at TechCorp
|
||||
- Led team of 3 developers on mobile app project
|
||||
- Expert in Python, JavaScript, React
|
||||
- Computer Science degree from State University
|
||||
```
|
||||
|
||||
### With Existing Resume
|
||||
Upload or paste your current resume along with the job description:
|
||||
|
||||
```
|
||||
Please tailor my resume for this position:
|
||||
|
||||
Job Description:
|
||||
[paste job description]
|
||||
|
||||
My Current Resume:
|
||||
[paste resume content]
|
||||
```
|
||||
|
||||
### Career Transition
|
||||
When changing industries or roles:
|
||||
|
||||
```
|
||||
I'm transitioning from marketing to product management.
|
||||
Here's the job I'm applying for:
|
||||
|
||||
[paste job description]
|
||||
|
||||
My transferable experience:
|
||||
- 7 years in digital marketing
|
||||
- Led cross-functional teams
|
||||
- Managed product launches
|
||||
- Data analysis and A/B testing
|
||||
```
|
||||
|
||||
## Example
|
||||
|
||||
**User Request:**
|
||||
```
|
||||
I need a tailored resume for this job:
|
||||
|
||||
Senior Data Analyst Position
|
||||
|
||||
Requirements:
|
||||
- 5+ years experience in data analysis
|
||||
- Expert in SQL, Python, and data visualization tools
|
||||
- Experience with A/B testing and statistical analysis
|
||||
- Strong communication skills to present findings
|
||||
- Healthcare industry experience preferred
|
||||
|
||||
My background:
|
||||
- Data Analyst at RetailCo (2019-2024)
|
||||
- Created dashboards using Tableau and Power BI
|
||||
- Built Python scripts for data automation
|
||||
- Worked with marketing team on campaign analysis
|
||||
- Business Analytics degree
|
||||
- Also did 1 year internship at HealthPlus clinic
|
||||
```
|
||||
|
||||
**Generated Output:**
|
||||
|
||||
```markdown
|
||||
# JOHN DOE
|
||||
Email: john.doe@email.com | Phone: (555) 123-4567 | LinkedIn: linkedin.com/in/johndoe
|
||||
|
||||
## PROFESSIONAL SUMMARY
|
||||
Results-driven Data Analyst with 5+ years of experience leveraging SQL, Python, and advanced
|
||||
visualization tools to deliver actionable insights. Proven track record in statistical analysis,
|
||||
A/B testing, and cross-functional collaboration. Healthcare industry experience with strong
|
||||
ability to communicate complex data findings to stakeholders.
|
||||
|
||||
## TECHNICAL SKILLS
|
||||
- **Data Analysis & Programming**: SQL, Python, Statistical Analysis, A/B Testing
|
||||
- **Visualization Tools**: Tableau, Power BI, Advanced Dashboard Development
|
||||
- **Data Management**: Data Automation, ETL Processes, Database Optimization
|
||||
- **Business Intelligence**: Campaign Analytics, Performance Metrics, KPI Tracking
|
||||
|
||||
## PROFESSIONAL EXPERIENCE
|
||||
|
||||
**Data Analyst** | RetailCo | 2019 - 2024
|
||||
- Designed and implemented 50+ SQL queries and Python automation scripts, reducing manual
|
||||
data processing time by 60%
|
||||
- Conducted rigorous A/B testing and statistical analysis for marketing campaigns,
|
||||
improving campaign ROI by 35%
|
||||
- Built interactive Tableau and Power BI dashboards for executive team, enabling
|
||||
data-driven decision making
|
||||
- Presented analytical findings to cross-functional stakeholders including marketing,
|
||||
operations, and executive leadership
|
||||
- Collaborated with marketing team to analyze customer behavior patterns and optimize
|
||||
targeting strategies
|
||||
|
||||
**Data Analysis Intern** | HealthPlus Clinic | 2018 - 2019
|
||||
- Supported healthcare analytics initiatives by analyzing patient data and operational metrics
|
||||
- Gained exposure to healthcare industry data management and HIPAA compliance requirements
|
||||
- Assisted in creating reports for clinical staff to improve patient care workflows
|
||||
|
||||
## EDUCATION
|
||||
|
||||
**Bachelor of Science in Business Analytics**
|
||||
State University | Graduated 2018
|
||||
|
||||
## KEY ACHIEVEMENTS
|
||||
- Reduced data processing time by 60% through Python automation
|
||||
- Improved marketing campaign ROI by 35% through A/B testing and optimization
|
||||
- Created data visualization system now used across entire organization
|
||||
```
|
||||
|
||||
**Additional Recommendations:**
|
||||
- Consider adding any specific healthcare projects or certifications
|
||||
- Quantify more achievements with metrics when possible
|
||||
- If you have experience with R or advanced statistical methods, add them
|
||||
- Consider mentioning any familiarity with healthcare regulations (HIPAA, etc.)
|
||||
|
||||
---
|
||||
|
||||
## Instructions
|
||||
|
||||
When a user requests resume tailoring:
|
||||
|
||||
### 1. Gather Information
|
||||
|
||||
**Job Description Analysis**:
|
||||
- Request the full job description if not provided
|
||||
- Ask for the company name and job title
|
||||
|
||||
**Candidate Background**:
|
||||
- If user provides existing resume, use it as the foundation
|
||||
- If not, request:
|
||||
- Work history (job titles, companies, dates, responsibilities)
|
||||
- Education background
|
||||
- Key skills and technical proficiencies
|
||||
- Notable achievements and metrics
|
||||
- Certifications or awards
|
||||
- Any other relevant information
|
||||
|
||||
### 2. Analyze Job Requirements
|
||||
|
||||
Extract and prioritize:
|
||||
- **Must-have qualifications**: Years of experience, required skills, education
|
||||
- **Key skills**: Technical tools, methodologies, competencies
|
||||
- **Soft skills**: Communication, leadership, teamwork
|
||||
- **Industry knowledge**: Domain-specific experience
|
||||
- **Keywords**: Repeated terms, phrases, and buzzwords for ATS optimization
|
||||
- **Company values**: Cultural fit indicators from job description
|
||||
|
||||
Create a mental map of:
|
||||
- Priority 1: Critical requirements (deal-breakers)
|
||||
- Priority 2: Important qualifications (strongly desired)
|
||||
- Priority 3: Nice-to-have skills (bonus points)
|
||||
|
||||
### 3. Map Candidate Experience to Requirements
|
||||
|
||||
For each job requirement:
|
||||
- Identify matching experience from candidate's background
|
||||
- Find transferable skills if no direct match
|
||||
- Note gaps that need to be addressed or de-emphasized
|
||||
- Identify unique strengths to highlight
|
||||
|
||||
### 4. Structure the Tailored Resume
|
||||
|
||||
**Professional Summary** (3-4 lines):
|
||||
- Lead with years of experience in the target role/field
|
||||
- Include top 3-4 required skills from job description
|
||||
- Mention industry experience if relevant
|
||||
- Highlight unique value proposition
|
||||
|
||||
**Technical/Core Skills Section**:
|
||||
- Group skills by category matching job requirements
|
||||
- List required tools and technologies first
|
||||
- Use exact terminology from job description
|
||||
- Only include skills you can substantiate with experience
|
||||
|
||||
**Professional Experience**:
|
||||
- For each role, emphasize responsibilities and achievements aligned with job requirements
|
||||
- Use action verbs: Led, Developed, Implemented, Optimized, Managed, Created, Analyzed
|
||||
- **Quantify achievements**: Include numbers, percentages, timeframes, scale
|
||||
- Reorder bullet points to prioritize most relevant experience
|
||||
- Use keywords naturally from job description
|
||||
- Format: **[Action Verb] + [What] + [How/Why] + [Result/Impact]**
|
||||
|
||||
**Education**:
|
||||
- List degrees, certifications relevant to position
|
||||
- Include relevant coursework if early career
|
||||
- Add certifications that match job requirements
|
||||
|
||||
**Optional Sections** (if applicable):
|
||||
- Certifications & Licenses
|
||||
- Publications or Speaking Engagements
|
||||
- Awards & Recognition
|
||||
- Volunteer Work (if relevant to role)
|
||||
- Projects (especially for technical roles)
|
||||
|
||||
### 5. Optimize for ATS (Applicant Tracking Systems)
|
||||
|
||||
- Use standard section headings (Professional Experience, Education, Skills)
|
||||
- Incorporate exact keywords from job description naturally
|
||||
- Avoid tables, graphics, headers/footers, or complex formatting
|
||||
- Use standard fonts and bullet points
|
||||
- Include both acronyms and full terms (e.g., "SQL (Structured Query Language)")
|
||||
- Match job title terminology where truthful
|
||||
|
||||
### 6. Format and Present
|
||||
|
||||
**Format Options**:
|
||||
- **Markdown**: Clean, readable, easy to copy
|
||||
- **Plain Text**: ATS-optimized, safe for all systems
|
||||
- **Tips for Word/PDF**: Provide formatting guidance
|
||||
|
||||
**Resume Structure Guidelines**:
|
||||
- Keep to 1 page for <10 years experience, 2 pages for 10+ years
|
||||
- Use consistent formatting and spacing
|
||||
- Ensure contact information is prominent
|
||||
- Use reverse chronological order (most recent first)
|
||||
- Maintain clean, scannable layout with white space
|
||||
|
||||
### 7. Provide Strategic Recommendations
|
||||
|
||||
After presenting the tailored resume, offer:
|
||||
|
||||
**Strengths Analysis**:
|
||||
- What makes this candidate competitive
|
||||
- Unique qualifications to emphasize in cover letter or interview
|
||||
|
||||
**Gap Analysis**:
|
||||
- Requirements not fully met
|
||||
- Suggestions for addressing gaps (courses, projects, reframing experience)
|
||||
|
||||
**Interview Preparation Tips**:
|
||||
- Key talking points aligned with resume
|
||||
- Stories to prepare based on job requirements
|
||||
- Questions to ask that demonstrate fit
|
||||
|
||||
**Cover Letter Hooks**:
|
||||
- Suggest 2-3 opening lines for cover letter
|
||||
- Key achievements to expand upon
|
||||
|
||||
### 8. Iterate and Refine
|
||||
|
||||
Ask if user wants to:
|
||||
- Adjust emphasis or tone
|
||||
- Add or remove sections
|
||||
- Generate alternative versions for different roles
|
||||
- Create format variations (traditional vs. modern)
|
||||
- Develop role-specific versions (if applying to multiple similar positions)
|
||||
|
||||
### 9. Best Practices to Follow
|
||||
|
||||
**Do**:
|
||||
- Be truthful and accurate - never fabricate experience
|
||||
- Use industry-standard terminology
|
||||
- Quantify achievements with specific metrics
|
||||
- Tailor each resume to specific job
|
||||
- Proofread for grammar and consistency
|
||||
- Keep language concise and impactful
|
||||
|
||||
**Don't**:
|
||||
- Include personal information (age, marital status, photo unless requested)
|
||||
- Use first-person pronouns (I, me, my)
|
||||
- Include references ("available upon request" is outdated)
|
||||
- List every job if career is 20+ years (focus on relevant, recent experience)
|
||||
- Use generic templates without customization
|
||||
- Exceed 2 pages unless very senior role
|
||||
|
||||
### 10. Special Considerations
|
||||
|
||||
**Career Changers**:
|
||||
- Use functional or hybrid resume format
|
||||
- Emphasize transferable skills
|
||||
- Create compelling narrative in summary
|
||||
- Focus on relevant projects and coursework
|
||||
|
||||
**Recent Graduates**:
|
||||
- Lead with education
|
||||
- Include relevant coursework, projects, internships
|
||||
- Emphasize leadership in student organizations
|
||||
- Include GPA if 3.5+
|
||||
|
||||
**Senior Executives**:
|
||||
- Lead with executive summary
|
||||
- Focus on leadership and strategic impact
|
||||
- Include board memberships, speaking engagements
|
||||
- Emphasize revenue growth, team building, vision
|
||||
|
||||
**Technical Roles**:
|
||||
- Include technical skills section prominently
|
||||
- List programming languages, frameworks, tools
|
||||
- Include GitHub, portfolio, or project links
|
||||
- Mention methodologies (Agile, Scrum, etc.)
|
||||
|
||||
**Creative Roles**:
|
||||
- Include link to portfolio
|
||||
- Highlight creative achievements and campaigns
|
||||
- Mention tools and software proficiencies
|
||||
- Consider more creative formatting (while maintaining ATS compatibility)
|
||||
|
||||
---
|
||||
|
||||
## Tips for Best Results
|
||||
|
||||
- **Be specific**: Provide complete job descriptions and detailed background information
|
||||
- **Share metrics**: Include numbers, percentages, and quantifiable achievements when describing your experience
|
||||
- **Indicate format preference**: Let the skill know if you need ATS-optimized, creative, or traditional format
|
||||
- **Mention constraints**: Share any specific requirements (page limits, sections to include/exclude)
|
||||
- **Iterate**: Don't hesitate to ask for revisions or alternative approaches
|
||||
- **Multiple applications**: Generate separate tailored versions for different roles
|
||||
|
||||
## Privacy Note
|
||||
|
||||
This skill processes your personal and professional information to generate tailored resumes. Always review the output before submitting to ensure accuracy and appropriateness. Remove or modify any information you prefer not to share with potential employers.
|
||||
Loading…
Add table
Reference in a new issue