Menu
Read and write memory JSON files in the user's dayarc folder.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Render brief from template and deliver to configured targets (email, GitHub issue, terminal).
Generate structured talking points for performance reviews, 1:1s, and self-assessments from accumulated monthly summaries.
Check for and apply updates to the Dayarc agent package from GitHub.
Extract corrections from user's reply to a brief email.
Conversationally configure a new signal source connector (Jira, ADO, Linear, Slack, etc.), generate a custom COLLECT skill, and register it in config.json.
Initialize Dayarc data directories, user config, and optional scheduler on first run or reconfiguration.
| name | Dayarc Memory |
| description | Read and write memory JSON files in the user's dayarc folder. |
~/Documents/dayarc/memory/
Read any JSON file from the memory directory. Common files:
daily/daily-profile-{YYYY-MM-DD}.jsonweekly-summary-current.jsonweekly-summary-prev.jsonweekly-archive/{week-date}.jsonmonthly-summary.jsonmonthly-archive/{YYYY-MM}.jsonruns/{date}-{type}.jsonTo list files: list the contents of a subdirectory.
Write JSON to the memory directory. ALWAYS read memory-schemas.md first and validate the structure.
⚠️ IMPORTANT — Always use PowerShell shell commands for all file writes. Never use the Copilot CLI built-in
createtool. Thecreatetool writes to the session sandbox, not to~/Documents/dayarc/memory/. Files written with it are lost when the session ends.Use this pattern for every write:
$memDir = Join-Path ([Environment]::GetFolderPath("MyDocuments")) "dayarc\memory" $json | Set-Content (Join-Path $memDir "{relative-path-to-file}") -Encoding UTF8For subdirectories (e.g.,
daily/,runs/,weekly-archive/), ensure the directory exists first:$dir = Join-Path $memDir "daily" if (-not (Test-Path $dir)) { New-Item -ItemType Directory -Path $dir -Force }
Write runs/{date}-{type}.json (e.g., runs/2026-03-14-pm.json) before sending email. If tag exists, skip — already ran.
When writing: validate against memory-schemas.md. When reading: handle missing files gracefully (bootstrap).