Skill

ws

Browse sayou workspace: list files as tree with metadata, search/grep content, read file contents, view version history. Use to manage stored notes/decisions.

Markdown

developer-tools

npx claudepluginhub pixell-global/sayou --plugin sayou

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Browse the sayou workspace. Show the user what's stored, find specific files, or check recent changes.

SKILL.md

Similar Skills

recall

Searches sayou workspace for past decisions, research, notes via structured path/frontmatter, content grep, and semantic search. Useful for recalling prior workspace knowledge.

sayou

memclaw

Creates, opens, and manages project workspaces in LiveDocs for cross-session memory, long-term tracking like diets or investments, and saving key outputs.

2 files

memclaw

obsidian-vault-manager

Manages Obsidian vault structure by organizing documents into service and work-log layers, adding files with auto-categorization and metadata, processing meeting notes, running health checks, and committing via Git.

5 tools

oh-my-obsidian

Stats

Stars27

Forks1

Last CommitFeb 19, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/ws — Workspace Browser

Browse the sayou workspace. Show the user what's stored, find specific files, or check recent changes.

Instructions

Start with an overview — use workspace_list with path: "/" and recursive: true to show the full file tree. Present it as a clean, readable tree with frontmatter metadata.

If the user asks about a specific file, use workspace_read to show its contents. Mention the version number and when it was last updated.

If the user asks about changes, use workspace_history on the relevant file to show version history. Offer to diff specific versions.

If the workspace is empty, tell the user:

Use /save to save findings or decisions from this session
Ask Claude to "save a note about [topic]" to create a file
Files support YAML frontmatter for metadata (status, type, tags, etc.)

For large workspaces, use workspace_search or workspace_grep to find specific files rather than listing everything.

Output Format

Show files as a tree with key metadata:

research/ competitor-analysis.md status=draft [v3, 2d ago] market-sizing.md status=reviewed [v1, 5d ago] decisions/ auth-architecture.md status=approved [v2, 1w ago] notes/ standup-2026-02-19.md type=meeting [v1, today]

Keep it concise. Don't read every file's contents unless asked — the tree overview is usually enough.

/ws — Workspace Browser

Browse the sayou workspace. Show the user what's stored, find specific files, or check recent changes.

Instructions

Start with an overview — use workspace_list with path: "/" and recursive: true to show the full file tree. Present it as a clean, readable tree with frontmatter metadata.
If the user asks about a specific file, use workspace_read to show its contents. Mention the version number and when it was last updated.
If the user asks about changes, use workspace_history on the relevant file to show version history. Offer to diff specific versions.
If the workspace is empty, tell the user:
- Use /save to save findings or decisions from this session
- Ask Claude to "save a note about [topic]" to create a file
- Files support YAML frontmatter for metadata (status, type, tags, etc.)
For large workspaces, use workspace_search or workspace_grep to find specific files rather than listing everything.

Output Format

Show files as a tree with key metadata:

research/
  competitor-analysis.md    status=draft     [v3, 2d ago]
  market-sizing.md          status=reviewed  [v1, 5d ago]
decisions/
  auth-architecture.md      status=approved  [v2, 1w ago]
notes/
  standup-2026-02-19.md     type=meeting     [v1, today]

Keep it concise. Don't read every file's contents unless asked — the tree overview is usually enough.