nextcloud-delivery

Place generated artifacts into standardized AGENT_SHARE subfolders on Nextcloud sync roots.

Updated May 7, 2026
One-click install
npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill nextcloud-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nextcloud-delivery
Source: https://github.com/MOODMNKY-LLC/mnky-atlas/tree/main/skills/nextcloud-delivery
Command: npx skills add https://github.com/MOODMNKY-LLC/mnky-atlas --skill nextcloud-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inconsistent manual work of organizing and delivering files to a shared Nextcloud sync root, ensuring all handoff packages are mobile-accessible and properly structured for MNKY agents without ad-hoc folder layouts.

Core Features & Use Cases

  • Standardized Folder Layout: Uses a consistent set of subfolders (00_INBOX, 10_Docs, 20_Exports, 30_Maps, 40_Agents, 90_Archive) to keep all files organized and easy to navigate.
  • Intelligent Placement Rules: Automatically routes files to the correct subfolder based on type (fresh deliverables, polished docs, maps, agent artifacts) to reduce sorting effort.
  • Use Case: When an MNKY agent generates a new project export and topology map, use this Skill to place them in the correct AGENT_SHARE subfolders so team members can access them immediately on mobile devices.

Quick Start

Use the nextcloud-delivery skill to place the generated project export and topology map into the correct folders under the AGENT_SHARE directory for the current agent.

Frequently Asked Questions about nextcloud-delivery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize files for mobile agent handoff in a Nextcloud sync root?

Nextcloud file delivery for mobile agent handoff eliminates inconsistent manual folder organization by automatically placing generated artifacts into standardized AGENT_SHARE subfolders like 00_INBOX and 40_Agents. This enforces stable, human-readable structures so team members can immediately access files on mobile devices.

What is the standardized folder layout for delivering agent artifacts to Nextcloud?

The standardized folder layout for Nextcloud delivery uses specific AGENT_SHARE subfolders: 00_INBOX, 10_Docs, 20_Exports, 30_Maps, 40_Agents, and 90_Archive. This consistent structure keeps all handoff packages properly organized and easy to navigate across Windows and WSL sync roots.

How do I automatically route project exports and topology maps to the correct Nextcloud folders?

Automatically routing project exports and topology maps to Nextcloud folders relies on intelligent placement rules that direct fresh deliverables and maps to their correct subfolders. The skill matches file types like polished docs or agent artifacts to the appropriate AGENT_SHARE directory to reduce sorting effort.

Does Nextcloud file delivery work with Windows and WSL sync roots?

Nextcloud file delivery supports both Windows and WSL sync roots for placing generated artifacts. It performs canonical path resolution for existing agent directories and pre-delivery copy verification to ensure file accessibility across these environments.

How do I verify file accessibility before delivering handoff packages to a Nextcloud sync root?

Verifying file accessibility before delivering handoff packages to a Nextcloud sync root is handled through built-in pre-delivery copy verification. This mechanism checks the copied artifacts against the standardized AGENT_SHARE directory to ensure they are properly placed and accessible.