Browse Skills — Page 224

pr-review-expert

alirezarezvani/claude-skills

Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.

pr-review-fix

TencentCloudBase/CloudBase-AI-Toolkit

Periodically analyze open pull requests for CI failures, code review feedback, and quality issues, then fix them in batch. Use this skill when the user asks to check PR status, triage CI failures, fix review comments, analyze open PRs, or run a scheduled PR health check across the repository.

pr-review-guide

cloudflare/workerd

Guidelines for posting pull request review comments via GitHub CLI, including suggested edits format, handling unresolved comments, etiquette, and report/issue tracking. Load this skill when reviewing a PR via GitHub and posting inline comments.

pr-screenshots

github/awesome-copilot

Embed before/after screenshots and annotated images in pull request descriptions. Covers PR description patterns, image upload for Azure DevOps and GitHub, and sizing best practices.

pr-skill-triage

aaronjmars/aeon

Structured triage for inbound PRs that introduce or modify SKILL.md files — security scan per skill, required-secrets enumeration, cron slot-conflict check, basic quality signals, posted as one PR comment. The receipt that turns a 10-minute manual skill-PR review into a 10-second human decision

pr-specialist

manojbajaj95/claude-gtm-plugin

Expert PR and media relations guidance for earned media, press coverage, and reputation building. Use when writing press releases, crafting media pitches, developing journalist relationships, planning embargo strategies, managing crisis communication, placing thought leadership, building analyst relations, submitting award applications, or measuring PR coverage. Use for media outreach, press kits, speaking opportunities, and earned media strategy.

pr-status-triage

vercel/next.js

>

pr-style

fredrikaverpil/dotfiles

>-

pr-test

Significant-Gravitas/AutoGPT

E2E manual testing of PRs/branches using docker compose, agent-browser, and API calls. TRIGGER when user asks to manually test a PR, test a feature end-to-end, or run integration tests against a running system.

pr-testing

microsoft/aspire

Use when asked to test a microsoft/aspire pull request, including CLI, hosting, dashboard, component, template, and VS Code extension changes. Also covers testing PRs that change CI infrastructure — GitHub Actions (workflows, actions, gh-aw agentic workflows, CI scripts under .github/ and eng/) and Azure DevOps pipelines (eng/pipelines, eng/common).

pr-threads-address

posit-dev/skills

Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.

pr-threads-resolve

posit-dev/skills

Bulk resolve unresolved PR review threads on the current branch’s PR — typically after threads have been addressed manually or via /pr-threads-address

pr-to-go-linter

github/gh-aw

Generate a new pkg/linters analyzer from a merged or open PR pattern.

pr-to-main

breaking-brake/cc-wf-studio

Create a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.

pr-to-main-cleanup

breaking-brake/cc-wf-studio

Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.

pr-validate

boshu2/agentops

Validate PR scope and quality.

pr-watch

SethGammon/Citadel

>-

pr-workflow

Chorus-AIDLC/Chorus

Complete workflow for submitting code changes — create branch, commit, open PR, check CI, fix failures, and merge.

pr-writer

tranhieutt/software_development_department

Creates and formats pull request titles, descriptions, and linked issue references following conventional commit standards. Use when creating or updating a pull request or when the user mentions PR description, pull request, or opening a PR.

pr-writer-v2

diegosouzapw/awesome-omni-skills

PR Writer workflow skill. Use this skill when the user needs Create pull requests following Sentry's engineering practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

pr-writing-review

evalstate/fast-agent

Extract and analyze writing improvements from GitHub PR review comments. Use when asked to show review feedback, style changes, or editorial improvements from a GitHub pull request URL. Handles both explicit suggestions and plain text feedback. Produces structured output comparing original phrasing with reviewer suggestions to help refine future writing.

practice-plan-creator

OneWave-AI/claude-skills

Design sport-specific practice sessions. Drills by skill level and time, warm-up, skill work, scrimmage, cool-down.

practitioner-hat

yogsoth-ai/de-anthropocentric-research-engine

Engineer perspective — assess buildability, cost, timeline, and integration challenges.

pragmatic-guard

codenamev/ai-software-architect

Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.

pragmatic-programmer

wondelai/skills

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "avoid technical debt", "code ownership", or "how do I become a better developer". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

pragmatic-writing

robertguss/claude-code-toolkit

This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies when creating technical essays, documentation, tutorials, or explanatory content that needs to be clear, engaging, and actionable.

pragmatics-communication

Tibsfox/gsd-skill-creator

Pragmatics and communicative competence across languages -- speech acts (Austin/Searle), Grice's conversational maxims and implicature, politeness theory (Brown & Levinson), face-threatening acts, discourse structure, turn-taking, repair strategies, register and formality, cross-cultural communication, communicative strategies (circumlocution, approximation, appeal for assistance), and the gap between grammatical competence and communicative performance. Use when teaching communication skills, analyzing cross-cultural misunderstandings, building conversational fluency, or understanding why grammatically correct sentences can be pragmatically inappropriate.

prcheckloop

microsoft/amplifier-app-paperclip

>

prcheckloop

paperclipai/paperclip

>

prd

SethGammon/Citadel

>-

prd

github/awesome-copilot

'Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.'

PRD Template v2

skillmatic-ai/playbooks

"Write a comprehensive Product Requirements Document following the standard template"

prd-breakdown

KerberosClaw/kc_ai_skills

Use when user wants to break a PRD into Azure DevOps work items via vertical-slice plan. Workflow: read PRD → quiz user to lock durable decisions → draft slices with HITL/AFK + blocked_by → call az CLI directly via Bash to create items + Predecessor relations. Idempotent re-runs via fingerprint markers embedded in description. Pure prompt-driven — Claude is the runtime, no Python helper, no install ceremony. Trigger phrases: prd-breakdown / 拆 PRD / 切 vertical slice / 推 slice 到 ADO.

prd-create

KerberosClaw/kc_ai_skills

Use when user wants to draft a PRD (Product Requirements Document) from raw input (meeting transcripts, hand-waved descriptions, scattered decisions). Workflow: load org's PRD Guideline + writing discipline → lock execution mode (human-run vs unattended-agent-run) → ingest raw input → quiz user numbered-list iterate to fill §1-§15 → draft v0.1 → handle stakeholder merge (review feedback, surface conflicts) → lock v1.0 + sanitize per ADO publication contract → publish to ADO Wiki. For an agent-run PRD, §13 carries the unattended-execution discipline (machine-checkable AC + traffic-light + 3-exits + stop-and-ask), aligned with goal-engineer's loop-run-protocol. NOT for packaging an ALREADY-FROZEN build spec (approved ADR / locked design / machine-checkable AC) into an unattended dispatch — that is goal-engineer's lean build dispatch. Pure prompt-driven — Claude is the runtime, no Python helper. Trigger phrases: 寫 PRD / PRD 撰寫 / prd-create / 初版 PRD / 起 PRD.

prd-creator

closedloop-ai/claude-plugins

This skill helps PMs draft lightweight PRDs. It should be used when a PM wants to define a new feature, brainstorm requirements, or prep for sprint planning. Triggers include "I have a feature idea", "help me write a PRD", "let's break this into stories", or "what do I need for sprint planning". Optimized for speed — generates minimal viable documentation through conversation, not heavy templates.

prd-development

deanpeters/Product-Manager-Skills

Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.

prd-reviewer

TestAny-io/testany-agent-skills

PRD review, 需求评审, 检查 PRD 质量。Use when: PRD 完成后需要评审、"审查 PRD"、"PRD 评审"、"需求评审"。

prd-studio

TestAny-io/testany-agent-skills

PRD automation, PRD 全流程。Use when: "帮我写个 PRD 并审查通过"、"自动完成 PRD"、"PRD 全流程"。

prd-template

mohitagw15856/pm-claude-skills

Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.

prd-to-issues

softspark/ai-toolkit

Splits a PRD into vertical-slice GitHub issues with HITL/AFK tagging and dependencies. Triggers: PRD to issues, create tickets, break down PRD, work items.

prd-to-plan

softspark/ai-toolkit

Converts PRD into phased plan via tracer-bullet vertical slices. Triggers: PRD to plan, break down PRD, implementation plan, tracer bullets, phased plan.

prd-v01-problem-framing

mattgierhart/PRD-driven-context-engineering

>

prd-v01-user-value-articulation

mattgierhart/PRD-driven-context-engineering

>

prd-v02-competitive-landscape-mapping

mattgierhart/PRD-driven-context-engineering

>

prd-v02-product-type-classification

mattgierhart/PRD-driven-context-engineering

Classify product approach into one of six types (Clone, Unbundle, Undercut, Slice, Wrapper, Innovation) based on competitive landscape. Triggers on PRD v0.2 work after competitive analysis, or when user asks "what type of product should we build?", "should we clone or innovate?", "is this a fast-follow opportunity?", "how should we position against competitors?", "clone vs undercut", "unbundle vs slice", or requests help choosing product strategy. Outputs BR- entries for product type classification and inherited GTM constraints.

prd-v03-features-value-planning

mattgierhart/PRD-driven-context-engineering

Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.

prd-v03-moat-definition

mattgierhart/PRD-driven-context-engineering

Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.

prd-v03-outcome-definition

mattgierhart/PRD-driven-context-engineering

Define measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages.

prd-v03-pricing-model

mattgierhart/PRD-driven-context-engineering

Select and validate pricing model for PRD v0.3 Commercial Model. Triggers on requests to set pricing, choose monetization model, design pricing tiers, validate willingness to pay, or when user asks "how much should we charge?", "what pricing model?", "freemium vs paid?", "how to structure tiers?", "price point?". Consumes Competitive Landscape (CFD-) and Product Type (BR-) from v0.2. Outputs BR- entries for pricing rules, tier boundaries, and competitive positioning.

prd-v04-persona-definition

mattgierhart/PRD-driven-context-engineering

Synthesize behavioral personas from prior stage evidence for journey mapping and marketing during PRD v0.4 User Journeys. Triggers on requests to define personas, create user profiles, identify target users, or when user asks "who are our users?", "define personas", "user profiles", "target users", "persona creation", "who uses this product?". Consumes CFD- (v0.1-v0.3), BR- (targeting from v0.3 Moat), FEA- (v0.3 Feature Value Planning). Outputs PER- entries with behavioral profiles and feature relationships. Feeds v0.4 User Journey Mapping.

prd-v04-screen-flow-definition

mattgierhart/PRD-driven-context-engineering

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review.

prd-v04-user-journey-mapping

mattgierhart/PRD-driven-context-engineering

Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.

prd-v04-visual-prototype-gate

mattgierhart/PRD-driven-context-engineering

>

prd-v05-risk-discovery-interview

mattgierhart/PRD-driven-context-engineering

Surface risks through guided questioning, helping users consider pivots, constraints, and prioritization during PRD v0.5 Red Team Review. Triggers on requests to identify risks, stress-test the idea, perform red team review, or when user asks "what could go wrong?", "identify risks", "red team", "risk assessment", "challenge assumptions", "stress test the idea". Consumes all prior IDs (CFD-, BR-, FEA-, PER-, UJ-, SCR-) as interview context. Outputs RISK- entries with owner decisions and mitigations. Feeds v0.5 Technical Stack Selection.

prd-v05-technical-stack-selection

mattgierhart/PRD-driven-context-engineering

Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what technologies?", "select tech stack", "build or buy?", "what do we reuse?", "existing stack", "technical decisions", "what tools do we need?", "evaluate solutions". Consumes FEA- (features), SCR- (screens), RISK- (constraints). Outputs TECH- entries with decisions, rationale, and trade-offs. Feeds v0.6 Architecture Design.

prd-v06-architecture-design

mattgierhart/PRD-driven-context-engineering

Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?", "architecture decisions", "technical architecture", "system overview". Consumes TECH- (stack selections), RISK- (constraints), FEA- (features). Outputs ARC- entries documenting architecture decisions with rationale. Feeds v0.6 Technical Specification.

prd-v06-environment-setup

mattgierhart/PRD-driven-context-engineering

Document development environment requirements for team consistency and AI agent understanding during PRD v0.6 Architecture. Triggers on requests to define environment setup, document tooling, create dev setup guide, or when user asks "what tools do I need?", "environment setup", "dev environment", "CLI requirements", "project setup", "onboarding setup". Consumes TECH- (stack selections), ARC- (architecture decisions). Outputs ENV- entries for development, CI/CD, and infrastructure environments. Feeds v0.7 Build Execution.

prd-v06-technical-specification

mattgierhart/PRD-driven-context-engineering

Define implementation contracts (APIs and data models) that developers will build against during PRD v0.6 Architecture. Triggers on requests to define APIs, design database schema, create data models, or when user asks "define APIs", "data model", "database schema", "API contracts", "technical spec", "endpoint design", "schema design". Consumes ARC- (architecture), TECH- (Build items), UJ- (flows), SCR- (screens). Outputs API- entries for endpoints and DBT- entries for data models. Feeds v0.7 Build Execution.

prd-v07-epic-scoping

mattgierhart/PRD-driven-context-engineering

Transform v0.6 specifications into context-window-sized work packages (EPICs) during PRD v0.7 Build Execution. Triggers on requests to create epics, scope work, break down implementation, or when user asks "create epics", "scope work", "break down work", "context window sizing", "what to build first?", "implementation planning", "epic breakdown". Consumes API-, DBT-, FEA-, ARC-. Outputs EPIC- entries with objectives, ID references, dependencies, and context windows. Feeds v0.7 Test Planning.

prd-v07-implementation-loop

mattgierhart/PRD-driven-context-engineering

Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.

prd-v07-test-planning

mattgierhart/PRD-driven-context-engineering

Define test cases BEFORE implementation, ensuring every API, business rule, and user journey has verifiable acceptance criteria during PRD v0.7 Build Execution. Triggers on requests to define tests, plan test coverage, create test cases, or when user asks "define tests", "test planning", "what to test?", "test cases", "test coverage", "TEST-", "test-first". Consumes EPIC- (scope), API-, DBT-, BR-, UJ-. Outputs TEST- entries with Given-When-Then format. Feeds v0.7 Implementation Loop.

prd-v08-changelog-as-marketing

mattgierhart/PRD-driven-context-engineering

>

prd-v08-drift-baseline-compare

mattgierhart/PRD-driven-context-engineering

>

prd-v08-marketing-ops-handoff

mattgierhart/PRD-driven-context-engineering

>

prd-v08-monitoring-setup

mattgierhart/PRD-driven-context-engineering

>

prd-v08-release-planning

mattgierhart/PRD-driven-context-engineering

>

prd-v08-runbook-creation

mattgierhart/PRD-driven-context-engineering

>

prd-v09-aeo-audit

mattgierhart/PRD-driven-context-engineering

>

prd-v09-alternatives-pages

mattgierhart/PRD-driven-context-engineering

>

prd-v09-cold-outreach-tiered

mattgierhart/PRD-driven-context-engineering

>

prd-v09-feedback-loop-setup

mattgierhart/PRD-driven-context-engineering

>

prd-v09-gtm-strategy

mattgierhart/PRD-driven-context-engineering

>

prd-v09-hn-reddit-launch

mattgierhart/PRD-driven-context-engineering

>

prd-v09-launch-channels-orb

mattgierhart/PRD-driven-context-engineering

>

prd-v09-launch-metrics

mattgierhart/PRD-driven-context-engineering

>

prd-v09-offer-construction-hormozi

mattgierhart/PRD-driven-context-engineering

>

prd-v09-positioning-dunford

mattgierhart/PRD-driven-context-engineering

>

prd-v10-case-study-builder

mattgierhart/PRD-driven-context-engineering

>

prd-v10-chasm-adoption-moore

mattgierhart/PRD-driven-context-engineering

>

prd-v10-continuous-discovery-torres

mattgierhart/PRD-driven-context-engineering

>

prd-v10-mom-test-interview

mattgierhart/PRD-driven-context-engineering

>

prd-v10-testimonial-collector

mattgierhart/PRD-driven-context-engineering

>

prd-vXX-skill-name

mattgierhart/PRD-driven-context-engineering

>

prd-writer

TestAny-io/testany-agent-skills

Write PRD, 写产品需求文档。Use when: 需要写新功能 PRD（有UI/无UI）、第三方集成、功能重构、性能/安全优化需求。

prd-writing

AsyrafHussin/agent-skills

Step-by-step workflow for writing Product Requirements Documents. Use when creating PRDs, documenting features, writing specifications, or planning new products. Triggers on "write PRD", "create PRD", "document requirements", "feature spec", or "product requirements".

pre-generation-check

bitwize-music-studio/claude-ai-music-skills

Validates all pre-generation gates before sending tracks to Suno. Checks sources verified, lyrics reviewed, pronunciation resolved, explicit flag set, style prompt complete, and artist names cleared. Use before generating tracks on Suno or when the user says "pre-gen check" or "ready to generate".

pre-meeting

anthropics/claude-for-financial-advisors

Prepare a complete client review meeting prep document for a financial advisor, for whatever timeframe the review covers (quarterly, annual, ad hoc). Given a household name or email and a timeframe, pulls CRM context (Salesforce/Redtail/Wealthbox), portfolio data (Orion/Addepar/Envestnet-Tamarac), estate & tax status (Wealth.com), meeting notes (Zocks or CRM), recent correspondence (Gmail/Outlook), and the household's plan snapshot (MoneyGuide), then assembles a meeting-ready prep doc with agenda, talking points, and action items. Triggers on "pre meeting", "/pre-meeting", "prep for [client]", "quarterly review prep", "get me ready for my meeting with [client]", or "client meeting tomorrow".

pre-merge

bobmatnyc/claude-mpm-skills

Comprehensive verification workflow before merging changes to production.

pre-mortem

phuryn/pm-skills

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

pre-plan-workflow

jpicklyk/task-orchestrator

Internal workflow for plan mode — checks MCP for existing work, note schemas, and gate requirements to set the definition floor before planning begins. Triggered automatically when entering plan mode for any non-trivial implementation task.

pre-publish-review

code-yeongyu/oh-my-openagent

Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user explicitly asks for a pre-publish review — a plain publish/release request MUST NOT trigger this; /publish ships directly. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.

pre-push-review

microsoft/amplifier-app-actions

>

pre-push-security-scan

aAAaqwq/AGI-Super-Team

【铁律】Git push 前必须执行的安全扫描。防止 API keys、tokens、passwords、私钥等敏感信息被推送到远程仓库。适用于所有 git push、gh pr create、代码同步等场景。

pre-ship-review

terrylica/cc-skills

Run a structured quality review before shipping code at any checkpoint such as PRs, releases, or milestones. Use whenever the user says.

pre-submit-pr

huggingface/OpenEnv

Validate changes before submitting a pull request. Run comprehensive checks including lint, tests, alignment review, and RFC analysis. Use before creating a PR, when asked if code is ready for review, or before pushing for PR.

preact

TerminalSkills/skills

>-

precision_oncology

InternScience/scp

Precision Oncology Workflow - Precision oncology: tumor expression profiling, variant analysis, targeted therapy lookup, and clinical trials. Use this skill for precision oncology tasks involving get gene expression across cancers get vep hgvs get associated drugs by target name get clinical studies info by drug name pubmed search. Combines 5 tools from 5 SCP server(s).

precision-oncology-agent

swaruplab/operon

Fuse genomic variants, pathology findings, and clinical context to draft evidence-linked therapy options for tumor board review.

preclinical-pkpd-analyst

aipoch/medical-research-skills

Use preclinical pkpd analyst for data analysis workflows that need structured execution, explicit assumptions, and clear output boundaries.

precoro-automation

ComposioHQ/awesome-claude-skills

"Automate Precoro tasks via Rube MCP (Composio). Always search tools first for current schemas."