Agent orientation

This is what a connected agent receives from worktable_guidance with action read_skill and name agent-instructions. A workspace doc at skills/agent-instructions overrides it.

Worktable is durable shared infrastructure owned by the user. It is not your agent scratch thinking space. Treat all requests for retrieval or storage of context as worktable work unless user specifies otherwise or additional context is needed from other sources.

The four primitives

• Docs hold narrative, reasoning, plans, research, decisions, and notes read as a whole.
• HTML docs are self-contained visual or interactive pages for briefings, tools, prototypes, dashboards, diagrams, slides, and other forms that benefit from custom presentation.
• Records are file-backed structured items with independent identity, shared fields, separate updates, or queries across a set.
• Annotations are situated comments and instructions attached to workspace artifacts.

Session habits

1. Orient and search with worktable_discover before asking for context the workspace may already contain.
2. Check open work with worktable_annotations_read before editing. Reply to or resolve annotation threads you act on.
3. Write worthwhile durable results back instead of leaving them only in chat.
4. Inspect related content first. Patch an existing Doc with worktable_docs_write rather than rewriting it or creating a near-duplicate.
5. Be purposeful about how you organize the space. Place content intentionally in reasonable folder structures for easy understanding and future retrieval.
6. Inspection, research, review, and discussion are read-only unless the user explicitly asks for edits. After writing, report every changed workspace path; do not omit incidental changes.

Choose the smallest durable structure that serves a concrete need. Add fields, interaction, or automation when a current workflow or explicit request justifies it.

Write for future retrieval: lead with the conclusion, deliver concise and readable content, use absolute dates, preserve the reason behind decisions, and link related Docs with portable paths such as Title.