Agent skill

Workspace Status

by JetXu-LLM in JetXu-LLM/DocMason

Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state.

Apache-2.0Auto-check passedKnowledge Management

Install Workspace Status

skills CLI
$ npx skills add JetXu-LLM/DocMason --skill workspace-status -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JetXu-LLM/DocMason workspace-status --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JetXu-LLM/DocMason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/canonical/workspace-status .claude/skills/workspace-status && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workspace-status
GitHub stars
147
Token cost
~737 tokens
SKILL.md length
365 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state.

  • Works in 5 steps: Run docmason status --json. → Use the reported stage, bootstrap_state,… → Do not claim that a knowledge base… → …
  • Knowledge Management work in your project
  • SKILL.md covers Required Capabilities, Procedure, Escalation Rules and Completion Signal, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workspace Status is an agent skill from JetXu-LLM/DocMason. Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state.

Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `workflow.json`).

It sits in Knowledge Management. The repository describes itself as: DocMason is a repo-native agent that turns your complex office files into a local LLM knowledge base and your second brain. The repo is the app. Codex is the runtime. The licence is Apache-2.0.

When your agent uses it

  • Knowledge Management work in your project

Example prompts

  • “/workspace-status”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Run docmason status --json.
  2. Use the reported stage, bootstrap_state, control_plane, and pending_actions as the authoritative workspace status summary.
  3. Do not claim that a knowledge base exists unless status reports it as present.
  4. If the task is ambiguous, interpret pending_actions in context rather than as a rigid universal order.
  5. Return the final status interpretation to the main agent without mutating workspace state.

What it can do on your machine

Read from SKILL.md and the folder at commit 37ea2f1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workspace Status loads about 737 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 365 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~737

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JetXu-LLM/DocMason at commit 37ea2f1, republished under its Apache-2.0 licence (© JetXu-LLM). 365 words, ~737 tokens.

Download SKILL.mdSave it as .claude/skills/workspace-status/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
workspace-status
description
Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state.

Workspace Status

Use this skill when the task is to understand what stage the workspace is in and what should happen next.

Required Capabilities

  • local file access
  • shell or command execution
  • ability to reason about staged workflow state

If the agent cannot inspect the filesystem, stop and explain that the current workspace state cannot be determined safely.

Procedure

  1. Run docmason status --json.
  2. Use the reported stage, bootstrap_state, control_plane, and pending_actions as the authoritative workspace status summary.
    • use the environment block to distinguish self-contained, mixed, and degraded
    • treat only self-contained as ordinary ask-time ready
      • in practice this is the repo-local steady-state runtime the ask path may trust
  3. Do not claim that a knowledge base exists unless status reports it as present.
  4. If the task is ambiguous, interpret pending_actions in context rather than as a rigid universal order.
    • missing or stale adapter guidance matters only when the current flow depends on generated adapter files
    • missing or stale knowledge-base state matters directly for ordinary asking
  5. Return the final status interpretation to the main agent without mutating workspace state.

Escalation Rules

  • status is descriptive, not reparative. Do not silently switch into prepare, sync, or sync-adapters from inside this workflow.
  • When the workspace is stale or invalid, preserve that distinction instead of flattening it into a generic “not ready” message.
  • When the stage is control-plane-pending-confirmation, preserve that state explicitly and surface the exact pending approval action such as switch-host-to-full-access, prepare --yes, or sync --yes.
Show full SKILL.md (121 more words)Show less

Completion Signal

  • The workflow is complete when the main agent has the authoritative workspace stage, environment readiness state, and next obvious actions.

Notes

  • status is derived from the filesystem and runtime state. There is no daemon or database.
  • bootstrap_state is the explicit cached-ready summary for ordinary ask-time reuse.
  • environment.toolchain_mode, environment.isolation_grade, and environment.entrypoint_health are the stable readiness fields for the prepared runtime.
  • control_plane is the authoritative summary for governed waits, approvals, and shared jobs.
  • Pending actions may include prepare, switch-host-to-full-access, sync-adapters, sync, and validate-kb.
  • Control-plane pending confirmations are authoritative status truth, not optional side notes.
  • A staged knowledge base with pending synthesis or blocking validation is reported as knowledge-base-invalid.
  • sync-adapters is an operator-maintenance action, not a universal prerequisite before every ask turn.

© JetXu-LLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/canonical/workspace-status of JetXu-LLM/DocMason.

  • SKILL.md
  • workflow.json

Open the folder on GitHubat commit 37ea2f1

Compare with similar skills

Workspace Status next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workspace Status compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workspace Status this skillJetXu-LLM/DocMason147—~737Automated safety check: PassApache-2.0
Logseq Review Workflow Evallogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Esm Cjs Risk Scanlogseq/logseq45k—~3.3kAutomated safety check: PassAGPL-3.0
Knowledge Searchdataelement/bisheng12k—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed
  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed
  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Knowledge Search

    dataelement/bisheng

    Search the user's knowledge bases and knowledge spaces (企业知识库检索).

    12k GitHub stars~1.1k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Capture Conversation

    outline/outline

    Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.

    41k GitHub stars~474 tokensUpdated today
    Knowledge ManagementAuto-check passed

More from JetXu-LLM/DocMason

All 15 skills in this repo
  • Ask

    JetXu-LLM/DocMason

    Accept an ordinary user question inside a DocMason workspace, route it to the right inner workflow, and preserve conversation-native logs automatically.

    147 GitHub stars~7.1k tokensUpdated yesterday
    Auto-check passed
  • Adapter Sync

    JetXu-LLM/DocMason

    Generate or refresh the local Claude adapter surface for DocMason from canonical committed sources.

    147 GitHub stars~684 tokensUpdated yesterday
    Auto-check passed
  • Grounded Answer

    JetXu-LLM/DocMason

    Answer a user question through DocMason's canonical grounded workflow using retrieval, provenance tracing, render escalation, and a final answer-state check.

    147 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed
  • Grounded Composition

    JetXu-LLM/DocMason

    Produce evidence-backed research, planning, drafting, or composition output from the published DocMason knowledge base while preserving provenance and answer-file discipline.

    147 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed
  • Knowledge Base Sync

    JetXu-LLM/DocMason

    Stage, incrementally refresh, validate, and publish the DocMason knowledge base from the local source corpus.

    147 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • Knowledge Construction

    JetXu-LLM/DocMason

    Write bilingual Phase 3 knowledge objects for staged DocMason sources from rendered evidence and extracted structure.

    147 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Questions about Workspace Status

What does Workspace Status do?

Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state. Workspace Status is an agent skill from JetXu-LLM/DocMason. Inspect the current DocMason workspace stage and pending actions from the filesystem and runtime state.

When should I use Workspace Status?

Workspace Status fits situations like: knowledge Management work in your project.

How do I install Workspace Status in Claude Code?

Run `npx skills add JetXu-LLM/DocMason --skill workspace-status -a claude-code`. Or copy the skill folder (skills/canonical/workspace-status in JetXu-LLM/DocMason) into .claude/skills/workspace-status in your project. Claude Code loads it when a task matches its description.

How do I install Workspace Status in Codex?

Run `npx skills add JetXu-LLM/DocMason --skill workspace-status -a codex`. Or copy the skill folder (skills/canonical/workspace-status in JetXu-LLM/DocMason) into .agents/skills/workspace-status in your project. Codex loads it when a task matches its description.

Can I use Workspace Status in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetXu-LLM/DocMason --skill workspace-status -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workspace-status, .gemini/skills/workspace-status, .github/skills/workspace-status and .opencode/skills/workspace-status in your project.

What does Workspace Status need to run?

SKILL.md names no scripts, command-line tools or credentials: Workspace Status is instructions for the agent only.

Does Workspace Status access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workspace Status safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workspace Status use?

Workspace Status is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workspace Status use?

About 737 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workspace Status?

Skills that share tags, products or a category with Workspace Status: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workspace Status?

JetXu-LLM (a GitHub user) maintains it in JetXu-LLM/DocMason, which has 147 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.

Source: JetXu-LLM/DocMason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.