workspace-fluency

Explain DailyOS workspace directory layouts and file schemas for AI agents.

3|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jamesgiroux/daily-operating-system --skill workspace-fluency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workspace-fluency
Source: https://github.com/jamesgiroux/daily-operating-system/tree/main/plugins/dailyos/skills/workspace-fluency
Command: npx skills add https://github.com/jamesgiroux/daily-operating-system --skill workspace-fluency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides essential knowledge about the structure, files, and conventions of a DailyOS workspace, ensuring all other skills and commands operate correctly within it.

Core Features & Use Cases

  • Workspace Detection: Identifies if the current directory is a DailyOS workspace.
  • Directory Structure Navigation: Understands the purpose and expected content of directories like Accounts/, Projects/, People/, _archive/, _inbox/, and data/.
  • File Schema Understanding: Explains the purpose and key fields of critical JSON and Markdown files such as dashboard.json, intelligence.json, person.json, schedule.json, prep.json, actions.json, emails.json, and manifest.json.
  • Entity Resolution: Details how to find and reference Accounts and Projects.
  • Role Preset System: Explains how manifest.json customizes vocabulary and output framing.
  • Loop-Back Convention: Guides on offering to save results back into the workspace.

Quick Start

Confirm if the current directory is a DailyOS workspace by checking for the presence of 'data/', 'Accounts/', 'Projects/', 'People/', '_archive/', and '_inbox/' directories.

Frequently Asked Questions about workspace-fluency

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

FAQPage Schema
How do I identify a DailyOS workspace directory structure?

To identify a DailyOS workspace, check the current directory for the presence of specific folders: 'data/', 'Accounts/', 'Projects/', 'People/', '_archive/', and '_inbox/'. These directories confirm the workspace structure and enable AI agents to navigate schemas correctly.

What file schemas are used in a DailyOS workspace?

DailyOS workspaces use specific JSON and Markdown file schemas including dashboard.json, intelligence.json, person.json, schedule.json, prep.json, actions.json, emails.json, and manifest.json. Each file defines key fields for managing accounts, projects, and people data.

How does entity resolution work for Accounts and Projects in DailyOS?

Entity resolution in a DailyOS workspace involves finding and referencing Accounts and Projects by navigating the 'Accounts/' and 'Projects/' directories. This process ensures AI agents accurately locate and interact with the correct workspace entities.

Can I customize AI agent vocabulary and output framing in DailyOS?

You can customize AI agent vocabulary and output framing in DailyOS using the manifest.json file. This role preset system configures how the workspace interprets instructions and formats responses, tailoring the agent's behavior to specific workflows.

What is the loop-back convention for saving outputs in a DailyOS workspace?

The loop-back convention in a DailyOS workspace guides AI agents to offer saving generated results directly back into the workspace directories. This ensures outputs are persistently stored within the correct file structure for future reference.

Do I need specific directories to use DailyOS workspace conventions?

You need the core directories 'Accounts/', 'Projects/', 'People/', '_archive/', '_inbox/', and 'data/' present to use DailyOS workspace conventions. Without these folders, AI agents cannot properly detect the workspace or apply the expected file schemas.