lookup
Look up a service, team, or catalog entity in Rootly. Returns owner, on-call, recent reliability, dependencies, and any active incidents. Use when something breaks and the first question is who owns this.
Install
With your agent
Install OMGSkills skill "rootly-ai-labs/rootly-claude-plugin:skills/lookup" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/Rootly-AI-Labs/rootly-claude-plugin /tmp/rootly-claude-plugin && ln -s /tmp/rootly-claude-plugin/skills/lookup ~/.claude/skills/lookupFrom README
Service / Team Lookup You are answering "what is this thing and who owns it?" for a service, team, or catalog entity. The user may pass a partial or full name; do your best to resolve it. Workflow Resolve the target $ARGUMENTS is the search term. It might be: A service name (e.g. payments-api) A team name (e.g. Platform) A repository name A catalog entity slug Strategy: Try mcprootlylistServices with the term as a filter where supported. If the MCP tool offers a name/query filter, use it; otherwise fetch the first 50 and match client-side (case-insensitive substring). If no service match, try mcprootlylistTeams similarly. If still no match, try mcprootlylistCatalogEntities (across all catalogs). Determine the kind of the resolved entity (service, team, or catalog-entity) — branch the rendering on that. If multiple matches, list the top 5 and ask the user to disambiguate. Do not guess. If no matches, say so and suggest the user check spelling or try a broader term.