3.9K skills · sorted by relevance
This skill should be used when creating, modifying, or managing Claude Code plugins and plugin marketplaces. Trigger when working with plugin manifests (plugin.json, marketplace.json), creating plugin directory structures, adding plugin components (commands, skills, agents, hooks), version bumping, or when discussing plugin development workflows.
The English summary is being prepared. Showing the original description.
Plan and run pre-release checks for OpenClaw plugins, covering installation, removal, configuration repair, startup, external plugin compatibility, and packaged releases. Record test evidence, failures, and skipped checks to show what has been verified.
Review Homecore plugins by distinguishing built-in native code from external Wasm packages. Check signatures, publisher identity, paths, resource limits, and host permissions, then use the documented verification command to assess the plugin’s trust boundaries.
Connect Claude Code plugins to external services through MCP, a protocol that makes service functions available as tools. Covers connection types, configuration files, authentication, tool permissions, and testing for local servers and hosted services.
Explains how PluginEval combines structural checks and experimental model assessments into quality scores. Helps interpret low scores, identify improvement areas, set marketplace thresholds, and explain what evaluation badges actually represent.
Create a local Codewhale plugin bundle with a versioned manifest and Skills named with the plugin prefix. Validate its structure and present review results so a person can decide whether to trust and enable it.
Diagnose OpenViking memory problems by checking plugin installation, client settings, server connections, and recent activity. The skill helps trace missing recalled context, failed saves, and authentication errors, then guides targeted fixes and checks whether they worked.
Diagnose missing recall, failed captures, and connection errors in the OpenViking memory plugin for Codex. Check installation, configuration, authentication, and server readiness, then use the findings to guide fixes and verify that memory works again.
Build and manage local Paseo plugins that add screens, workspace panels, commands, themes, or searchable attachments. It also covers hooks, code triggered by lifecycle events, and backend handlers for custom integrations and agent configuration changes.
Evaluate local Codex skills and plugins, understand their scores, and identify fixes to prioritize. Get explanations of token estimates, set up benchmark scenarios, and prepare workflows for measuring actual token usage.
Turn feedback about the TRES Claude plugin into a clear submission. The skill gathers relevant details, organizes bugs, ideas, or praise, and previews the report and conversation excerpt for approval before sending.
Configure the social-science-research plugin through guided questions about your field, institution, journals, and datasets. Save research preferences, researcher details, and R figure colors in project files for use in your research context.
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a plugin to the public catalog. End-to-end publishing covers TypeScript GitHub-source plugins, not Rust native-package releases or in-process TempsPlugin backend crates.
The English summary is being prepared. Showing the original description.
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml; Configure Maven quality plugins in pom.xml; Add Maven build lifecycle plugins for Java verification; Review Maven plugin versions and executions. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Audit, score, and compare repositories containing portable Agent Plugins against the official Agent Plugins specification. Use when asked to review a plugin repo, check plugin.json or mcp.json conformance, assess bundled skills and MCP servers, produce an evidence-cited 0–100 plugin scorecard, identify release blockers, or compare two agent plugins side by side.
The English summary is being prepared. Showing the original description.
Use when developing, reviewing, packaging, debugging, or answering questions about DeepSeek Harness (DSH) plugins — the plugin-based agent harness on vendored Cordis. Applies the official plugin-development constraints (plugin contract, cordis.yml layers, services/events/effects, tool DSL, bundles/profiles) backed by the dsh-plugin-guide knowledge base.
The English summary is being prepared. Showing the original description.
Guides implementation of custom Wwise or FMOD DSP plugins from scratch — effect, source, and mixer plugin types. Use when the user wants to create a new Wwise plugin, build an FMOD DSP effect, or implement a custom game audio middleware plugin. Trigger on phrases like "create a Wwise effect plugin", "build an FMOD DSP", "implement custom game audio middleware plugin", "how do I write a Wwise source plugin", or "set up an FMOD DSP description".
The English summary is being prepared. Showing the original description.
Apply when creating, modifying, or reviewing any Rembric agent plugin. Triggers on changes under `apps/plugin/`, on new clients added alongside Claude Code / Codex CLI / Hermes Agent / opencode / Pi, on edits to `apps/plugin/mcp-bridge/`, `apps/plugin/bin/rembric-plugin-core.mjs`, per-client manifest changes, or plugin install/uninstall scripts. End-to-end validation against a local dev server (`pnpm run dev`, host Next.js on :3000) is mandatory whenever local testing is feasible.
The English summary is being prepared. Showing the original description.
Find Laravel packages for specific features through LaraPlugins.io MCP, a connection to its package search tools. Check maintenance indicators, release history, and Laravel/PHP compatibility to compare candidates before adding a package to a project.
Connect external services to Claude Code plugins through MCP, a protocol that exposes service functions as tools. Get guidance on server configuration, connection methods, authentication, tool permissions, and testing connections and tool calls.
Manage Omni Skills, plugins, and persistent memory from the command line. Find and install skills, run them with supplied input, inspect execution history, and maintain saved information alongside plugin installations.
Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.
Set up, configure, update, and troubleshoot persistent memory for OpenClaw agents. The plugin stores conversations locally and supports automatic recall, task summaries, reusable skills derived from successful tasks, and a visual memory manager.
Build or modify Expo native modules and views using Swift, Kotlin, and TypeScript. Guides scaffolding, native function bindings, events, lifecycle hooks, and configuration so Expo apps can use platform features or existing native SDKs.