Aegis-skills
MCP Skill Management Server with Role-Based Access Control
Install & Use
Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:
Help me install this AI Skill: Aegis-skills. It is used for: MCP Skill Management Server with Role-Based Access Control Full Skill content: https://321skill.com/skills/aegis-skills/raw/index.md Read that page and install it.
The prompt includes a link to the full Skill content. You can also view the full content.
Aegis Skills MCP Server is a skill management server built on the Model Context Protocol. Its core functionality is to provide a structured skill inventory and role-based access control. Through five MCP tools—list_skills, get_skill, list_resources, get_resource, and run_script—it enables AI clients to dynamically discover available skills, retrieve detailed skill definitions, manage skill resource files, and execute scripts within skills. Each skill is defined using a SKILL.md file, which includes the skill's name, description, a list of permitted MCP tools, and the user roles allowed to access it, enabling fine-grained permission management.
To use it, simply install the dependencies, start the server, and specify the skills directory. The default path is ~/.skills, but a custom directory can be specified via command-line arguments. Built-in example skills are also available for a quick trial. Once started, AI clients (such as Claude Desktop or VS Code Copilot) can point to this server via MCP configuration, allowing available skills to be dynamically displayed in various development scenarios based on the user's role.
This project is particularly suitable for teams or individuals who need to manage multiple AI skills and wish to implement granular permission control based on roles (e.g., admin, editor, developer). Agent developers, full-stack engineers, and DevOps engineers can use it to build a skill marketplace, enabling AI assistants to automatically load corresponding capabilities and tools based on user identity.
It is recommended to plan the skill directory structure and role system before deployment, utilizing the allowedRoles field to adhere to the principle of least privilege. The three built-in example skills (docx-handler, code-reviewer, data-analyzer) help users quickly understand the configuration. Note that the server itself does not provide specific skill implementations; rather, it acts as a management hub for the skill inventory and must be used in conjunction with Aegis-CLI or other MCP clients.
Key Features
Aegis Skills MCP Server binds skill definition, role permissions, and the list of MCP tools within a single SKILL.md file, enabling declarative permission management rather than merely aggregating a skill list.
Limitations
It requires Aegis-CLI or another MCP router to fully utilize the role-filtering functionality; when used alone, it only provides skill metadata queries.
FAQ
How do I define a new skill?
Create a new folder in the skills directory, place a SKILL.md file inside, and fill in fields such as name, description, and allowedRoles in YAML format.
How does it work with Aegis-CLI?
Aegis Router calls the list_skills tool to retrieve all skills and their permission information, then filters the available skill list based on the user's role.
Installation guide for AI assistants
If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:
Visit https://321skill.com/skills/aegis-skills/raw/index.md to read the original Skill definition (Markdown format) for Aegis-skills, and install it according to the instructions.
Raw Markdown URL for AI: /skills/aegis-skills/raw/index.md