sourcebot
Search external libraries and frameworks using Sourcebot MCP. Use when researching external code patterns, library APIs, framework examples, or documentation from repositories like Effect-TS/effect, vercel/ai, tanstack/query. NEVER use for local project code.
What this skill does
# Sourcebot Guide
Expert guidance for using Sourcebot MCP to search external libraries, frameworks, and code patterns.
## When to Use
- **External library research:** Finding code patterns in Effect-TS, TanStack, Vercel AI SDK, etc.
- **API discovery:** Understanding how external libraries implement specific features
- **Documentation examples:** Finding real-world usage examples from official repositories
- **Framework patterns:** Learning best practices from external framework codebases
- **Migration guidance:** Finding upgrade patterns and breaking changes in external libraries
## When NOT to Use
- **Local project code:** Use `codebase_search` or `osgrep search` instead
- **Local components:** Use local search tools for project files
- **Local utilities:** Never use Sourcebot for your own codebase
## Required Workflow
1. **First, call `list_repos`** to get available repository IDs
2. **Identify relevant repository ID(s)** for your search (e.g., "Effect-TS/effect" for EffectTS)
3. **Always include `filterByRepoIds`** when calling `search_code`
4. **Use `get_file_source`** to fetch specific file contents when needed
## Repository ID Format
- **CRITICAL**: Repository IDs must be in format `"owner/repo"` (e.g., `"Effect-TS/effect"`, `"vercel/ai"`)
- **DO NOT** include the `github.com/` prefix
- The `list_repos` tool returns IDs like `"github.com/owner/repo"` - strip the prefix when using in `filterByRepoIds`
## Usage Examples
### Searching EffectTS patterns
```json
{
"query": "Effect.gen yield",
"filterByRepoIds": ["Effect-TS/effect"],
"includeCodeSnippets": true
}
```
### Searching AI SDK
```json
{
"query": "streamText tool calling",
"filterByRepoIds": ["vercel/ai"],
"includeCodeSnippets": true
}
```
### Searching multiple repos
```json
{
"query": "error handling patterns",
"filterByRepoIds": ["Effect-TS/effect", "vercel/ai"],
"includeCodeSnippets": true
}
```
## Best Practices
- Use descriptive queries (not just keywords, but full descriptions)
- Always specify `filterByRepoIds` to scope searches
- Set `includeCodeSnippets: true` when you need actual code examples
- Use `get_file_source` after finding relevant files to see full context
## Tool Hierarchy for Code Search
1. **Sourcebot** - For EXTERNAL libraries and frameworks only
2. **`codebase_search`** (if available) - For local project code
3. **`osgrep search`** - For local code when codebase_search unavailable
4. **`grep`/`find`** - Last resort for exact string matching
## Critical Requirements
- **MANDATORY**: Use Sourcebot MCP 5-7 times when researching external libraries
- **CRITICAL**: NEVER use Sourcebot to search local project code
- **CRITICAL**: Always use `filterByRepoIds` on EVERY `search_code` call
- **TASK INVALIDATION**: Task will be invalidated if you don't use Sourcebot 5-7 times when dealing with external libraries
- **AFTER SOURCEBOT**: Also use Perplexity and Context7 for updated information on external libraries
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.