find-in-circleback
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword,…
Answer "what's breaking" questions from Sentry — find the right org and project, search issues and errors with the vocabulary Sentry uses, and report what is actually firing rather than the first hit. Use when the user asks what errors are happening, whether something is stable,
Claude Code
$ npx -y skills add paradevai/paradev --skill find-in-sentry --agent claude-code
Codex
$ npx skills add paradevai/paradev --skill find-in-sentry -a codex -y
Cursor
$ npx skills add paradevai/paradev --skill find-in-sentry -a cursor -y
Gemini CLI
$ npx skills add paradevai/paradev --skill find-in-sentry -a gemini-cli -y
GitHub Copilot
$ npx skills add paradevai/paradev --skill find-in-sentry -a github-copilot -y
OpenCode
$ npx skills add paradevai/paradev --skill find-in-sentry -a opencode -y
Windsurf
$ npx skills add paradevai/paradev --skill find-in-sentry -a windsurf -y
name: find-in-sentry description: Answer "what's breaking" questions from Sentry — find the right org and project, search issues and errors with the vocabulary Sentry uses, and report what is actually firing rather than the first hit. Use when the user asks what errors are happening, whether something is stable, what changed since a release, or for any health summary of a service. argument-hint: the service, error, release, or question to look up allowed-tools: mcp__sentry__find_organizations, mcp__sentry__find_projects, mcp__sentry__search_issues, mcp__sentry__search_errors, mcp__sentry__get_sentry_resource, mcp__sentry__search_sentry_tools, mcp__sentry__execute_sentry_tool
Sentry answers precise questions precisely and vague questions misleadingly. The work is scoping the question before searching, and ranking what comes back by impact instead of by relevance.
Run `find_organizations` and `find_projects` before searching if you are not certain where the code reports to. A monorepo often maps to several Sentry projects (api, web, desktop), and a search in the wrong one returns a confident, empty answer. Say which project you searched.
"Is checkout broken?" becomes queries on what Sentry actually stores: the error type, the transaction or URL, the release. Prefer `search_issues` for "what problems exist" and `search_errors` for "how often / for whom / since when". Run two or three narrow queries over one broad one, and time-bound them — `is:unresolved` over the last 24h answers a different question than all-time.
The issues worth reporting are the ones with high event counts, many affected users, or a first-seen that matches a recent release. A brand-new issue with three events can matter more than a year-old one with thousands — say why the ones you picked matter. When a number is load-bearing (error rate, affected users), take it from `search_errors` rather than eyeballing the issue list.
Every issue you cite gets its Sentry link and the window you looked at. "No matching issues in the last 7 days in `api`" is a complete, useful answer — silence about scope is how "it's fine" turns out to mean "I searched the wrong project".
questions; filter to the environment the user cares about.
than one issue hitting every user; lead with events and users affected.
window or the prior release, not against zero.
Paradev is an open-source Codex App and Conductor alternative. Orchestrate an army coding agents in parallel with your own subscriptions.
Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword,…
Build a brief for an upcoming meeting from Circleback — the calendar event, the history with the same people and company, open…
Work the action items Circleback captured — find what is assigned to this user, do the ones the workspace can do, and update…
Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and…
Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels,…
Answer "what did we say, decide, or promise" from Granola meeting notes — narrow to the meetings that can hold the answer, read…
Direct actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's…
Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…