seis-trusted-marketplace

Curates trusted plugins, MCP servers, and GitHub Marketplace entries for the SEIS ecosystem.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-trusted-marketplace-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-trusted-marketplace
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/seis-trusted-marketplace-plugin/skills/seis-trusted-marketplace
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-trusted-marketplace-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Choosing which plugins, MCP servers, GitHub Marketplace actions, or AI model channels to trust is risky and confusing, especially for non-developers. This Skill provides a governed curation workflow that evaluates trust posture, matches sources to capability lanes, and gates live activation behind explicit approvals. ## Core Features & Use Cases - Trust Evaluation: Checks publisher verification, documentation quality, maintenance activity, permission scope, and rollback paths before recommending any marketplace source. - Capability Lane Routing: Routes requests into eight governed lanes (Data Engineering, Development, Design, Learning, Monitoring, Productivity, Security, Testing) instead of activating every connector at once. - Repo-Bound Governance: Binds curation work to the SEIS UIX-Apps branch contract with validation commands like npm run validate and check scripts before any publication. - Use Case: A designer wants to add a new AI tool integration. The Skill evaluates whether it should ship as an MCP server, Codex plugin, or GitHub Marketplace Action, explains the trade-offs in plain language, and blocks live installs until target, auth, approval, and rollback owner are explicit. ## Quick Start Ask the assistant to review a specific plugin or MCP server for trustworthiness and recommend which capability lane and activation gates apply before installing it.

Frequently Asked Questions about seis-trusted-marketplace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a GitHub Marketplace plugin is trustworthy?▼

Check the trust posture: official or verified publisher, clear documentation, active maintenance, minimal permissions, and a rollback or removal path. This Skill walks through each signal and explains the result in non-technical language before any activation.

Should I use an MCP server or a GitHub Marketplace Action for a new integration?▼

Prefer MCP for new AI tool integrations when the choice is available. Use GitHub Marketplace Actions only for small reusable repository automation, and avoid building new GitHub App-based Copilot Extensions in favor of MCP or plugin packaging.

What validation checks run before publishing marketplace changes?▼

The Skill prefers npm run validate first, then check:workspace, check:trusted-marketplace-intake, check:seis-trusted-marketplace-plugin, check:aggressive-capability-map, check:connector-activation-report, and automation:publish-readiness for the bound UIXAppTTR branch.

Can this Skill install or activate plugins directly?▼

No. Live installs, writes, deploys, and credential use stay blocked until the target, authentication, approval, and rollback owner are explicit. The Skill curates and plans activation rather than executing it autonomously.

When should GitHub Marketplace Apps be used instead of plugins?▼

Use GitHub Marketplace Apps only after there is a real app surface, a support model, and a completed permission review. For most SEIS integrations, the GitHub MCP Registry or local Codex plugin packaging is the preferred channel.