70 Plugins aus öffentlichen Claude Code marketplaces. Jedes bündelt Skills, Slash-Commands, Agents, Hooks oder MCP servers, die zusammen installiert werden.
Zeige 70 Plugins, die diesen Filtern entsprechen.
realsee-developer-skillsrealsee-developer/skills1
bretfisherBretFisher/skills1
relewiseRelewise/relewise-agent-plugins1
pretext-marketplaceyaniv-golan/pretext-skill1Reiche das repo mit .claude-plugin/marketplace.json ein und wir listen jedes plugin auf.
Marketplace einreichenRealsee skills for Claude Code: Argus panorama reconstruction and local editable Blender space modeling.
developmentSmall developer utilities for agents, such as screencapture-mac, which lets the agent screenshot native macOS apps to see what you see.
utilitiesBuild and troubleshoot Relewise integrations with current API and SDK guidance.
developmentHelp developers use @chenglou/pretext for line breaks and heights without DOM reflows
Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration.
Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend.
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences.
AI-powered project handover for Claude Code and Codex: export a short onboarding doc plus privacy-filtered AI memories into handover.zip; the next developer dry-runs import and writes only memories verified against current code.
Read-only project diagnostics and developer workflows
Help developers using coding agents retain solution knowledge by quizzing them on the code they maintain.
developer toolsBlockchain skills for technical blockchain developers and founders: Quicknode infrastructure, smart contracts, decentralized applications, blockchain development, and more
Helps developers author and debug Clix personalization templates (Liquid-style) for message content, deep links/URLs, and audience targeting. Use when the user mentions personalization variables, Liquid, templates, conditional logic, loops, filters, deep links, message logs, or when the user types "clix-personalization".
Azure SDK patterns and best practices for Python developers covering AI, storage, identity, monitoring, messaging, and management libraries.
Azure SDK patterns and best practices for .NET developers covering AI, resource management, identity, messaging, and Key Vault libraries.
Azure SDK patterns and best practices for TypeScript/Node.js developers covering AI, storage, identity, monitoring, and messaging libraries.
Azure SDK patterns and best practices for Java developers covering AI, communication, storage, identity, monitoring, and management libraries.
Azure SDK patterns and best practices for Rust developers covering identity, Key Vault, storage, Cosmos DB, and Event Hubs.
Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from the project pom.xml, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects.
Pull structured Apple App Store and Google Play data — app metadata, price, rating, the 1–5★ ratings histogram, version, developer, and reviews — and watch it for changes over time. Use when the user asks to look up an iOS or Android app by App ID, bundle ID, package name or app name, compare a set of competitor apps across both stores, monitor a competitor's price or rating for changes, track when an app ships a new version, scrape App Store or Google Play reviews, resolve a bundle ID to a full app record, check an app's rating across multiple country storefronts, build an ASO or app-market dataset, or set up a recurring app-store watch on an app's price, rating and version. One routed Actor, praise-most-high/app-store-intelligence, is built by this skill's author; every other row is unaffiliated (see Disclosure).
