发现 Skills
为真实工作流程挑选经过整理的 Skill,连接、安装并开始使用。
bio-filter-sequences
Filter and select sequences by criteria (length, ID, GC content, patterns) using Biopython. Use when subsetting sequences, removing unwanted records, or selecting by specific criteria.
bio-pathway-gsea
Gene Set Enrichment Analysis using clusterProfiler gseGO and gseKEGG. Use when analyzing ranked gene lists to find coordinated expression changes in gene sets without arbitrary significance cutoffs. Detects subtle but coordinated expression changes.
bio-crispr-screens-jacks-analysis
JACKS (Joint Analysis of CRISPR/Cas9 Knockout Screens) for modeling sgRNA efficacy and gene essentiality. Use when analyzing multiple CRISPR screens simultaneously or when accounting for variable sgRNA efficiency across experiments.
bio-workflows-smrna-pipeline
End-to-end small RNA-seq analysis from FASTQ to differential miRNA expression. Use when analyzing miRNA, piRNA, or other small RNA sequencing data.
bio-clinical-databases-somatic-signatures
Extract and analyze mutational signatures from somatic variants using SigProfiler or MutationalPatterns to characterize mutagenic processes. Use when identifying DNA damage mechanisms or etiology in cancer genomes.
bio-spatial-transcriptomics-spatial-statistics
Compute spatial statistics for spatial transcriptomics data using Squidpy. Calculate Moran's I, Geary's C, spatial autocorrelation, co-occurrence analysis, and neighborhood enrichment. Use when computing spatial autocorrelation or co-occurrence statistics.
bio-phylo-tree-manipulation
Modify phylogenetic tree structure using Biopython Bio.Phylo. Use when rooting trees with outgroups or midpoint, pruning taxa, collapsing clades, ladderizing branches, or extracting subtrees.
claude-design-system-audit
Audits and optimizes the Design System of a Claude Design project (claude.ai/design). Verifies completeness (fonts, tokens, brand refs, a11y), identifies gaps, applies fixes when possible, and delivers a report. Intended to be invoked before any large-scale design generation campaign to ensure outputs inherit from a clean system. Relies on `design:design-system`, `design:design-critique`, `design:accessibility-review`, `marketing:brand-review`.
output-dev-types-file
Create types.ts files with Zod schemas for Output SDK workflows. Use when defining input/output schemas, creating type definitions, or fixing schema-related errors.
escalation
Use to define incident tiers, response protocols, and stakeholder communications.
firmographic-analysis
Use when interpreting company-level enrichment data to segment accounts, spot buying triggers, and tailor outreach.
messaging-frameworks
Use when building message houses, key statements, and proof structures for announcements or crises.
notebooklm
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
android-patterns
WHAT: Android-specific patterns for BackHandler, StatusBar, and material elevation. WHEN: handling hardware back button, configuring status bar color, implementing shadows. KEYWORDS: android, BackHandler, StatusBar, elevation, ToastAndroid, PlatformIs, Platform.select, shadow, cleanup.
ticket-refinement
Use this skill whenever the user wants to write, refine, or break down a subtask for a software ticket — especially backend endpoints, frontend components, or API integrations. Trigger when the user shares a user story, acceptance criteria, or ticket scope and asks for a subtask, refinement card, or implementation breakdown. Also trigger when the user says things like "help me refine this", "write a subtask for X", "break this down", or "create a card for the endpoint / component / feature". This skill produces structured, audience-appropriate subtask write-ups for developers, PMs, and QAs alike.
guimkt-design-system-extractor
Extrai design systems completos de websites para gerar arquivos .md que guiam agentes na criação de páginas com a identidade visual do site analisado. Captura cores, tipografia, componentes (botões, cards, navbar, footer), assets (logos, imagens de produto), layout/grid, animações, anti-patterns e gera CSS variables prontos para uso. Use quando o usuário pedir para "extrair design system", "criar design system de um site", "analisar identidade visual", "capturar estilo de um site", "design tokens de um site", "gerar guia visual de marca", ou qualquer variação de análise visual de website para replicação de identidade.
pricing-page
Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.
testing-best-practices
Define a test strategy, improve test quality, choose the right test type, and apply mocking correctly. Use when planning test coverage, reviewing test quality, deciding between unit/integration/E2E tests, or fixing flaky tests. Triggers: test strategy, coverage, flaky test, mock, stub, fixture, TDD, BDD, test pyramid, Vitest, Jest, pytest, JUnit, Playwright, Cypress.
database-suite
Unified Database Management Suite. Consolidates administration, architecture, design, migration, performance tuning, and SQL optimizations.
skill-i18n
Translate SKILL.md and README.md files into multiple languages for sharing skills internationally
updating-a-pipeline-step
Use when the user wants to modify, change, or update an existing step within a named pipeline, or invokes /superpipelines:update-step. Reads current step, applies changes, re-validates edges with neighbors, audits the delta, and gates on human approval before writing to disk.
review-prep
Interactive code review walkthrough using tmux and nvim for pair programming style review. Use when user says "review", "walk through changes", "explain this diff", "prep for PR", or wants to understand what changed.
multi-project
Manage a multi-repo workspace — register projects under aliases, then search, edit, diff, and commit across them as one unit. Use when a single task spans more than one repo (Jenkinsfile + library, frontend + backend, microservice + shared SDK), when you need to trace a symbol's references across repos for impact analysis, or when you need a coordinated commit with the same message across multiple checkouts. Workspace state persists in `.agent-memory/workspace.json` under the cwd.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code