Loading...
Loading...
Found 99 Skills
Report a bug in the compound-engineering plugin
Break a plan into tracer-bullet tickets with blockers and publish via issue-tracker. Local files only if asked.
Fix a bug reported in a GitHub issue or a markdown file, without letting the report's noise and guesses into the main context. Takes an issue number, an issue URL, or a file path as an argument. Use when asked to fix, investigate, or reproduce a reported bug.
File contributor or agent papercuts as GitHub issues labeled friction, or investigate those issues as the daily friction-log Cloud Agent. Use when you hit repo friction, when asked to log friction, or when spawned to resolve open friction issues.
Interview the requester, then draft and file a complete Elastic documentation issue against the right template and repository — enforcing the good-issues quality bar, checking for duplicates and existing coverage first, rewriting implementation-side detail into user-facing terms, and routing sensitive requests privately. Use it to request docs for a feature, hand off notes or a pull request, request a UI copy review, report a problem with a published page, share support feedback privately, or ask how to request documentation support.
Track Remotion CI flakes in issue
Sweep flagged Outlook threads, or threads named by subject, into GitHub issues or comments.
Turn a spec into GitHub tickets using Matt Pocock's to-tickets skill, attaching every ticket as a native sub-issue, adding ticket, and defaulting to status/todo when no status/ label exists.
OPT-IN skill. Send developer-experience feedback about the TomTom Maps SDK for JavaScript (@tomtom-org/maps-sdk) to its public GitHub repository, tomtom-international/maps-sdk-js, as an issue or a discussion. Use at the START of any work with the SDK to ask the developer once for permission (the tomtom-maps-sdk-js skill hands over here for that), and after that whenever the SDK gets in the way while building — the docs, types or AI skill did not say what was needed; the API cannot express what the developer asked for; the code that actually works differs from what the docs or examples showcase; or something is plainly broken. Also use when the developer says "report this", "send feedback", "file an issue", "tell TomTom", "stop sending feedback", or asks what feedback has been collected so far. Drafts a redacted report and posts it only after the developer approves that draft.
Pulls a fitness report from a GitHub issue or from a local fitness report, addresses the action items by updating the codebase, and closes the issue when done. Use when the user says "apply review", "fix review issues", "address review feedback", "apply fitness report", "work through the action items", or provides a GitHub issue URL or number containing a fitness report, even if they don't say "fitness". Not for producing a new report (that's review-full).
Use when the user wants several open issues built by agents and turned into pull requests — "work through the issues", "implement the open issues", "clear the backlog", "open PRs for #12 and #15" — optionally at an effort level ("/implement-issues low", "at medium effort"), and when plan pull requests it opened are approved or have comments to answer. Works in Claude Code, Codex, or any agent that can dispatch subagents. Not for one issue the user is building themselves in this session.
Analyze an already-collected infrahub-collect diagnostic bundle — traceback and failure triage across service logs, incident correlation, and known-issue matching against opsmill/infrahub GitHub issues. TRIGGER when: the user says they collected a diagnostic bundle, gives you a bundle path, or pastes bundle contents — and asks what's wrong, wants the logs or tracebacks analyzed, asks "what does this bundle say", wants errors triaged/correlated, or asks whether a crash is a known issue. DO NOT TRIGGER when: no bundle exists yet — collect one first (use infrahub-collecting-diagnostics), filing the issue itself (use infrahub-reporting-issues), or querying live data (use infrahub-analyzing-data).