Loading...
Loading...
Found 10,388 Skills
Configure OMX notifications - unified entry point for all platforms
Intelligently handle git rebase operations and resolve merge conflicts while preserving features and maintaining code quality. Use when rebasing feature branches, resolving conflicts across commits, and ensuring clean linear history without losing changes.
Run Gemini CLI to take a screenshot for a specific page.
Run Codex to take a screenshot for a specific page.
Infobip integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Infobip data.
Webhook integration. Manage Recordses. Use when the user wants to interact with Webhook data.
Enforces complete execution, mode-aware delivery, compact sub-agent communication, independent agent-review gating, validation, and reporting for implementation, bugfix, hardening, documentation, specification, architecture, design, review, and post-mortem tasks. Use whenever work must be completed, reviewed, validated, or documented through an explicit execution mode instead of handled ad hoc.
Generates structured changelogs and release notes from git history and PR descriptions. Classifies changes into breaking, features, fixes, performance, and docs. Filters internal-only changes, detects breaking changes, and produces human-readable entries linked to source PRs. Triggers on: "generate changelog", "write release notes", "compose changelog", "what changed since", "changes since last release", "prepare release", "release notes for", "changelog for", "summarize changes", "diff since tag". Use this skill when preparing a release and needing to summarize changes for users.
Browse the XBTI Gallery — all community-created BTI personality tests at xbti.lovstudio.ai. Trigger when user says "XBTI Gallery", "xbti-gallery", "BTI列表", "浏览人格测试", "show BTI cases", or wants to see available BTI variants.
Use when deleting a Zeabur project. Use when user says "delete project", "remove project", or "clean up project". Use when tearing down test or temporary projects. Always confirm project name and ID with the user before deleting.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Use when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.