2.2K skills · sorted by relevance
Add a short status line to the end of agent responses so readers can see whether work is finished, a specific follow-up remains, or progress depends on their input.
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.
AI-DLC v3（AI-Driven Development Lifecycle）のオーケストレーター。 define / develop / release / reflect の 4 フェーズコマンドと status / doctor の 補助コマンド、連続実行ラッパ express、旧名エイリアス（inception / construction / operations / retrospective）を統一的にルーティングする。 define / develop（normal / risky 含む）/ release / reflect の各フェーズフローと status / doctor の補助コマンドを実装済み（doctor は shallow scope）。
The English summary is being prepared. Showing the original description.
Generate weekly or monthly status updates from local PM data. Use this skill when: - It's end of week and you need a status update for leadership or stakeholders - You need a monthly executive summary - You want to draft an email update using data from meetings, tracker tickets, and decisions - The user says "weekly update", "status report", "what happened this week?", "weekly summary" - The user says "Friday update", "send status email", "EOW update" Pulls from work logs, meetings, ticket tracker, and decisions — no manual input needed.
The English summary is being prepared. Showing the original description.
Use when configuring or troubleshooting Salesforce CPQ contract creation, subscription management, amendment quotes, or renewal quotes. Trigger keywords: contract, amendment, renewal, subscription, co-termination, SBQQ__Subscription__c. NOT for designing the amendment/renewal architecture or swap pattern — use architect/subscription-management-architecture. NOT for amending or renewing contracts from Apex — use apex/cpq-api-and-automation. Also covers the standard Contract and Order objects underneath CPQ — Contract Status vs StatusCode, activation locking, EndDate auto-calculation, ContractSettings and OrderSettings, reduction orders, and renewal-reminder automation. Trigger keywords: Contract, ContractStatus, StatusCode, ActivatedDate, OwnerExpirationNotice, ContractTerm, EndDate, Order, OrderItem, reduction order, ContractSettings, OrderSettings, renewal reminder. NOT for Revenue Cloud or Subscription Management objects — use architect/revenue-cloud-architecture and architect/subscription-management-architecture.
The English summary is being prepared. Showing the original description.
GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or "give me a handoff summary of open work". NOT for code review (see mk:review-pr); NOT for PR creation (see mk:ship); NOT for git operations (see mk:ship / mk:resolving-merge-conflicts).
The English summary is being prepared. Showing the original description.
Check GitHub Actions CI status for PRs and branches. Use when the user asks "did CI pass", "check status", "what failed", "are checks green", "PR checks", "CI status", "workflow status", "re-run jobs", or wants a quick summary of GitHub Actions runs for a PR or the current branch.
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.
Use this skill when the implementation status column of a statement of applicability may not match reality, and the team asks "is our SoA accurate", "check the implemented column", "do we have evidence for every implemented control", "reconcile the SoA with our evidence", "pre-audit evidence check" or "the auditor found a control marked implemented with no records". Samples the records behind every control marked implemented, grades the evidence, proposes a corrected status for each row and writes a reconciliation table plus an evidence gap list with owners.
The English summary is being prepared. Showing the original description.
Maintains four living project files (overview and progress log, decision log, RAID log, links) from the mail, channel posts, documents and meeting notes the user attaches or the agent can reach, returns each touched file complete in the chat for the user to save, and builds a weekly DRAFT status report from those files. Use when the user asks to "set up tracking for project X", "catch the project files up", "log this decision against the project", "add this risk to the RAID log", "save this link to the project" or "write this week's status report". Do not use for reviewing an existing RAID log for stale or ownerless entries, use raid-log-review instead; for an HTML status page, use project-dashboard-builder; for minutes of one meeting, use meeting-minutes-writer. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Builds a DRAFT month-end, quarter-end or year-end close checklist and status table for a finance team from the close calendar, the open items list and last month's close issues that the user attaches, pastes or the agent can reach, marks every task on time, due, late, at risk or blocked, and flags dependency chains and repeat issues. Use when the user asks to "build the close checklist", "where are we on the month-end close", "what is late or blocked in the close", "refresh the close tracker as of today" or "prepare the close status note". Do not use for a project tracker or weekly project status, use project-status-tracker instead; for corrective actions from audits or NCRs, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Builds a self-contained single-file HTML project dashboard (status banner, milestones table, risks heat list, decisions log, links) from the project tracker files the user attaches, pastes or holds in configured knowledge sources, and returns the complete HTML source in chat ready to save as dashboard-project-date.html. Use when the user asks to "build a dashboard for this project", "make a status page I can pin in the team channel", "give me an HTML overview of milestones, risks and decisions", "refresh the project dashboard from the tracker" or "turn these tracker files into a one-page visual summary". Do not use for creating or updating the tracker files or for the written weekly status report, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Write an evidence-based status update from Linear data - summarize what shipped, what is in progress, what is blocked or stale for a project, cycle, or a person's issues, and optionally post it as a Linear project status update after the user approves the text. Use for "status for project X", "weekly update", "what moved this cycle".
The English summary is being prepared. Showing the original description.
プロジェクトアイテムのフィールド値 (Status/Priority/Size 他) をクエリフィルタやアイテム指定で絞り込んで一括更新する。SINGLE_SELECT/TEXT/NUMBER/DATE のフィールドタイプに対応。「Status を In Progress に変更」「優先度を一括更新」「Todo を全部 In Progress に」などで使用。
The English summary is being prepared. Showing the original description.
status:needs-investigation な issue を並列調査し、結果をコメントして status:investigated に更新する
The English summary is being prepared. Showing the original description.
status:investigated な issue の調査結果コメントを読み、実装可能なら status:ready に昇格させる
The English summary is being prepared. Showing the original description.
Start and manage voice calls from OpenClaw. Use command-line commands or an agent tool to send spoken messages, continue calls, check their status, and end them through Twilio, Telnyx, Plivo, or a mock provider.
Check Foodora order history, active order status, and arrival information through ordercli. Monitor ongoing orders, inspect individual order details, or preview and confirm adding items from a previous order to your cart.
Control an Eight Sleep pod through the eightctl command-line tool. Check its status, switch it on or off, adjust temperature, manage alarms and schedules, and control audio playback or the base angle.
Work with X through authenticated commands for posting, replying, searching, direct messages, and media uploads. Read posts, inspect followers and authentication status, or call v2 API endpoints directly when a shortcut command does not cover the task.
Schedule and publish social posts across multiple platforms through SocialClaw. Upload media, prepare campaign schedules, validate them before publishing, and check delivery status using connected accounts and a single workspace API key.