bugsnag

Description

**UNIVERSAL TRIGGER**: Use when user wants to GET/FETCH/RETRIEVE any data FROM Bugsnag. Common patterns: - "get/show/list/display [something] from bugsnag" - "получить/показать/вывести [что-то] из bugsnag" - "bugsnag [organizations/projects/errors/details/events/comments/stats]" - "what [data] in bugsnag", "check bugsnag [resource]" Specific data types supported: 📊 **Organizations & Projects**: - "list bugsnag organizations/orgs", "show organizations" - "list bugsnag projects", "available projects", "проекты bugsnag" 🐛 **Errors (viewing)**: - "show/list bugsnag errors", "что в bugsnag", "check bugsnag" - "open errors", "error list", "ошибки bugsnag", "открытые ошибки" - "errors with severity error/warning", "filter bugsnag errors" 🔍 **Error Details**: - "bugsnag details for <id>", "error details", "детали ошибки" - "show stack trace", "error context", "what happened in error" - "events for error", "error timeline", "события ошибки" 💬 **Comments**: - "show comments for error", "error comments", "комментарии ошибки" - "bugsnag discussion", "what comments on error" 📈 **Analysis**: - "analyze bugsnag errors", "error patterns", "анализ ошибок" - "bugsnag statistics", "error trends", "что происходит в bugsnag" ✅ **Management** (write operations): - "mark as fixed/resolved", "fix error", "resolve error", "close error" - "закрыть ошибку", "отметить как решенную", "исправить ошибку" - "add comment to error", "comment on bugsnag error" - NOTE: Fix/Resolve/Close are synonyms - all mark error as resolved in Bugsnag TRIGGERS: bugsnag, получить из bugsnag, показать bugsnag, список bugsnag, bugsnag data, bugsnag info, check bugsnag, what in bugsnag, bugsnag status, error tracking, error monitoring, production errors, stack trace, bugsnag organizations, bugsnag projects, bugsnag errors, bugsnag details, bugsnag events, bugsnag comments, bugsnag analysis, ошибки в bugsnag, что в bugsnag, проверить bugsnag, данные bugsnag, fix error, resolve error, close error, закрыть ошибку, исправить ошибку, отметить как решенную This skill provides complete Bugsnag API integration for viewing and managing error tracking data via Ruby helper scripts.

Tool Access

2 tools

Limited to specific tools

Supporting Files

6 files

Additional assets for this skill

Tool Access

This skill is limited to using the following tools:

BashRead

Supporting Assets

README.md

TESTING.md

TRIGGER_EXAMPLES.md

bugsnag.rb

bugsnag_api_client.rb

bugsnag_helper.rb

Links

GitHub Stats

0 forks

Updated 2 days ago

Related Skills

Agent Development

46.0K

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

46.0K

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev

Hook Development

46.0K

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

From plugin-dev