2.1K skills · sorted by relevance
Status match and status challenge rules for airlines and hotels. Covers free direct matches, paid concierge via statusmatch.com with fees, card-granted status, and critical lifetime/once-per-N-years restrictions that make wasted matches expensive.
The English summary is being prepared. Showing the original description.
Generate comprehensive status reports for git repositories. Analyzes commits, codebase structure, type errors, branch health, dependency status, GitHub PRs/issues/CI, working tree changes, and optionally integrates with `td` (task management CLI) if a `.todos` folder is present. **TRIGGERS - Use this skill when:** - User asks for the status of a git project or repo - User asks "what's going on in [project]" or "give me an overview of [repo]" - User wants a project summary, progress report, or codebase overview - User asks about recent commits, code structure, or project health - User says "check my project" or "project status" **Output:** A rich, structured text report covering overview, branches, commit history, codebase breakdown, GitHub activity, dependency health, issues/errors, working tree changes, task management, and summary.
The English summary is being prepared. Showing the original description.
Write a structured client status report for a consulting engagement. Use when a consultant says "write my weekly status update", "I need to send a status report", "draft the client update", "what should be in the weekly report", "client wants a progress update", "help me write the RAG status", "I need to report on blockers", "end of week update to the client", or "help me communicate what's stuck". Also trigger when someone needs to communicate engagement progress, surface blockers to the client, or flag decisions that need to be made by the sponsor.
The English summary is being prepared. Showing the original description.
Register a custom WooCommerce payment gateway — extend WC_Payment_Gateway, declare $id / $title / $supports, implement process_payment returning array(result, redirect), optionally process_refund when refunds is in supports, register via the woocommerce_payment_gateways filter. The single most-confused thing AI gets wrong is payment_complete vs update_status — payment_complete runs the canonical paid-order state machine (status, transaction id, session flag, woocommerce_payment_complete action), update_status only changes the status string. Includes the always-forgotten WC cart empty_cart call after success. Use when integrating a payment provider, reviewing gateway code, or debugging "payment succeeded but cart didn't clear" / "order stuck in pending". Triggers on WC_Payment_Gateway, woocommerce_payment_gateways, process_payment, process_refund, payment_complete, get_return_url, woocommerce_payment_complete_order_status.
The English summary is being prepared. Showing the original description.
Use when working with Atlassian Statuspage — atlassian Statuspage management, component monitoring, incident communication, scheduled maintenance, and subscriber notifications. Covers page configuration, component group management, incident lifecycle, metric tracking, and uptime reporting. Use when managing public or private status pages, communicating outages, scheduling maintenance, or reviewing component uptime in Atlassian Statuspage.
The English summary is being prepared. Showing the original description.
Design and review REST APIs with consistent URLs, HTTP status codes, error responses, and pagination, which divides results into smaller batches. Covers authentication, access limits, and versioning to help define clear behavior for API users.
Check live H100 or H200 GPU availability, request fixed-rate quotes, and review procurement status through the canonical Itô client. It also supports device credential revocation and explicitly authorized node checks; quote requests do not reserve capacity.
Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.
Build a tabbed project status page with goals, workstreams, owners, risks, and next actions. Publish it privately on claude.ai, then refresh the same URL from current sources and report what changed since the previous update.
Diagnose missing recall, failed captures, and connection errors in the OpenViking memory plugin for Codex. Check installation, configuration, authentication, and server readiness, then use the findings to guide fixes and verify that memory works again.
Diagnose OpenViking memory problems by checking plugin installation, client settings, server connections, and recent activity. The skill helps trace missing recalled context, failed saves, and authentication errors, then guides targeted fixes and checks whether they worked.
Add a NanoClaw status icon to the macOS menu bar. Check whether the service is running through a green or red dot, then start, stop, restart, or open its logs from the menu.
Turn project or team updates into a structured report for leaders and stakeholders. The skill summarizes key metrics, accomplishments, ongoing work, risks, decisions needed, and next-period priorities, with an overall assessment of whether work is on track.
Manage version control through GitButler’s but CLI. Select files or hunks, meaning sections of a diff, for commits; organize dependent branches, split or combine history, resolve conflicts, and create pull requests using task-specific command workflows.
Diagnose GKE nodes marked NotReady or Unknown using node conditions, events, logs, and resource metrics. The skill gathers evidence, distinguishes temporary transitions from faults, and proposes fixes for a person to apply.
Find Linear issues by text, assignee, or status, and read their details and comments. Prepare new issues, comments, and status changes for user approval, then return identifiers and links so results can be checked.
Draft a Linear project update by comparing current issues with the previous report. Explain progress, added scope, schedule risks, and one needed decision, then publish the update to the project after the user approves it.
Diagnose unexpected terminal-tools results, including empty output, missing exit codes, expired output handles, and busy sessions. Use returned status fields to distinguish ongoing work, output limits, shell behavior, and failures, then choose a recovery step.
Track legal work after an acquisition closes, including counterparty consents, contract transfers, and purchase agreement deadlines. Build phased workplans from available deal documents, update progress, and produce status reports or CSV exports for review.
Build dashboard panels in plain TypeScript with automatic retries, saved panel settings, and clear error states. Keep panel-specific helper functions in the same file to make each component easier to understand and maintain.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
The English summary is being prepared. Showing the original description.
Manage git worktrees across any repository with the `gwm` Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (`gwm exec`) or reclaim build artifacts (`gwm clean`), materialise a PR into a worktree (`gwm review`), drive a multi-repo workspace (`--workspace`), run the JSON daemon / statusline (`gwm daemon`, `gwm statusline`), list or pin AI-agent sessions per worktree (`gwm agents`, Claude Code / Codex / opencode / Mistral Vibe detection), seed config from a preset (`gwm init --preset`), diagnose with `gwm doctor`, drive tmux/zellij, or wire `gcd` via `gwm shell-init`. Also covers multi-forge (#419): GitHub via `gh` **or** GitLab via `glab`, the `forge` / `[forge_hosts]` keys, and `gwm trust add`. Triggers on `gwm`, `gwq`, `git worktree`, `.gwm.toml`, `forge`, `forge_hosts`, `glab`, `gwm trust add`, GitLab MR, `gwm create`, `gwm list`, `gwm exec`, `gwm clean`, `gwm review`, `gwm daemon`, `gwm statusline`, `gwm agents`, `gwm note`, `gwm bootstrap`, `gwm doctor`, `gwm switch`, `gwm tmux`, `gwm zellij`, `gwm link`, `gwm status`, `gwm shell-init`, `gcd`, `feat/#`, `fix/#`, GitHub issue/PR linking on a worktree.
The English summary is being prepared. Showing the original description.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
The English summary is being prepared. Showing the original description.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
The English summary is being prepared. Showing the original description.