New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

skillos-mcp-server

Package Overview
Dependencies
Maintainers
1
Versions
3
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

skillos-mcp-server

SkillOS MCP Runtime — exposes the SkillOS skill registry as activatable MCP tools

latest
Source
npmnpm
Version
3.0.2
Version published
Weekly downloads
0
Maintainers
1
Weekly downloads
 
Created
Source

SkillOS Registry Archive

This directory stores superseded versions of skills. When a skill is updated to a new version, the previous version is moved here — not deleted.

Why This Exists

Mobile users in low-bandwidth environments, enterprise teams with locked AI configurations, or developers using older model APIs may depend on a specific skill version. Deleting old versions silently breaks these users.

The archive provides:

  • Permanent lineage — every version of every skill is traceable
  • Rollback capability — teams can pin to a specific version
  • Historical research — see how a domain's best practices evolved over time

Directory Structure

registry/archive/
├── tier-0/
│   └── software-architect-v1.0.0.md    ← original, superseded by v1.0.3
├── tier-1/
│   └── frontend-specialist-v1.0.0.md   ← superseded by v1.0.1
└── tier-2/
    └── react-expert-v1.0.0.md          ← superseded by v1.0.1

Archive Policy

RuleDetail
Never deleteArchived skills are permanent. Use DEPRECATED status if a skill has no valid successor.
Never modifyArchived files are read-only historical records. Bugs in archived versions are not patched.
Version in filenameFilenames always include the full version (v1.0.0) — no ambiguity.
Keep active registry cleanOnly the latest stable version of each skill lives in registry/tier-N/.

How to Archive a Skill (When Releasing an Update)

When releasing skill-name-v1.1.0.md:

# 1. Move the old version to archive
git mv registry/tier-1/skill-name-v1.0.0.md registry/archive/tier-1/skill-name-v1.0.0.md

# 2. Place the new version in the active registry
cp new-skill.md registry/tier-1/skill-name-v1.1.0.md
git add registry/tier-1/skill-name-v1.1.0.md

# 3. Commit both moves together
git commit -m "feat: update skill-name v1.0.0 → v1.1.0 (archive old version)"

Finding a Specific Version

To find all versions of a skill across active + archive:

# PowerShell
Get-ChildItem -Recurse registry/ -Filter "*frontend-specialist*"

# Bash
find registry/ -name "*frontend-specialist*"

MCP Runtime Behavior

The MCP Runtime (runtime/) by default only loads skills from registry/tier-N/ (active versions).

To activate an archived skill version via the activate_skill tool, pass archive: true:

{
  "skill_name": "frontend_specialist",
  "version": "1.0.0",
  "archive": true
}

The runtime will load from registry/archive/ instead of the active registry.

registry/archive/README.md · SkillOS · MIT License

Keywords

mcp

FAQs

Package last updated on 23 Sep 2026

Related posts