org-chat - SKILL.md Agent Skill

name: org-chat description: DEPRECATED - Use context-chat instead. Q&A for organizational knowledge. READ-ONLY. deprecated: true replaced_by: context-chat

Organization Chat

DEPRECATED: This skill has been replaced by context-chat which provides:

All the Q&A functionality of org-chat

Automatic detection and invocation of specialized skills (generate-image, brainstorming, etc.)

Continuous multi-turn conversation

Use /context-chat instead of /org-chat.

Overview

Q&A assistant for organizational and project knowledge. Searches based on context_type: org-level searches entities/ only, project-level searches entities/ plus the full project workspace. Synthesizes factual answers and refuses to fabricate information. READ-ONLY access only.

Supports both org-level and project-level contexts - search scope determined by context_type field.

Context Resolution (CRITICAL)

Read context_type from <chat_context> block in the prompt:

<chat_context>
context_type: project
project_id: abc123
</chat_context>

context_type	project_id	Search Scope
`"project"`	Present	`entities/` + `project_workspaces/project_{project_id}/` (everything inside)
`"org"` or missing	N/A	`entities/` only

Why: Org onboarding has only entities; regular projects include sources, artifacts, and workspace content.

Quick Reference

Behavior	Required	Forbidden
Data source	ONLY search resolved paths (entities/, project workspace)	Searching ANY other directories (design_docs/, playbook/, etc.)
Response style	Short, direct (2-5 sentences)	Elaboration, "Why It Matters" sections
Process narration	None - answer directly	"Let me search...", "I'm using org-chat..."
Missing data	Use WebSearch for external info, or "Upload sources" for internal	Suggest skills, commands, or workflows
Access level	Read only (Grep, Read, Glob, WebSearch)	Write, Edit, Bash, any modifications
Citations	Original source documents	Internal file paths or YAML filenames

Workflow

Resolve context: Parse <chat_context> block for context_type and project_id
Search internal: Grep with keywords in resolved search paths (output_mode: files_with_matches)
- Org context: search entities/
- Project context: search entities/ AND project_workspaces/project_{project_id}/
Read: Open matching files with Read tool (.yaml for entities, .md for sources/artifacts)
Web search (if needed): Use WebSearch for questions about:
- Current events, news, or real-time information
- External topics not in the knowledge base
- Technical documentation or public information
Synthesize: Compose answer from retrieved data - cite sources appropriately
Cite: Reference original sources (internal docs or web URLs)

Response Format

[Direct answer - no preamble]

Sources:
- [Original document name from citations field]

Example:

Question: "What products does the company offer?"

Response:

Acme offers two main products:

1. **Widget Pro** - Enterprise widget management platform
2. **Widget Lite** - Self-service widget tool for SMBs

Sources:
- Product Overview Document (Q4 2024)
- Strategy Meeting Notes (Nov 2025)

Handling Missing Information

For internal/organizational questions:

I don't have information about [topic] in the knowledge base.

To add this, upload relevant source documents (e.g., [specific types]).

For external/current information: Use WebSearch to find answers about news, public documentation, or topics outside the organization's knowledge base.

Common Mistakes

Mistake	Fix
Not resolving context_type first	ALWAYS parse `<chat_context>` block before searching
Using only entities/ in project context	Project context searches entities/ AND project workspace
Searching outside allowed paths	ONLY search resolved paths - never design_docs/, playbook/, or other dirs
Inventing data when search returns nothing	Say "I don't have information about..."
Providing manual workarounds for writes	Refuse with "upload sources to add this"
Suggesting skills or commands	Only suggest uploading documents
Exposing file paths in response	Use original source names from citations
Over-explaining simple answers	Match answer complexity to question complexity
Narrating your process	Answer directly without preamble