01 / INSTRUCTIONS
Skills
Instructions, scripts, and references that teach an agent how to complete a task.
Independent guideAP / 1.0
DiscoverAgent Plugins.
Agent Plugin = Skills + MCP
Understand the portable package standard, then compare public Plugin and Skill repositories by GitHub activity.
Open standard Source links Clear labels
Portable package
plugin anatomy
plugin.jsonrequired manifest
skills/optional
└─SKILL.md
mcp.jsonoptional
FORMAT
1.0.0
COMPONENTS
2 types
PORTABLE
Yes
The standard defines the package. Clients still control installation, permissions, and runtime behavior.
The simple model
Skills + tools,
packaged to travel.
Agent Plugins give reusable agent capabilities a predictable home. The package can contain instructions, tool connections, or both.
Read the official specification02 / TOOLS
MCP
Server definitions that connect an agent to data, APIs, and external systems.
03 / PACKAGE
Plugin
The portable directory that gives Skills and MCP configuration a shared, predictable structure.
Start from the source
Verified context, not hype.
The 1.0 ecosystem is new. We separate official references, conformant packages, and client-specific formats instead of inflating the catalog.
Official reference
agentplugins / agent-plugins-example
Agent Plugins 1.0 example
The canonical example demonstrates a valid manifest and a migration Skill. It is a reference package—not an official marketplace pick.
plugin.json1 SkillNo MCP configReference
Open repositoryFormat-aware
Agent Plugins 1.0 is kept separate from client-only formats.
Source-first
Every ranked repository points back to a source you can inspect.
Claims stay precise
Stars are attention—not installs, compatibility, or security.
Repository rankings
See what has momentum.
Compare Plugin and Skill repositories by GitHub stars and transparent seven-day growth snapshots.
View rankingsPlugin · TopPlugin · 7dSkills · TopSkills · 7d
RankRepositoryStars
Daily snapshots start with the dataset.
No estimated growth and no made-up install counts. Rankings appear when verified source data is ready.
Data source: GitHubMethod: repository stars + daily snapshots
Learn the standard
Start with the right mental model.
Agent Plugins guide
A practical guide to Agent Plugins.
Learn how portable agent capabilities are structured, what to check before installation, and where Skills and MCP fit into the package.
Agent Plugin = Skills + MCP
Instructions explain the work. Tool connections make the work possible. The package gives both a portable structure.
What are Agent Plugins?
Agent Plugins are portable packages for reusable agent capabilities. Instead of scattering prompts, setup notes, scripts, and tool configuration across several repositories, a plugin gives them a predictable home. A manifest identifies the package, while optional components describe what an agent should know and which external systems it may use. This structure helps people inspect a capability before deciding whether it belongs in their workflow.
An Agent Plugin is not a model and it is not an autonomous agent. It is a package that a compatible client can read. The client still decides how installation works, which permissions are allowed, and how tools run. That separation is important: the package describes a capability, while the client controls its execution and security boundaries.
How Agent Plugins combine Skills and MCP
Skills provide the instructional layer. A Skill can include task guidance, repeatable procedures, scripts, examples, and reference material. It teaches an agent how to approach a specific job with more consistency. MCP provides the connection layer. An MCP server can expose data, APIs, files, databases, or actions that the agent needs in order to complete that job.
Agent Plugins bring those layers together without making every package identical. One Agent Plugin may contain only a focused Skill, another may configure an MCP connection, and a larger package may include both. The manifest provides the shared entry point, so clients and users can understand the package contents before enabling them.
Why teams use Agent Plugins
Teams use Agent Plugins to make useful agent behavior easier to share, review, and maintain. A portable package can reduce repeated setup work, keep operational knowledge close to the scripts that support it, and make changes visible through source control. It also creates a clearer review boundary than copying instructions from an unknown page directly into an agent session.
Portability does not guarantee universal compatibility. Different clients may support different installation flows, runtime options, or permission models. Treat every Agent Plugin as source material that must be evaluated for your chosen client and environment. Repository activity can help with discovery, but stars are not a substitute for code review, documentation, or security checks.
Common use cases
Agent Plugins can support focused workflows without locking useful knowledge inside one conversation or one client.
01
Research
Package repeatable discovery, analysis, and source-checking workflows.
02
Development
Combine coding instructions with tools for repositories and services.
03
Operations
Share documented procedures for support, reporting, and routine tasks.
How to evaluate Agent Plugins
Start with the source repository and inspect the package before you install it. Useful Agent Plugins explain their purpose, list their components, document external access, and keep instructions narrow enough to review. For any Agent Plugin that connects to outside systems, check credentials, requested permissions, network access, and the actions its tools can perform.
- A readable manifest with clear package metadata
- Focused Skills with useful instructions and references
- Documented MCP connections and permission requirements
- A source repository you can inspect before installation
Use the learning guides to understand the package model, then use the rankings to find public repositories worth inspecting. This gives Agent Plugins a useful discovery path without confusing popularity with safety, quality, or client support.
Frequently asked questions
Agent Plugin FAQ
01What is an Agent Plugin?
An Agent Plugin is a portable package that describes a reusable agent capability. It can include a manifest, task instructions, supporting files, scripts, and connections to external tools.
02Are Agent Plugins the same as Skills?
No. A Skill is the instructional part that teaches an agent how to perform work. A plugin is the wider package that can contain Skills, MCP configuration, or both.
03Does every plugin require MCP?
No. MCP is optional. An Agent Plugin can contain only a Skill when the task needs instructions but no external tool connection. Other packages use MCP to reach APIs, data, or services.
04How should I review Agent Plugins before installing?
Inspect the source, manifest, instructions, scripts, permissions, credentials, and network access. Confirm that your client supports the package, and never treat repository popularity as proof of safety.