Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
treasure-data/td-skills Complete workflow to set up RT 2.0 personalization from scratch - validates parent segment RT status, discovers event tables and attributes, configures RT infrastructure (events, attributes, ID stitching), creates personalization service, and deploys the personalization entity with payload. Use when user wants to "create realtime setup and build personalization" or "set up RT personalization end-to-end". Includes automatic validation using rt-personalization-validation skill to prevent common API errors. | Skills | |
ClawBio/ClawBio Query metadata and download data from the NCBI Gene Expression Omnibus (GEO). Works with GEO accessions (GSE series, GSM samples, GPL platforms, GDS datasets) to search GEO DataSets, fetch series and sample metadata, list and download series matrix / SOFT / MINiML / supplementary files, fetch the SRA Run Selector files, and emit a standardised metadata.tsv plus a pipeline-ready nf-core/rnaseq or nf-core/scrnaseq samplesheet.csv. | Skills | |
modu-ai/moai-adk Author editable SVG technical infographics — architecture, flow, comparison, hierarchy — by computing the layout numerically before writing markup, then rendering a 2x PNG via headless Chromium. Carries a CJK-first font stack, a deterministic source lint, and mermaid-vs-SVG selection rules. | Skills | |
dotnet/dotnet Implementation details for EF Core migrations. Use when changing MigrationsSqlGenerator, model diffing, migration operations, HistoryRepository, the Migrator or related classes. | Skills | |
tesslio/tessl-eval-demo Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow. | Skills | |
wondelai/skills Build empowered product teams using discovery and delivery dual-track. Use when the user mentions "product discovery", "empowered teams", "feature factory", "opportunity assessment", "product vision", "product strategy", "what should we build", or "our roadmap is just a feature list". Also trigger when restructuring teams away from output-driven models, or deciding what to build next based on outcomes. Covers discovery techniques, team structure, opportunity assessment, vision/strategy, and continuous delivery. For customer interviews, see mom-test. For ongoing discovery systems, see continuous-discovery. | Skills | |
compozy/compozy General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches. | Skills | |
zts212653/clowder-ai 按问题与证据缺口选择记忆检索范围(8 类题型参考)。 Use when: 任务是 "哪些地方提过 X" / "X 的来源 / source map" / "有没有提过 Y / absence check" / "上次到现在变了什么 / delta" / 冷启动 onboard 复杂主题 / 任何召回任务搜了一刀觉得不够。 Not for: 只是选哪个入口走第一刀(用 memory-navigation)/ 已知精确 anchor 单 Read(直接 Read)/ 代码符号查(Grep/LSP)/ 新功能开发(不是 recall 任务)。 Output: 单一 owner 汇总原始证据、实际覆盖与未验证边界,一次交付。 GOTCHA: memory-navigation 选择入口;本 skill 处理证据缺口与覆盖边界,不按模型家族或固定轮次决定停止。 | Skills | |
cocoindex-io/cocoindex-code This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'. | Skills | |
microsoft/vscode-pull-request-github Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository. | Skills | |
yyeret/portfolio-pdlc Run a lightweight, evidence-based "sniff test" on a single initiative (epic, project, or Tier-1 bet) to find where its clarity is insufficient for its stage in the Portfolio PDLC lifecycle, so you can drive the right investment/commit and derisking conversations. Best run pointed at where the initiative is managed (its folder/workspace, Confluence space, or Jira epic) or given its Lean Product Canvas plus a recent sponsor update; with little input it asks for context first. Use when pressure-testing an initiative before a Plan/Commit decision or Execute/Build commitment, checking whether a Lean Product Canvas and Discovery plan match the real risks, or coaching on leading indicators and risk-appropriate derisking. For multi-initiative board patterns, use the sniff-test-portfolio add-on. | Skills | |
yyeret/portfolio-pdlc Run a portfolio-level, product-oriented PDLC (Explore → Discovery → Plan/Commit → Execute → Rollout → BAU, with humans keeping the investment decisions) as an operating loop that leaves the portfolio sharper every cycle, over a plain-file workspace. Use when standing up, operating, or resuming a portfolio of initiatives/epics — seeing where everything is, advancing initiatives with evidence, improving artifact quality and outcome orientation, and continuously improving the process and portfolio construction themselves. Entry point and operating loop for the portfolio-pdlc-* skill family; for one-off diagnostics of a single initiative use sniff-test instead. | Skills | |
yyeret/portfolio-pdlc White-box assessment of a spec-driven harness or coding-agent configuration from a public GitHub repository, local directory, ZIP archive, or effective instruction hierarchy. Use when a CTO, VPE, or AI adoption leader wants evidence-backed feedback on outcome discovery, trustworthy delivery, in-use validation, and how the harness improves its own loop. For a produced spec as black-box evidence, use pdlc-readiness instead. | Skills | |
yyeret/portfolio-pdlc Bind a flow workspace to wherever the work is actually managed — GitHub Issues and Projects, Jira, Linear, an internal Kanban dashboard, a spreadsheet, or chat — by choosing a system-of-record mode (files-only, mirror, adopt, split), writing a field-ownership map with exactly one writer per field, and using the board export plus the harness's own tools to sync. Use when leadership needs the flow where they already look, when a tracker already holds the work, or when a sync has started fighting the workspace. Part of the flow-driven family. | Skills | |
yyeret/portfolio-pdlc Decide what a workflow should measure and wire it in — flow measures (WIP, age, cycle time, throughput, rework), evidence measures (coverage, first-pass yield, escape rate, check agreement), leverage measures (delegate mix, human minutes per item, escalation rate, cost per item), and the outcome measure the stream exists for — with each measure named on the steps that feed it and a baseline taken before anything changes. Use when defining a workflow, when a board has numbers nobody steers with, or before making any workflow-improvement bet. Part of the flow-driven family. | Skills | |
yyeret/portfolio-pdlc Run the meta-loop — inspect and adapt the workflow itself. Probe the flow (constraint drift, rework hotspots, WIP theatre, decision starvation), the evidence (watermelon steps, checks that always pass, self-graded work), the delegation (rung mismatches, escalation droughts, context rot, platform stall), and the definition of workflow (policy contradictions, silent drift, measures nobody steers with) — then capture improvement bets with benefit hypotheses and kill criteria instead of changing anything on the spot. Use on the meta-loop cadence, after recurring findings, or when the board is clean enough to earn self-improvement. Loop 2 of the flow-driven family. | Skills | |
Drakkar-Software/OctoBot End-user UX for node_web_interface (React) and web_interface (Flask/templates): entry-level trading terms OK, no pro-trader jargon, minimal UI, situational focus, no AI slop, no em dash in UI strings. Apply on any UI copy, layout, error, or help change. | Skills | |
OpenCTI-Platform/opencti Use when: scaffolding a new backend entity type, domain module, GraphQL schema, resolvers, or STIX converter in opencti-graphql | Skills | |
flightctl/ai-workflows Draft and submit a well-specified Jira bug report after explicit confirmation. Use when a user wants to report, file, log, or open a bug rather than fix it now. | Skills | |
microsoft/apm Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running in its own agent thread, and a spec-editor synthesizer that produces a fold-now / defer-v0.1.1 / defer-v0.2 / reject list plus a ship decision keyed off a 1..10 shocked_meter scale. The orchestrator is the sole writer to the PR: ONE consolidated comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes folds, and renders a ship recommendation that the maintainer weighs. | Skills |
Can't find what you're looking for? Evaluate a missing skill.