SkillAgentSearch skills...

persona-agent-marketplace

persona-agent official marketplace

Install / Use

claude mcp add Code-MonkeyZhang -- npx -y github:Code-MonkeyZhang/persona-agent-marketplace

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

68/100

Supported Platforms

Claude Code
Claude Desktop
OpenAI Codex

Tags

Our assessment of persona-agent-marketplace

persona-agent-marketplace scores 68/100 on our quality scale, 876th of 944 AI & Machine Learning skills we index.

Its MCP Server is 5.3 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
26/30
Structure
17/20
Description
8/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 11 days ago, so persona-agent-marketplace is actively maintained.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 75/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

persona-agent-marketplace compared with similar skills

All 4 of these similar skills score higher than persona-agent-marketplace; compare them before choosing.

SkillScoreStarsUpdatedFormat
persona-agent-marketplace (this skill)by Code-MonkeyZhang68311d agoMCP Server
claude-memby thedotmack100118.5ktodayCLAUDE.md
Agent-Reachby Panniantong100113.3k12d agoCLAUDE.md
Understand-Anythingby Egonex-AI10093.3k1d agoCLAUDE.md
hyperframesby heygen-com10087.1ktodayCLAUDE.md

Frequently asked questions

How do I install persona-agent-marketplace?
Run claude mcp add Code-MonkeyZhang -- npx -y github:Code-MonkeyZhang/persona-agent-marketplace. The install tabs above show the steps for each supported agent.
Which AI agents does persona-agent-marketplace work with?
It is written for Claude Code, Claude Desktop and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
Is persona-agent-marketplace safe to use?
It declares no license and scores 75/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is persona-agent-marketplace still maintained?
The repository was last updated 11 days ago, so persona-agent-marketplace is actively maintained.

persona-agent-marketplace

The official marketplace repository for persona-agent. The app reads the manifests and downloads Skills, MCP servers, Agent Apps, and Agent personas from here.

Directory Structure

persona-agent-marketplace/
├── skills/
│   ├── index.json          ← Skill manifest
│   └── <skill-folder>/     ← One folder per Skill
│       ├── SKILL.md
│       └── logo.svg        ← Card icon, referenced by the logo field
├── mcp/
│   ├── index.json          ← MCP & Agent App manifest
│   └── <name>/             ← One folder per product
│       ├── mcp.json        ← Launch config (agentApp: true marks an Agent App)
│       ├── icon.png        ← Card & app-bar icon
│       └── src/ + ui/ ...  ← Server source + built Web UI (Agent Apps)
├── agents/
│   ├── index.json          ← Agent persona manifest
│   └── <name>/             ← One folder per persona
│       ├── config.json
│       ├── systemPrompt.md
│       └── assets/
└── docs/
    └── agent-app/          ← Developer docs (not distributed to users)

Agent Apps live under mcp/ — there is no separate apps/ directory. An Agent App is an MCP product whose mcp.json carries agentApp: true; the marketplace buckets such products into the "Apps" tab.

Building an Agent App

An Agent App is an MCP Server + Web UI combo: the user interacts with a visual panel while the Agent sees only standard MCP tools. To build one, read the developer guide:

Publishing

Add your folder under the right category, register it in that category's index.json, and open a Pull Request. Each category has a dedicated guide covering the full requirements:

Skills

  • Folder name === frontmatter name === manifest id: all three carry the same lowercase kebab-case machine key. The app loads a Skill by its frontmatter name; the manifest id states the same key explicitly so identity never has to be derived from path.
  • Manifest name is the display name: the frontmatter name is a machine key while the manifest name is what users see on cards, so the two may differ in wording even though both are called name.
  • Manifest description === frontmatter description: keep them as the same text.
  • Every entry carries a logo image (SVG or PNG) in its folder, referenced by the logo field; the card falls back to a built-in icon when absent.

MCP Servers

  • Product lives under mcp/<name>/ and must contain a mcp.json launch config. ${SERVERS_DIR} in it is replaced with the actual install directory at install time.
  • Register an entry in mcp/index.json with id / name / description / author / homepage / path / logo / and runtime: "uv" when the server runs on uv (the installer then pre-installs dependencies via uv sync, so commit uv.lock for reproducibility).

Agent Apps

An Agent App inherits all MCP constraints, plus:

  • mcp.json must contain agentApp: true and a supportedUI array ("desktop" / "mobile").
  • Same-name rule: folder name === manifest id === the last segment of the index.json entry's path === the installed mcp.json key === the notification source. All five must match.
  • The built Web UI under ui/ must be committed — users have no Node and cannot rebuild. Strip web/ sources, node_modules/, data/, and logs before publishing, and make sure .gitignore does not exclude ui/.
  • icon.png serves double duty: marketplace card (via the logo field) and runtime app bar (served by your HTTP server at /icon.png).

See the developer guide for the full spec, a minimal server skeleton, and the publishing checklist.

Agent Personas

  • Product lives under agents/<name>/ with config.json, systemPrompt.md, and assets/.
  • Register an entry in agents/index.json with id / name / description / author / homepage / path. id equals the folder name. An optional logo overrides the default assets/avatar.png card image; omit it to keep the card and the chat avatar on the same picture.

Key Constraints

  • name means two different things: in SKILL.md frontmatter it is the lowercase kebab-case machine key the app loads Skills by; in the manifest it is the display name shown on cards. Keep frontmatter name === folder name === manifest id so the machine identity stays unambiguous.
  • Manifest description === frontmatter description: keep them as the same text.
  • Commit build outputs, strip sources: anything needed at runtime (ui/ builds, uv.lock, icon.png) must be in the repo; anything needed only for development (web/, node_modules/, data/, logs) must be stripped. Users download raw files and run them directly.
  • Do not use Git LFS (it breaks the app's raw download mechanism).

Related Skills

View on GitHub
GitHub Stars3
CategoryAI
Updated11d ago
Forks0

Languages

Python

Trust signals

75/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium2 low