Loading...
Loading...
Found 9,340 Skills
Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style verification pass, then commit and push.
Diagnose what state one open PR is actually in — unfinished plan steps, missing review, unresolved conversations, red CI, base conflicts, missing QA evidence, merge-ready — then run the matching chain of om-* skills in order and publish a status report. Use for "finish PR 123", "what is left on PR 123", "drive PR 123 to the end".
Configure safe agent behavior around PlanetScale MCP, Insights, schema recommendations, and repository work without autonomous production mutation.
Collect, download, and verify App Store Connect Analytics reports with asc. Use when users need to discover analytics report requests, select report instances by processing date or granularity, download every segment, or verify downloaded files against Apple's size and MD5 metadata before analysis.
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legal_hold fields in _log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
Reuse one manually established Playwright login state across multiple isolated automation instances running in parallel, with routed Setup, Login, and Launch subflows. Use when a user asks to install or configure Playwright Chromium, manually establish or refresh a site's shared login state, open or automate a site with persisted authentication, verify shared authentication, take authenticated screenshots, or run concurrent authenticated browser work. On first use, automatically run Setup; prefer the read-only Launch subflow for normal daily automation.
Use when the user asks to "create an influencer brief" or "write a campaign brief"; produces a structured creator brief with deliverables, key messages, creative direction, timeline, disclosure rules, and compensation terms. Not for choosing how to split spend across creators — use budget-optimizer. 达人合作简报/创作者BF
This skill should be used when the user asks to "write a creative brief", "build a motion brief", "the client doesn't know what they want", "turn this vague client request into a brief", "what questions should I ask the client", or "make a brief I can get sign-off on". It turns a fuzzy client ask into a structured, sign-off-ready motion design brief and the exact clarifying questions to send back.
Own experiment evidence semantics: decide datasets, baselines, metrics, ablations, robustness tests, chart evidence, and exactly what rows or columns a result table should contain. Use for experiment design, benchmark planning, supplied-result evidence structure, result-table schema, chart-spec semantics, 设计实验, 对比实验, 消融, 结果表证据结构. Do not search literature as the main deliverable, visually beautify or render an already specified table/figure, improve layout/colors/readability, or invent results.
Synthesize GitHub delivery context into a concise Basic Memory project update. Use in CI after `bm ci collect` prepares a ProjectUpdateContext; return only structured AgentSynthesis JSON for `bm ci publish`.
Babysits or watches an open GitHub PR until merge-ready, continuously reacting to review comments, CI failures, and routine base movement throughout the PR's life. Use when asked to 'babysit the PR', 'watch the PR', monitor, or keep an eye on a PR over time — not a one-shot request to resolve review comments or debug one CI failure (those are separate skills). GitHub only, including GitHub Enterprise.
Create an exercise directory structure containing section, problem, solution, and explainer that passes lint checks. Use this when users want to build an exercise framework, create exercise templates, or set up new course chapters.