30 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 30 plugins that match these filters.
90n-skillspolar-bear-org/claude-skills3
claude-code-skillsalirezarezvani/claude-skills2
pm-claude-skillsmohitagw15856/pm-claude-skills2
claude-code-workflowswshobson/agents1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceEnterprise / cross-functional Research Operations domain — the managed counterpart to the academic research/ domain. v2.9.0 ships 5 skills: orchestrator (context: fork), clinical-research (protocol synopsis, endpoint selection, sample-size/power for means/proportions/survival, phase-gate feasibility), research-finance (R&D budgeting with F&A split, burn/runway, capitalize-vs-expense routing, portfolio ROI), market-research (TAM/SAM/SOM top-down and bottoms-up, survey sampling with FPC, Kotler segmentation), and product-research (goal-matched study design, method-based saturation, insight synthesis flagging single-source anecdotes). Hard rules: outputs are estimates routed to a named clinical or finance owner, market sizes show method + assumptions, product insights require recurrence across independent participants. 24 stdlib Python tools, 12 reference docs. Distinct from ra-qm-team, finance, research/grants, product-team, and marketing-skill.
Open-source investment research terminal integration - comprehensive equity analysis, crypto tracking, macro indicators, portfolio optimization, and AI-powered financial insights using OpenBB Platform
Personal & professional documents for you: Resume/CV, Cover Letter, Personal Bio, LinkedIn Profile, Portfolio Page, and One-Pager. Pair with the playground's themed PDF export for beautifully typeset output.
Quantitative analysis, algorithmic trading strategies, financial modeling, portfolio risk management, and backtesting
Get products ready for the EU Cyber Resilience Act (Regulation 2024/2847). Four deterministic stdlib scripts: a scope classifier that sorts a portfolio into default, important class I/II and critical (Annex III/IV), blocks conformity routes Article 32 does not allow, checks support periods and names the CSIRT for Article 14 reports; an Article 14 clock for the 24h/72h/14-day/one-month deadlines live since 11 September 2026; an Annex I/II/VII gap check before the EU declaration of conformity; and an SBOM floor check for CycloneDX and SPDX. Ships cs-cra-officer agent, /cs-cra-readiness and /cs-cra-report commands, 3 cited references and an Article 14 runbook.
12 Claude Skills for running an innovation program that tests real bets, kills most of them cheaply, and earns its next round of funding: chartering the program, designing gates that ask questions instead of handing out scores, keeping the innovation ledger, mapping the portfolio, framing challenges, running ideation, planning the discovery interviews, designing and reading experiments, preparing each gate review, writing the case for continued investment, and closing initiatives with dignity.
productivityClaude for Product Designers: 32 Claude skills for one piece of design work, from the request to the result, in eight stages: frame the problem with a problem framing brief, a user journey map and a HEART metrics plan; explore and decide with design principles, an options trade-off table, a rationale doc and a decision log; design with context through a design system rules file, a product context file, the user flow, the copy deck and every UI state; prototype around one question; critique against a quality bar, ten heuristics and an accessibility review; test with real users; hand off with a spec and a UX debt register; then show the impact in a review deck, a pushback brief, an impact write-up and a portfolio case study. For product designers, UX and UI designers, and designers who do their own research. Claude drafts, checks and explains; you make the design decisions, real users test the work, and nothing is presented as tested, accessible or ready to ship that was not.
productivityClaude Guide for Product Interviews: 32 Claude skills for preparing product interviews from the job ad to the offer, in eight stages: read the role with a target role brief, a job ad breakdown and an interview loop map; tell your story with a career evidence inventory, a story bank and resume bullets; prepare the cases for product sense, metrics, prioritisation and execution, and app critique; prepare the conversations with behavioural answers, a portfolio or project walkthrough and a mock interview; show how you work with AI with an AI use plan, a fluency answer and a work sample; get in through people you already know; run each process with a take-home plan, round debriefs and a tracker; then decide with an offer comparison and negotiation prep. For product managers, product owners and product designers with years of shipped work. Claude helps you prepare and practise from work you really did; it never invents a role, a result or a number, and it stays out of the live interview.
productivityProfessional crypto portfolio tracking with real-time prices, PnL analysis, and risk metrics
Banking & lending skills: credit memos with covenant headroom, quarterly covenant compliance reviews, KYC/AML escalation write-ups, and portfolio risk briefs — credit and compliance judgment for analysts and RMs.
Expert database guidance for the AWS database portfolio. Design schemas, execute queries, handle migrations, and choose the right database for your workload.
All LLMQuant category skills bundled as one plugin: equities, ETFs, options, equity-derivatives, commodities, crypto, prediction-markets, macro, credit, rates/FX, events, portfolio, portfolio-lab, risk, strategies, market-intelligence, investor-lenses, and data.
Track crypto wallets across multiple chains with portfolio analytics and transaction history
Skills for platform and SDK developer experience — API design, auth and error patterns, integration marketplace strategy, SDK portfolio, app store listings, partner onboarding, and developer observability.
4 portfolio-strategy skills: long-short-construction, long-short-equity, portfolio-hedging, position-sizing.
Design and evolve enterprise architectures by connecting business capabilities, value streams, applications, information, technology, operating models, and transition choices. Use when mapping an enterprise portfolio, comparing current and target states, sequencing transition architectures, or defining federated architecture decision rights and stakeholder communication. Do not use for system or solution design, API or data-platform design, organizational or talent design, product roadmaps, technology adoption, or corporate strategy; route those to the named specialist skills.
Route a product through its full lifecycle — discovery, strategy, portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. Use when evaluating a new product idea, managing a product through its lifecycle, or connecting product phases that currently operate in isolation. Do not use for a single product task that is already owned by a specialist skill (load that skill directly); do not use for software delivery lifecycle work (route to neckbeard); do not use to duplicate product discovery, strategy, UX, experimentation, analytics, release, or delivery methods.
Define and run product governance — recurring decision rights, intake, portfolio cadences, evidence standards, and cross-functional operating contracts. Covers six review cadences (intake, portfolio, roadmap, experiment, launch, lifecycle) with named accountable owners, minimum evidence standards per decision type, and escalation paths. Supports lightweight and high-assurance operating modes with configurable governance patterns. Use when designing a product governance model, resolving contested decisions, establishing evidence standards, recording exceptions and escalations, or building cross-functional operating contracts. Do NOT use for executive governance (capital allocation, org structure — route to chief-of-staff-methodology or strategy-frameworks), for technical delivery gates (CI/CD, release approval — route to release-engineering or spec-driven-development), or to impose a universal org chart.
Build and maintain outcome-based product roadmaps and portfolio views that sequence strategic bets by evidence, not dates. Covers Now/Next/Later views, strategic-bet management, capacity allocation, dependency and confidence mapping, scenario planning, continue/pause/kill/revisit criteria, stakeholder narratives, and roadmap review cadences. Use when building or reviewing a product roadmap, managing a portfolio of bets, or communicating strategic sequencing to stakeholders. Do NOT use for tactical prioritization mechanics (RICE, MoSCoW, Kano, OST — route to product-methodology or product-strategy), for project scheduling or Gantt charts, or for delivery-flow management (route to kanban-guru).
Use this skill to shape product or engineering work before committing time to it: set appetites instead of estimates, narrow raw ideas into bounded problems, sketch solutions at the right level of abstraction, de-risk rabbit holes, write pitches, bet with capped downside (circuit breaker), and govern builds with discovered scopes and scope hammering. Adapted from Basecamp's Shape Up and extended for human+AI-agent teams. Use when a raw idea, feature request, or "redesign X" grab-bag needs to become a bounded project before anyone builds; when planning how much work an idea is worth; or when delegated agent builds need budgets, kill criteria, and non-convergence rules. Do not use for discovering whether a problem is real (use product-discovery), for portfolio-level sequencing across quarters (product-roadmapping-and-portfolio), for formal specification after the bet is placed (spec-driven-development), or for task-level prioritization frameworks like RICE (product-methodology).
