# Nextcloud Time Manager

> Connects to Nextcloud using nextcloud-agent, retrieves latest calendar events and task files, interacts with the user to discover scheduling modifications, and applies updates/adds/removes to synchronize their personal schedule.

- Skill: `knuckles-team/nextcloud-time-manager` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add knuckles-team/nextcloud-time-manager`
- Raw SKILL.md: https://api.skillmd.com/api/skills/knuckles-team/nextcloud-time-manager/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Knuckles-Team (https://skillmd.com/u/knuckles-team)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/knuckles-team/nextcloud-time-manager

---


# Nextcloud Time Manager Workflow

**CONCEPT:KG-2.12**

Connects to Nextcloud using nextcloud-agent, retrieves latest calendar events and task files, interacts with the user to discover scheduling modifications, and applies updates/adds/removes to synchronize their personal schedule.

## Steps

### Step 0: Nextcloud Schedule Retrieval [skill: nextcloud-agent]
**Agent**: `intake-agent`
**Tools**: `graph_query, nc_files`

Retrieve current calendar lists and schedule events using nextcloud_calendar list_calendars and list_calendar_events tools. Fetch active tasks using nextcloud_files list_files in the task directory.
Expected: `calendars, events, tasks`

### Step 1: User Interaction
**Agent**: `processor-agent`
**Tools**: `graph_analyze, document_tools`

Analyze the retrieved calendar events and tasks. Present a summary of the current schedule to the user, and prompt them to specify any new events/tasks to add, modify, or remove.
Expected: `user_schedule_instructions`

### Step 2: Nextcloud Schedule Mutation [skill: nextcloud-agent]
**Agent**: `validator-agent`
**Tools**: `graph_query`

Apply requested scheduling modifications to Nextcloud. Call nextcloud_calendar create_calendar_event to register new events, or call nextcloud_files tools to write/update/delete task records as instructed.
Expected: `nextcloud_sync_results`

### Step 3: KG Persistence [depends_on: Step 2]
**Agent**: `validator-agent`
**Tools**: `graph_write`

Persist workflow results as nodes and edges in the Knowledge Graph.
Create appropriate typed nodes with metadata and link to existing domain entities.

## Output
- Nextcloud Time Manager results persisted in KG
- Structured report (MD/PDF)
- Audit trail with timestamps and agent attributions

## Human Oversight Required
✅ Critical decisions require human review and approval.

## Execution

Run this workflow as a dependency-ordered DAG. Steps with no unmet `depends_on` run in parallel; dependents run after their prerequisites complete.

- **Run first (in parallel):** Step 0 — Nextcloud Schedule Retrieval; Step 1 — User Interaction; Step 2 — Nextcloud Schedule Mutation
- **After level 0:** Step 3 — KG Persistence

**Execution:** If graph-os is reachable, offload the whole DAG via `graph_orchestrate action=execute_workflow` (or the `kg-delegate` skill) for true parallel/swarm execution. Otherwise execute the steps natively in dependency order: run steps with no unmet `depends_on` in parallel, then their dependents.