unblocked-skills

Direct URL content resolution via context_get_urls. Use this to fetch full content from one or more URLs the agent already has in hand — PRs, issues, docs, Slack messages, or arbitrary web pages that were surfaced by a prior search or provided by the user. TRIGGER when: you already have concrete URLs from a previous context_research / context_search_* result and want the full body, not just the title and URL; the user pasted one or more links and wants them summarized or analyzed; you need to resolve a Jira/Linear/PR/Slack link directly. DO NOT TRIGGER when: you need to search for content (use context_research or the context_search_* family); the URL is local (localhost, file://, private network) — those aren't reachable.

Structured, filtered issue retrieval via context_query_issues. Use this instead of context_search_issues when you need a precise filtered list — scoped by project and/or person — rather than semantic relevance matching. TRIGGER when: the user asks "what bugs are open in PROJECT", "what issues is Alice working on", "list in-progress tickets for the payments team", "issues I filed last month"; you need a definitive list rather than a ranked set of relevant items; you already know the project key or person's name and want to enumerate issues under that filter. DO NOT TRIGGER when: the question is conceptual ("is there an issue about X") or you don't have a project/person anchor — use context-search-issues for semantic matching instead.

Structured, filtered PR retrieval via context_query_prs. Use this instead of context_search_prs when you need a precise filtered list — scoped by project/repo and/or person — rather than semantic relevance matching. TRIGGER when: the user asks "what PRs did Alice open last week", "list merged PRs in payments-service this month", "PRs I'm waiting on review for", "what did the team ship yesterday"; you need a definitive list rather than a ranked set; you already know the repo name or person and want to enumerate PRs under that filter. DO NOT TRIGGER when: the question is conceptual ("why was this introduced", "what PR added feature X") — use context-search-prs for semantic matching instead.

Unified context retrieval via context_research. Searches PRs, docs, messaging platforms, issue trackers, and code history to surface WHY code works the way it does, what was tried before, and what constraints apply. TRIGGER when: you need decision history, prior art, or conventions before modifying code; planning, scoping, or researching a topic; investigating a bug or incident; you need filtered lookups across issues, messages, or PRs (e.g., "open bugs in PROJECT", "what did X work on last week"); Grep/Glob/Read failed to find the referenced code — this skill searches across repos and systems beyond the current workspace. DO NOT TRIGGER when: you only need current implementation (not history or reasoning) — use Grep/Glob/Read directly.

Code-only search across the current repo and connected repos via context_search_code. Use this instead of context_research when you want code results without Slack, Jira, or doc noise mixed in. TRIGGER when: Grep/Glob/Read can't find a referenced class, function, or module (it may live in another connected repo); you need semantic code search rather than a literal pattern match; you want to find how something is implemented or used across repos; the user asks to "find", "locate", or "search for" code. DO NOT TRIGGER when: local Grep/Glob/Read can find what you need; you also need PR history, team decisions, Slack context, or issue tracker data — use context_research instead.