So, its very strange because it created in .cursor\skills.
Besides that cursor is loading agents from .claude\agents instead of .cursor\agents (idk if they load from both folders but I only have the .claude\agents created)
create a sub agent to search documentation in the internt or dicussion in forums to help us implemnt a new integration or solve any problem
-–
name: search-docs-forums
description: Search online documentation, forums, and community discussions to help implement integrations, solve technical problems, and find best practices. Use when implementing new libraries, troubleshooting errors, researching APIs, or when the user mentions needing external documentation, forum help, or community discussions.
-–
# Search Documentation and Forums
This skill helps you search for up-to-date documentation, forum discussions, and community knowledge to implement integrations and solve technical problems.
## When to Use This Skill
Use this skill when:
- Implementing a new library or integration
- Encountering errors or bugs that need investigation
- Researching API usage or best practices
- Looking for implementation examples
- Troubleshooting configuration issues
- Finding community solutions to specific problems
## Search Strategy
### 1. Identify the Search Need
Determine what type of information is needed:
- **Official documentation**: API references, getting started guides, configuration
- **Implementation examples**: Real-world usage, code samples
- **Troubleshooting**: Error messages, known issues, workarounds
- **Best practices**: Community recommendations, patterns, anti-patterns
### 2. Construct Effective Search Queries
**For Official Documentation:**
```
“{library name} documentation {specific feature} 2026”
“{library name} official API reference {method/class}”
“{library name} installation guide {platform}”
```
**For Implementation Examples:**
```
“{library name} example {use case} GitHub”
“how to {specific task} with {library name}”
“{library name} integration with {other technology}”
```
**For Troubleshooting:**
```
“{exact error message}” {library name}
“{library name} {issue description} Stack Overflow”
“{library name} {issue} GitHub issues”
```
**For Best Practices:**
```
“{library name} best practices 2026”
“{library name} recommended patterns”
“{library name} vs {alternative} comparison”
```
### 3. Search Multiple Sources
Prioritize sources in this order:
1. **Official Documentation**
-
Official websites and docs
-
GitHub repositories (README, docs folder)
-
Official blogs and announcements
2. **Community Forums**
-
Stack Overflow
-
Reddit (r/programming, language-specific subreddits)
-
GitHub Issues and Discussions
-
Discord/Slack communities
3. **Technical Blogs**
### 4. Execute Comprehensive Search
For comprehensive searches, perform multiple searches with different angles:
1. **Primary search**: Official documentation
2. **Implementation search**: Code examples and tutorials
3. **Problem search**: Known issues and solutions
4. **Community search**: Discussions and recommendations
**Example Workflow:**
```
Problem: “Need to integrate Stripe payment with Express.js”
Search 1: “Stripe Express.js integration documentation 2026”
Search 2: “Stripe payment example Express.js GitHub”
Search 3: “Stripe webhook handling Express.js best practices”
Search 4: “Stripe Express.js common issues Stack Overflow”
```
## Output Format
Present findings in this structure:
### Summary
Brief overview of what was found (2-3 sentences)
### Official Documentation
- **[Source Name](URL)**: Key information found
- **[Source Name](URL)**: Key information found
### Implementation Examples
- **[Source Name](URL)**: Description and relevance
- **[Source Name](URL)**: Description and relevance
### Community Discussions
- **[Source Name](URL)**: Problem discussed and solutions suggested
- **[Source Name](URL)**: Problem discussed and solutions suggested
### Key Findings
1. **Main point**: Explanation with source reference
2. **Main point**: Explanation with source reference
3. **Main point**: Explanation with source reference
### Recommended Approach
Based on the research, provide a recommended implementation approach or solution with reasoning.
### Additional Resources
- Links to related documentation
- Useful GitHub repositories
- Community resources
## Search Quality Guidelines
### 
Do
- Include the year (2026) to get recent documentation
- Search for exact error messages in quotes
- Check multiple sources before concluding
- Verify information is up-to-date
- Look for official sources first
- Cross-reference solutions from multiple discussions
- Check GitHub issues for known problems
- Look for recently updated documentation
### 
Avoid
- Relying on a single source
- Using outdated documentation (check dates)
- Assuming first result is correct
- Ignoring version compatibility
- Skipping official documentation
- Using information without verifying currency
## Special Cases
### New Library/Integration
1. Search official documentation first
2. Find quickstart/getting started guides
3. Look for official examples in GitHub repo
4. Search for integration tutorials (recent)
5. Check for common pitfalls in forums
### Error Troubleshooting
1. Search exact error message in quotes
2. Include library name and version if known
3. Check GitHub issues (open and closed)
4. Look for Stack Overflow solutions
5. Search for release notes and changelogs
### API Usage
1. Find official API documentation
2. Search for code examples
3. Look for TypeScript definitions (if applicable)
4. Check for SDK documentation
5. Search for common patterns
### Configuration Issues
1. Search official configuration guides
2. Look for example configuration files in repos
3. Check GitHub issues for config problems
4. Search for migration guides (if upgrading)
5. Look for environment-specific guides
## Evaluation Criteria
After gathering information, evaluate:
1. **Reliability**: Is the source authoritative?
2. **Recency**: Is the information current (2025-2026)?
3. **Relevance**: Does it address the specific problem?
4. **Completeness**: Are there multiple confirming sources?
5. **Actionability**: Can this be implemented immediately?
## Quick Reference
### Common Search Patterns
| Need | Search Pattern |
| --------------- | --------------------------------------- |
| Getting started | `{library} getting started guide 2026` |
| API reference | `{library} API documentation {feature}` |
| Integration | `{library} integrate with {technology}` |
| Error fix | `“{exact error}” {library}` |
| Examples | `{library} example {use case} GitHub` |
| Best practices | `{library} best practices 2026` |
| Comparison | `{library} vs {alternative} 2026` |
| Migration | `migrate to {library} from {old tech}` |
### Useful Search Terms
- Add “official” for official documentation
- Add “GitHub” for code examples
- Add “Stack Overflow” for Q&A
- Add “tutorial” for step-by-step guides
- Add “2026” or “2025” for recent content
- Add language name for language-specific results
- Add framework name for framework-specific results
## Notes
- Always use the WebSearch tool for current information
- Documentation changes frequently - verify dates
- Community solutions may be more practical than official docs
- GitHub Issues often contain real-world solutions
- Multiple sources increase confidence in the solution
- Official docs may lag behind community knowledge for new features