Use when users need to manage ClawDeck project workspaces backed by Felo LiveDoc — creating, loading, switching workspaces, saving artifacts, querying history, or managing tasks. Triggers on workspace-related intent combined with project/client names, or on 401 UNAUTHORIZED errors from Felo API.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Use when users need to manage ClawDeck project workspaces backed by Felo LiveDoc — creating, loading, switching workspaces, saving artifacts, querying history, or managing tasks. Triggers on workspace-related intent combined with project/client names, or on 401 UNAUTHORIZED errors from Felo API.
ClawDeck — Workspace Manager
The Agent's external brain for projects. Once active, the Agent continuously syncs tasks, artifacts, and knowledge to the corresponding LiveDoc, so anyone (including future sessions or colleagues) can load the workspace and immediately get full context.
Core Concepts
Concept
Description
Workspace
One project = one LiveDoc
Active Workspace
Session-level state; all operations auto-sync here
README
The Agent's memory of the project; Agent maintains proactively
Artifacts
Key outputs; Agent asks before saving
Tasks
Tracking records for substantive work; Agent maintains silently
Registry
~/.claude/workspaces.json, maps project names to LiveDoc IDs
One-off generation unrelated to any project/workspace
User has not installed the Felo LiveDoc NPM package
Workflows
0. First-Time Installation
User pastes GitHub install link → execute installation → after completion, automatically enter Login flow (0a).
0a. Login / Re-authorization
Trigger conditions (either one):
First-time installation, Key not yet configured
Any API call returns {"status":401,"code":"UNAUTHORIZED","message":"Invalid API Key"}
Flow:
Send login link:
"Please click the link to log in / register a Felo account: https://felo.ai/settings/api-keys
Once done, paste the Key back to me and I'll complete the setup automatically."
User pastes Key → write to config:
export FELO_API_KEY="user's Key"
Or persist to ~/.claude/env (platform-dependent).
Verify: $SCRIPT list
Pass + first install → show usage introduction (see "First-Time Usage Introduction" below)
First-Time Usage Introduction (show only on first install; skip on re-authorization):
"🎉 Setup complete! You can now use the following commands to manage workspaces:
📁 Create workspace — Create a standalone workspace for a new project
Example: 'Create a workspace called Client Acme'
📂 Load workspace — Open an existing project, restore context
Example: 'Load the Acme workspace'
📋 View workspace — List all projects or view project contents
Example: 'What workspaces do I have?' / 'What's in the Acme workspace?'
💾 Save artifacts — Important outputs will prompt you to save
The workspace records everything we do. You can view it anytime on the web: https://felo.ai"
1. Load Workspace
Read ~/.claude/workspaces.json, fuzzy-match project name. If not found locally, try $SCRIPT list --keyword.
Found: Set as active → $SCRIPT get-readme SHORT_ID → present README as workspace briefing → append link https://felo.ai/livedoc/SHORT_ID?from=claw. If README is empty or missing, fall back to $SCRIPT resources SHORT_ID to show the resource list.
Not found: "No workspace found for '[X]'. Want me to create one?"
Iron rule: When the workspace is active, if the user's request requires the Agent to invoke tools to produce new content (search, generate, analyze, etc.), the very first step is always create-task — before doing anything else.
Decision flow:
User sends a message
Does this message require the Agent to invoke tools to produce new content? (search, generate, collect, analyze, write)
Yes → immediately create-task → execute → update-task to mark complete
No → execute directly, no task needed
Requires task creation (invoking tools to produce new content):
"Collect client info on Mr. Zhang" → requires search + generation
(--operated-by rule same as above — pass it when the Agent has a name.)
Execute silently — do not narrate the task sync to the user. If you forgot to create a task before starting, create it retroactively and mark it DONE immediately. Never skip it.
4. Save Artifacts (Ask First)
After producing significant output, ask the user: "Want me to save this to the [project] workspace?"
Significant artifacts = research reports, competitive analyses, meeting summaries, generated documents, key data exports. Intermediate drafts do not need to be saved.
The README is the Agent's memory of the project — not a work log. Agent maintains proactively, no need to ask the user.
README Structure Template:
# [Project Name]## What This Project Is
[Project background, objectives, stakeholders]
## User Preferences & Work Patterns
[How the user likes to work, what dimensions they care about, specific requirements]
## Current Progress
[Where things stand now — updated each session]
Last updated: YYYY-MM-DD
When to update README — core question: Did this operation bring any new understanding?
Update (new understanding):
When the project is first created — record "what this project is about"
When the user expresses preferences or work patterns — record "how the user wants to work" (e.g. collection dimensions, focus areas, format requirements)
When the project's nature or direction changes
Do NOT update (repeated execution):
Same-pattern repeated operations (e.g. after collecting info on Mr. Zhang, collecting info on Mr. Li using the same pattern — no update needed)
The mere fact of executing an action (generating a document is not worth recording by itself)
Update method: Read → merge in memory into the correct section → write back in full. Never blindly append to the end.
$SCRIPT get-readme SHORT_ID to read current content
Locate the target section in memory and insert:
Project background → ## What This Project Is
User preferences → ## User Preferences & Work Patterns
Progress changes → replace ## Current Progress section content
Update Last updated: YYYY-MM-DD to today's date
$SCRIPT update-readme SHORT_ID --content "..." to write back
Initialization (README is empty or missing): Skip step 1, write the full skeleton directly with update-readme.
Update the in-memory snapshot. Tell the user: "Workspace refreshed." If anything changed, briefly describe the differences (new resources, README updates, new tasks).
8. List Contents
$SCRIPT resources SHORT_ID, grouped by type, artifacts newest first.
