import-art
将专辑封面复制到音频和内容目录的正确位置并按配置组织文件。
相关性达标的全量 Skills(含未精选长尾)· 共 5090 个
将专辑封面复制到音频和内容目录的正确位置并按配置组织文件。
展示插件可用技能、常见工作流与快速参考帮助信息。
运行插件健康检查,验证环境、依赖与技能注册状况。
为 bitwize-music 生成新的流派(genre)README 文件并规范化 slug。
扫描歌词并核验显性内容标注是否准确。
用浏览器自动化检索并下载公共档案与原始文献。
交互式设置或编辑插件配置文件并校验配置有效性。
将宣传视频与专辑内容上传到 S3 或 Cloudflare R2 存储。
将曲目内容复制到系统剪贴板以便粘贴到外部工具。
管理专辑创意库:增删查改并跟踪状态。
生成专辑制作进度面板,显示阶段完成率与阻塞项。
按七阶段流程设计专辑概念、叙事弧与曲目构架。
为专辑设计视觉概念并生成针对不同平台的 AI 艺术提示。
Keep an existing Figma design system aligned with the codebase as the code changes over time — propagating token, spacing, icon, colour or breakpoint changes into Figma and proving nothing broke. Use when code and Figma have drifted, when a design-system change in code must reach Figma (or the reverse), when auditing a Figma file against the code that ships, when deciding between variable modes and component variants, when a per-instance fix in Figma "succeeds" but nothing changes on canvas, when checking whether a Figma component's variants and props still match the code component, when checking contrast on token pairs inside the Figma file, when a Figma page or template is built from raw frames instead of component instances, when deciding which tier a component belongs to or in what order to build a component library, when a template's grid, margins or spacing need to come from tokens, or when building a DTCG token pipeline so the two sides cannot diverge. Complements figma-generate
Build and enforce a design system inside a codebase — token tiers that nothing can skip, and guards that stop the code from drifting off them. Works for both new and existing projects, which need different guards. Use when starting a project and setting up tokens and enforcement from the first commit, when installing design-system enforcement on an existing repo, when tokens exist but nobody uses them, when hardcoded colours/spacing/typography keep reappearing, when deciding between a ratchet and a hard rule, when a design-system guard needs writing, extending or debugging, when migrating a large codebase onto tokens without a red build from day one, or when a "we have tokens" system is not actually being consumed. The code-side counterpart of figma-generate-library and figma-code-sync.
为有 ADHD 的读者调整回复格式,突出下一步行动并保持会话持续模式。
使代理输出适配 ADHD 读者:强调下一步、列步骤、限制跑题与估时。
让 LLM 以自我改写方式管理并维护你的 Obsidian 知识库,实现长期自治的“第二大脑”。
Give this agent a real, routable IPv6 (/128) identity on the Whisper network, with safe egress and externally-verifiable identity (DNSSEC + RDAP). Keyless verification needs no account.
Sweep a repository to US English, sized by blast radius — every finding reported before anything changes, and identifier renames and string edits confirmed one at a time. Use when the user asks to check spelling or grammar across a repo, wants a consistent pass after spotting a single UK spelling, or is settling a project's language before a release or handoff.
Mentor — coach while the user writes every line themselves, so they learn by doing instead of receiving a finished diff. Use when someone asks for "mentor mode" or "learning mode", tells you not to do the work for them ("teach me, don't do it for me", "let me drive", "guide me, don't take over", "don't write it, help me write it"), or is learning a language or framework and wants to type it themselves. Not for someone who wants the code explained while you still write it.
Test-driven development gated on user approval of the failing test. Use when implementing new behavior, fixing a bug, or when the user asks for TDD by any name. Not for docs, config, or refactors already covered by tests.
Combines multiple open dependency-update PRs (Dependabot, Renovate, or any dep-update bot) into one branch and one PR, so CI runs once instead of once per bump. Fires on an explicit ask to combine them, and equally on the bare complaint that dependency PRs have piled up or that CI reruns on every bump. Reserved for collapsing several bot PRs into one: a single PR on its own (fixing a failing bump, closing it, merging it) and configuring the bot are other work.
Changesets — write the changeset file directly, since the interactive CLI asks questions an agent cannot answer. Use when a change to released code is ready to commit and has no changeset yet, when a check fails with "packages have been changed but no changesets were found", when only docs or tooling changed and the release needs an explicit "nothing to release", or when the user asks for a changeset, a release note, or a version bump. Not for running a release or editing versions and changelogs by hand — automation owns those.
Audit a repository's agent configuration for rot — pointers to things that moved, commands that no longer run, facts that stopped being true, wiring nothing ever registered. Use when the user asks to audit the agent config, CLAUDE.md or AGENTS.md; after restructuring the config layer; or when an agent has just followed an instruction that turned out to be wrong. Reads the instruction layer alone — the files an agent consults before it acts. Reports its findings and waits for approval before changing anything.
为 macOS/Windows 做只读磁盘占用扫描并生成交互式清理报告。
审计并收尾项目文档、代码与运行态,确保现役答案一致可交接。
把一句想法拆成可直接交给 agent 执行的目标任务书和验收标准。
以卡兹克(Khazix)风格生成公众号长文、扩写与续写稿件。
用横纵双轴法对产品/公司/技术做系统性深度研究并生成 PDF 报告。
通过 AI HOT 的公开 API 提供中文 AI 资讯、热榜与日报摘要。
Prices research, tests, surveys, dashboards and experiments before running them, by computing how much the result would raise expected utility - which is zero whenever no outcome would change the decision. Use when someone proposes an A/B test, user survey, market study, competitor analysis, analytics build, consultant, pilot, or "let's gather more data", and when deciding how large a study needs to be.
Separates signal from noise in metrics you cannot observe directly, updating a belief from evidence instead of reacting to the latest reading - Bayesian updates over competing explanations, and a filter that says whether this week's move is real. Use when a metric moves and someone wants to act, when diagnosing why traffic or revenue changed, when a dashboard number contradicts intuition, or when deciding whether a trend is real yet.
Validates a plan before committing to it - checks whether the ranking survives the assumptions, finds the most likely way it fails, and makes the trade-offs explicit via a Pareto frontier instead of an invented single score. Use before a launch, price change, migration, infrastructure change or major commitment, when running a premortem, when two objectives conflict, or when a decision depends on an assumption nobody has tested.
Models what a competitor will do next and what happens if you respond - best response, equilibrium, and the difference between a rival who optimises perfectly and one who does not. Use before a price change or price war, when a competitor launches something, when deciding whether to match a rival's move, when analysing a market with few players, or when someone asks "what will they do if we do this".
Decides how far ahead to plan, what to discount future payoffs by, and which backlog items can be dropped without analysis - using receding-horizon planning, an explicit discount factor, and branch-and-bound pruning against the incumbent. Use when building a roadmap, prioritising a backlog, arguing about short-term versus long-term, setting quarterly or annual plans, or when planning has become an end in itself.
Turns past decisions into calibrated judgment - scoring old predictions against what happened, assigning credit for delayed results, and separating a bad decision from a good decision that lost. Use during a retrospective, postmortem, quarterly or monthly review, when reviewing decisions taken 30+ days ago, when attributing a result to a cause, or when someone claims to have called something.
Turns a vague "what should we do about X" into a scored decision - explicit actions, an explicit unknown, an explicit prior, and one utility scale - then picks by maximum expected utility and checks the result for framing effects. Use when facing a choice between options under uncertainty, when a decision has stalled in circular debate, when someone asks "should we do A or B", or before writing any decision record, strategy memo, or roadmap commitment.
Splits scarce time, budget or traffic across competing products, channels, campaigns or variants by treating them as a multi-armed bandit - Thompson sampling over beta posteriors, with optimism for anything not yet tried enough to judge. Use when deciding what to work on next, how to divide a marketing budget, which product to prioritise, whether to kill something that is underperforming, or when picking a winner among test variants.
在隐私保护下发布临时化名资料并匹配互补的联合创始人或项目合伙人。