AgenticSelfHostSkills

Create complete, portable handoffs from Manus to another agent or Manus instance. Use when transferring an in-progress task, project, workflow, research effort, or operational context and the recipient needs both a concise execution prompt and a structured repository of supporting documents, custom skills, decisions, rules, and artifacts.

Manage and interact with a Subsonic-compatible music streaming server (Navidrome or Airsonic); control playback, manage playlists, and trigger library rescans via the OpenSubsonic API.

Integration guidance for using Subsonic/OpenSubsonic client libraries in netrunner and other projects.

Teaches Soulseek culture, etiquette, and search strategies; logs discoveries to Obsidian.

Manage and automate music downloads via slskd (Soulseek daemon), including search, queue management, and transfer monitoring.

Wraps the Slsk MCP server (MCPMarket) with safety rules, rate limits, and session logging for Soulseek access.

Configures Nginx/Caddy reverse proxies and Cloudflare/WireGuard tunnels for safe homelab service exposure.

Operate, inspect, maintain, back up, restore, and safely evolve Proxmox VE 9 nodes, storage, networking, LXC, and VMs using official-first guidance. Use for Proxmox node administration, guest lifecycle, storage, network, package updates, backup/restore, upgrade planning, API/CLI inspection, and third-party helper-script review.

Plan, inspect, approve, create, validate, and roll back a fresh Proxmox service guest while protecting legacy guests. Use before creating or changing an LXC or VM for self-hosted services, especially on resource-constrained Proxmox hosts.

Govern a personal software and creative portfolio with explicit ownership, lifecycle status, and attention limits. Use when deciding where a new idea belongs, reviewing overlapping repositories, selecting one active experiment, maintaining a portfolio ledger, or archiving dormant work without applying startup traction metrics to personal tools.

Create, organize, and maintain Obsidian vault notes, folders, and links; manage templates, daily notes, and vault structure via the Obsidian Local REST API or filesystem.

Designs and enforces folder structure, naming conventions, and template standards for Obsidian vaults.

Create and maintain music-related journal entries in Obsidian; log listening sessions, DJ set plans, album reviews, discovery notes, and curation reflections.

Logs homelab events, changes, incidents, and maintenance notes to structured Obsidian notes.

Orchestrates the full acquisition-to-playback media pipeline for the netrunner project.

Reliably inspect, create, edit, validate, and transfer files in a Windows-hosted WSL workspace. Use when a task names a WSL path, a `\\wsl.localhost` path, a Windows/WSL project location, or when remote file writes, UNC paths, mounted workspaces, and WSL shell execution may disagree.

Plans music production and release projects with milestones, task breakdowns, and Obsidian integration.

Logs active listening sessions, albums, and tracks to Obsidian with ratings, notes, and context.

Guard consequential personal music-library work with explicit ownership, preview, recovery, and approval checks. Use before scanning, tagging, moving, deduplicating, importing, deleting, or synchronizing music files, metadata, playlists, samples, stems, or mixlists.

Import, tag, and organize music files using beets; enforce consistent folder structure, metadata, and MusicBrainz tagging across the local music library.

Teaches agents when to query Cipher/Mem0, when to consult Obsidian, and when to log decisions inline — routing context retrieval to the right memory layer.

Assembles and configures the full homelab media stack including slskd, Navidrome/Subsonic, and beets.

Bridges lyric writing with music theory concepts — helps composer-lyricists align words with chord function, melody contour, rhythm, and song structure.

Safely integrate private local knowledge systems using explicit data classification, sanitized fixtures, compatibility checks, and reversible writes. Use before indexing, syncing, retrieving from, migrating, exporting, or changing a personal vault, memory runtime, note template, or knowledge connector.

Maps Proxmox cluster topology including nodes, VMs, containers, storage, and network layout.