Ulasbilgen Mcp Skills Plugins
ulasbilgen-mcp-skills-plugins is a Claude Code plugin marketplace for the Build phase that exposes MCP server tools as on-demand skills without loading full MCP servers into main context.
by ulasbilgen · github.com/ulasbilgen/mcp-skills-plugins
Install MCP Server Skills as Claude Code plugins so Figma, browser, and other MCP tools run on demand without bloating the main context window.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ulasbilgen-mcp-skills-plugins@ulasbilgen/mcp-skills-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:ulasbilgen/mcp-skills-plugins") and the paste-ready config with skillselion.get_install_config("plugin:ulasbilgen/mcp-skills-plugins").
What it does
ulasbilgen-mcp-skills-plugins is a Claude Code plugin marketplace that repackages MCP server capabilities as discrete skills you invoke when needed, which keeps long tool schemas and server chatter out of your default context. Solo builders shipping UI from Figma, running browser-based QA, or documenting components install it when raw MCP wiring feels heavy or token-expensive for every chat. The catalog keywords point at end-to-end design-to-code and test automation paths—extract tokens, implement layouts, control Chrome, capture screenshots, and analyze pages—without maintaining a separate MCP config per workflow. With two bundled plugins, the scope is intentionally narrow: skill-shaped entry points to existing MCP servers, not a replacement for those servers themselves. Use it across Validate prototypes, Build integrations, and Ship testing when you want the same agent to reach external tools on demand.
Highlights
- Marketplace of MCP Server Skills packaged as Claude Code plugins instead of always-on MCP context
- Coverage spans browser automation, Chrome capture, Figma extract/implement, component and design-token workflows
- Supports inspect, navigate, screenshots, network/console devtools, and desktop testing tasks
- 2 plugins in the bundle aimed at selective tool invocation per task
- Designed so builders load MCP capabilities only when a skill triggers them
Why builders use it
Keeping multiple MCP servers attached burns context and complicates every Claude Code session even when you only need Figma or browser tools occasionally.
After registration, you invoke MCP Server Skills as plugins so external tools attach only for the tasks that need them.
At a glance
- Type - Plugin in LLM Integration.
- Adoption - 0 installs, 3 stars, 0 votes.
FAQ
Who is ulasbilgen-mcp-skills-plugins for?
Claude Code users who use MCP for design, browser, or devtools tasks and want those capabilities as installable skills instead of permanent context load.
When should I use ulasbilgen-mcp-skills-plugins?
Use it when integrating Figma-to-code, browser testing, or component documentation workflows and you want MCP invoked only per skill trigger.
How do I add ulasbilgen-mcp-skills-plugins to my agent?
Add the ulasbilgen/mcp-skills-plugins marketplace in Claude Code, install the two plugins, and ensure underlying MCP servers are configured per each skill’s README.
Comments
Share how you use ulasbilgen-mcp-skills-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.