skillporter
Related Servers
Alternatives to skillporter
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceRead-only MCP server for the markdown files coding agents load: CLAUDE.md, AGENTS.md, GEMINI.md, SKILL.md, rules, commands and memory. Lints frontmatter, broken imports, invisible characters and hidden comments, shows which files load per tool and folder, and estimates token budgets. Never writes, deletes or touches the network.74MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for AI coding agents to inspect repositories, audit code quality, route engineering skills, and plan safe issue/PR workflows.1MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.182 PyPI4MIT
- AlicenseAqualityCmaintenanceMCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.414 npmMIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.57 npmMIT
TDQS
Scored across 18 tools
Several clusters overlap: add vs install vs import all move skills into harnesses, and inspect vs scan vs diagnose vs status all report on environment/skill health with fuzzy boundaries. Descriptions add some nuance (repository/archive vs local directory vs .skillpack restore), but an agent could easily pick the wrong one. Preview/context/consolidate_preview form a second slightly muddled read cluster.
Every tool follows the identical skillporter_<verb_or_noun> snake_case pattern with no camelCase or style drift. Names are short, predictable, and readable across the whole set.
18 tools is on the heavy side for a skill-portability server and pushes into the borderline range. Given the redundant install/add/import and inspect/scan/diagnose groupings, a few tools likely don't fully earn their place.
The surface covers the full lifecycle: detect/matrix/inspect/scan (discovery), suggest/insights/context (analysis), add/install/sync/import (apply), export/diff (portability), remove (teardown). Minor gaps like a direct update/rename operation are largely absorbed by sync and import.