hermes - 💡(How to fix) Fix feat: Skill ownership and permission system for multi-user gateway

---
name: my-skill
owner: moment          # creator / owner identifier
permission: owner-write  # "owner-write" | "readonly"
---
  owner  : the user/platform ID who created the skill
  permission  :
  owner-write   (default for new skills): only the owner can modify/delete
  readonly  : no one can modify (useful for shared infrastructure skills)
2. CLI interface
# View permissions
hermes skills list --show-owner

# Change owner (only current owner can do this)
hermes skills permission set <skill> --owner <user>

# Set read-only mode
hermes skills permission set <skill> --mode readonly
3. Gateway-aware enforcement
When a user on a gateway platform (WeCom, Telegram, etc.) tries to
modify a skill via slash command or the AI's   skill_manage   tool:
If the user's identity matches   owner   → allow
If not → reject with message: "This skill is owned by {owner}.
Only the owner can modify it."
  readonly   skills reject modification from everyone
4. Backward compatibility
Existing skills without   owner   field = world-writable (current behavior)
The   permission   field is optional; absent = world-writable
  hermes curator pin   can coexist — pin protects from auto-archive,
owner-permission protects from user edits
Use Cases
Team shared skills: Admin creates and maintains shared skills;
team members use but cannot accidentally break them
Department isolation: Each department's skills are owned by
their lead, preventing cross-department modification
Production safety: Critical automation skills (deployment,
database operations) are locked to specific owners