Showing 26131–26160 of 60114 skills
Use this agent when you need to perform custom bioinformatics analyses on genes or proteins that go beyond standard database lookups. This includes situations where existing domain/family annotations from UniProt are insufficient, when you need to verify dubious annotations, or when you need to perform comparative analyses across gene sets. The agent creates reproducible analysis pipelines with proper dependency management and documentation.
ai4curation/ai-gene-review
Use when running or wiring OpenScientist for AI Gene Review gene-function hypotheses, especially blinded comparisons against local bioinformatics analyses.
ai4curation/ai-gene-review
Manage and drive forward an ongoing project, tracked in projects/ dir
ai4curation/ai-gene-review
Analyze any existing codebase, discover its patterns and best practices, and generate an Espalier structure (rules, skills, wiki, pipeline) so AI coders produce code matching that project's language and conventions. Greenfield repos take the two-pass Decide-Then-Bind path (/espalier-map charts the conventions, init binds them); boilerplate repos run init normally, then map the product. Wires into Claude Code, Codex, and/or GitHub Copilot (.claude/, .agents/skills/ + .codex/, .github/).
Junhanliu-dev/espalier-engineering
Continue game-art production from a director's project pack. Assign and create related characters, environments, props, UI and animation, review them in context, and export optional Compositor scenes without inventing another visual style.
NewenergyEric/art-director-skill
grill-me / 访谈 / 一问一答拷问(一次问一个)/ 压力测试方案 / stress-test a plan — lightweight one-question-at-a-time interview to challenge a plan, design, API shape, data model, or feature direction before implementation. Skip 拷问用的问题池·推荐默认值等材料,以及拷问后的结论整理(不是逐问过程)→ requirement-intent;code-level YAGNI/delete/adversarial review of written code → `product-rd-workflow`'s independent-review gate; full delivery/spec/plan authoring → product-rd-workflow; tests → testing-strategy; implementation → stack/dev skill; process lesson extraction → skill-extraction-workflow.
ccoalm/ccl-skills
Use when designing, reviewing, debugging, or shipping observability — service logs, metrics, distributed tracing, log/trace correlation, 给接口·服务加结构化日志与 trace 透传, dashboards, alerts, on-call routing(值班/排班 SOP、P0/P1 打断;发布值班/回滚除外), SLI/SLO, error budgets, 线上是否已启用(开关·配置在生产的实际生效状态)— for a backend product. Owns the cross-cutting evidence layer — what signals must exist, what fields must propagate, what middleware must auto-wire, what verification proves a change is observable in production. Hand off mesh/routing/mTLS to `platform-service-connectivity`, release gates and rollback evidence to `platform-release-engineering`, service-internal architecture (HTTP/RPC/DB/queue) to `software-architecture`. Product-agnostic.
ccoalm/ccl-skills
发布 / 灰度 / canary / rollback / rollout / 环境泳道 / promotion gate / 发布值班 SOP(P0·P1 打断排班、是否回滚)→ design or review how a change moves from build to traffic and back safely, including rollout strategy, approval, rollback, secrets, config, and deploy control planes. Skip when the ask is the production release lifecycle — 上线范围确认 / 合并 main / 打 tag / 生产构建 / 发布后 reset → release-coordination; release document substance → release-doc-writer.
ccoalm/ccl-skills
服务互通 / service mesh / service discovery / mTLS / retry / timeout / circuit breaker / lane routing → design or debug how one request safely reaches another service across environments, mesh, clients, HTTP/RPC, and queues.
ccoalm/ccl-skills
现状盘点 / 当前能力梳理 / 按当前代码说明现状(某状态·数据怎么产生和消费)/ 现有流程、页面、API、数据、运营规则盘点 / as-is audit / current state inventory —— 交付物是**现状清单本身**:现在怎么运作、已有哪些能力与例外、事实来源与 freshness、缺口和冲突,含按 commit 固定的代码现状取证。Skip 要的是意图、用户故事、验收标准、问题池(「到底要什么」)→ requirement-intent;要的是本轮改哪些、不改哪些、切几版(变更边界)→ requirement-scope;问线上是否已启用 → platform-observability;代码/项目质量评估 → product-rd-workflow;bug 根因 → defect-diagnosis。
ccoalm/ccl-skills
写 PRD / 需求文档 / 产品需求文档 / 需求说明 / user story 文档 / 验收标准文档 / 产品需求正文 —— 在 lifecycle 判定 PRD Ready 之后,把已关闭的需求组装成人读的 PRD。Skip 需求实质不清 → requirement-intent;缺现状事实 → requirement-baseline;范围/版本切片/开放决策未关闭 → requirement-scope;Agent/Machine 技术规格 → llm-inference-integration;其评测与测试层 → testing-strategy;只是润色措辞 → tighten-doc;写完 PRD 还要接着往下做的多阶段研发交付·实现/发布计划 → product-rd-workflow。
ccoalm/ccl-skills
产品需求沟通 / 需求讨论完善 / 产品需求澄清 / 澄清 PRD / 需求对齐会 / 需求讨论会后整理 / 用户故事 / 验收标准 / 产品意图 / 需求不清楚 / clarify requirement / requirement discussion —— 交付物是「这需求到底要什么」:意图、目标用户、成功标准、用户路径、意图级非目标、功能点验收点、拷问问题池、决策关闭 backlog。Skip 要的是现状清单(现有流程·页面·API·数据·运营规则怎么运作、已有什么能力、缺口在哪)→ requirement-baseline;要的是变更边界(in/out、受影响对象、依赖、版本切片、appetite)→ requirement-scope;要成文 PRD → requirement-doc-writer;一问一答拷问 → grill-me;已有 spec/PRD 实质内容写错要改对(substance 修正,非澄清)、多阶段交付计划 → product-rd-workflow。
ccoalm/ccl-skills
改动范围 / 影响范围 / scope / 需求拆分 / MVP 边界 / 非目标 / 版本切片 / 兼容·回滚降级边界 / 变更影响 / appetite / timebox —— 交付物是**变更边界**:in/out scope、受影响对象、依赖、MVP 与后续切片、appetite 与砍项、每个切片的验收范围。前提是方向已定。Skip 方向还没定、要先弄清「到底要什么」→ requirement-intent;要的是现状清单(现在怎么运作、有什么能力)→ requirement-baseline;风险定级与要哪些 gate → feature-risk-router;实现/发布计划 → product-rd-workflow;测试范围 → testing-strategy。
ccoalm/ccl-skills
Create and maintain structured test cases from requirements or code, including initializing or reusing the Feishu Bitable, canonical fields, import, update, status sync, and deprecation. Use for 写测试用例, 写测试用例文档, test-case documents, TC, source-to-TC generation, 初始化测试用例多维表格, 测试用例放飞书, and 导入/更新/同步/废弃测试用例. Skip executable test code, coverage, CI gates, mocks, and regression verification → testing-strategy; broader feature delivery → product-rd-workflow.
ccoalm/ccl-skills
Spoken: read a specific passage the user named (read this aloud) by running the plugin CLI. Not for routine per-turn status.
akunzai/agent-skills
The last mile: enroll a graded list into a built (inactive) sequence, get a human to approve activation, and pull contacts on complaint or bad fit. Use to take an Apollo sequence live safely.
creatop-gtm/apollo-operator
Turn a business and its ICP into a real Apollo search, a shared profile.yaml, and one to three custom scoring signals, validated on a sample. Use to define who to target on Apollo before building a list.
creatop-gtm/apollo-operator
Build a clean, enriched, graded lead list on Apollo: paginated search, dedupe, credit-aware enrichment, scoring signals, email verification, then grade. Use to build the full prospect list after the ICP is set.
creatop-gtm/apollo-operator
Optional layer on top of email: add LinkedIn, call, and manual steps to an Apollo sequence and work the task queue they create. Apollo automates email only; the rest are human tasks. Use to run multichannel outbound on Apollo.
creatop-gtm/apollo-operator
The four ways to run Apollo headless and how to choose: MCP (typed tools, results always through context), the apollo CLI binary (disk output, common filters), REST authenticated with the CLI's own OAuth token (full MCP filter surface WITH disk output, no API key), and REST with an API key. Includes measured context costs, credit costs per lane, verified command recipes, and the kill switch for stopping a live sequence. Use to decide which lane a task should run on.
creatop-gtm/apollo-operator
Write a 3-step, 2-variation cold email sequence matched to the persona (ATL or BTL) and build it in Apollo as an inactive draft. Use to write and create outbound sequences on Apollo.
creatop-gtm/apollo-operator
Build one readable brief.md capturing the business: identity, offer, who buys and why, objections, proof, and voice. The narrative context layer every other skill reads. Use before ICP work, when copy comes out generic, or when the business changes.
creatop-gtm/apollo-operator
Operator context for running B2B outbound on Apollo.io through the Apollo MCP. Load this first. Provides the Apollo tool map, universal deliverability and copy rules, the shared profile.yaml object, and routing to every other Apollo Operator skill. Use for any outbound task on Apollo: targeting, list building, sequences, deliverability, sending, or iteration.
creatop-gtm/apollo-operator
Classify replies and compute positive reply rate, the metric that predicts revenue. Use to tell whether a campaign is actually working, not just getting replies.
creatop-gtm/apollo-operator
Build the sending stack from zero before you send: dedicated domains separate from your primary, mailboxes, SPF/DKIM/DMARC/MX, redirect, and warmup. Includes the volume math (mailboxes and domains per daily send target). Use for first-time setup or when scaling adds mailboxes.
creatop-gtm/apollo-operator
Use for this repository when the maintainer asks to prepare or publish a release — «подготовь релиз», «выпусти релиз», "prepare a release", "publish the release". Do not use for ordinary changelog edits, package validation, commits, pushes, or pull requests that are not explicitly a release.
xonika9/agent-skills
Подбирает и сравнивает товары на Wildberries/WB, проверяет карточки, отзывы, продавцов и варианты товара перед покупкой. Не применяется к другим магазинам и общим вопросам о товарах без намерения выбрать или проверить их на WB. В Claude Code требует текущую сессию Opus.
xonika9/agent-skills
统计 conf-app 的 AI Chat 和 AI Repair 线上使用情况,汇报入口曝光、请求次数、 去重用户和租户、返回与应用结果、失败及结果缺失、耗时和租户分布。 用于“近7天 AI 使用情况”、AI Chat/Repair 周报或指定日期的使用统计; 模型评测、单次修复诊断和 AI 标题生成使用各自流程。
ZenUml/conf-app
Use agent-browser with the dedicated support@zenuml.com Atlassian Developer Console profile for console workflows that lack an API, including definitive feature-flag inventory and UI-only flag changes. Use for developer.atlassian.com Console inspection or mutation; for feature flags, pair with the forge-feature-flag skill.
ZenUml/conf-app
Create, enable, scope, and verify Atlassian Forge feature flags for Confluence apps. Use when asked to enable, roll out, disable, create, or check a Forge Feature Flag, especially before or after a release.
ZenUml/conf-app