Weslinkde Weslink Claude Marketplace
weslinkde-weslink-claude-marketplace is a Claude Code plugin for the Build phase that registers Weslink’s internal integration and documentation plugins for German telecom and EDIFACT work.
by weslinkde · github.com/weslinkde/weslink-claude-marketplace
Load Weslink’s internal Claude Code plugins for German telecom integrations, EDIFACT invoicing, and wiki-style domain documentation when you work on that stack.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install weslinkde-weslink-claude-marketplace@weslinkde/weslink-claude-marketplaceBuilt 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:weslinkde/weslink-claude-marketplace") and the paste-ready config with skillselion.get_install_config("plugin:weslinkde/weslink-claude-marketplace").
What it does
weslinkde-weslink-claude-marketplace is an internal Claude Code plugin marketplace published from the Weslink organization. It bundles two plugins aimed at builders who already operate inside Weslink’s German telecom and integration context—think EDIFACT invoicing, segment definitions, KibiConnect, carrier providers, and internal wiki or handbook pages rather than greenfield SaaS from scratch. For Skillselion’s solo-builder audience, treat this as a specialized integration catalog: valuable if you contract on Weslink stacks or mirror their EDIFACT and telecom patterns, otherwise skip it in favor of general integration skills. Installing means registering this marketplace in Claude Code and enabling the specific plugins you need; the agent then gains domain prompts and tooling aligned to Weslink documentation practices. It is not a public skills.sh-style general directory—it is org-scoped domain knowledge packaged as plugins.
Highlights
- Internal Claude Code plugin marketplace with 2 bundled plugins
- Domain focus: German telecom (Telekom, Vodafone) and Weslink platform context
- EDIFACT invoicing and segment parsing support keywords
- KibiConnect integration and provider-oriented workflows
- Tiptap/wiki-style documentation and handbook creation helpers
Why builders use it
Working on Weslink telecom integrations without curated agent context forces you to re-read handbooks and mis-parse EDIFACT segments in every session.
You install two domain plugins from one marketplace so Claude Code carries Weslink definitions, parsing, and doc patterns into integration tasks.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is weslinkde-weslink-claude-marketplace for?
It is for Weslink-aligned developers who need Claude Code plugins for telecom integrations, EDIFACT, and internal documentation workflows.
When should I use weslinkde-weslink-claude-marketplace?
Use it when your build work involves Weslink platform context, KibiConnect, or German carrier integrations rather than generic app features.
How do I add weslinkde-weslink-claude-marketplace to my agent?
Register the weslinkde/weslink-claude-marketplace repo as a Claude Code plugin marketplace, then enable the two plugins from that catalog in your settings.
Comments
Share how you use weslinkde-weslink-claude-marketplace, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.