New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Workspace Bootstrap

by JetXu-LLM in JetXu-LLM/DocMason

Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state.

Apache-2.0Auto-check passedKnowledge Management

Install Workspace Bootstrap

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

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

GitHub CLI
$ gh skill install JetXu-LLM/DocMason workspace-bootstrap --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-bootstrap .claude/skills/workspace-bootstrap && 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-bootstrap
GitHub stars
147
Token cost
~2.1k tokens
SKILL.md length
1,134 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state.

  • Works in 12 steps: Inspect runtime/bootstrap_state.json… → If .venv is absent or docmason is not… → Once the launcher succeeds, prefer the… → …
  • Knowledge Management work in your project
  • SKILL.md covers Required Capabilities, Procedure, Escalation Rules and Completion Signal, plus 1 more section
  • Calls python, brew and soffice

What it does

Workspace Bootstrap is an agent skill from JetXu-LLM/DocMason. Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state.

Its SKILL.md is about 2.1k 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-bootstrap”

Requirements

  • Python 3

Workflow steps

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

  1. Inspect runtime/bootstrap_state.json when it exists.
  2. If .venv is absent or docmason is not yet runnable from the repo-local environment, start with
  3. Once the launcher succeeds, prefer the repo-local environment for subsequent commands
  4. Run docmason doctor --json when you need a readiness snapshot after launcher completion or on an already prepared workspace.
  5. Run docmason prepare --json --yes when the launcher was not used, or when bootstrap needs an explicit rerun to repair or complete the…
  6. If prepare reports a degraded result, follow the reported next steps and rerun only the necessary deterministic command.
  7. Use docs/setup/manual-workspace-recovery.md only when the launcher or prepare still cannot finish honestly after the governed automatic…
  8. If the corpus already contains PPTX, DOCX, or XLSX files and LibreOffice is missing or detected but unusable
  9. Run docmason status --json when you need to confirm the resulting workspace stage.
  10. Recommend docmason sync --json when source files are present and the user needs a usable knowledge base next.
  11. If the current agent ecosystem is a compatibility target such as Claude Code rather than the native Codex path, decide here whether…
  12. Recommend docmason sync-adapters --json only when the current agent ecosystem depends on generated adapter files or those files are…

What it can do on your machine

Read from SKILL.md and the folder at commit 362417b. 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

    Shell commands in SKILL.md call:

    • python
    • brew
    • soffice

    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 Bootstrap loads about 2.1k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 1,134 words of instructions outside code blocks.

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

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 362417b, republished under its Apache-2.0 licence (© JetXu-LLM). 1,134 words, ~2,073 tokens.

Download SKILL.mdSave it as .claude/skills/workspace-bootstrap/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
workspace-bootstrap
description
Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state.

Workspace Bootstrap

Use this skill when the task is to make a DocMason workspace ready for use, or when ask has discovered that the workspace is not yet ready for a safe answer path.

This is also the correct first explicit setup workflow when the current agent is not running on the native Codex path and needs to determine whether adapter-specific guidance should be refreshed.

Required Capabilities

  • local file access
  • shell or command execution
  • ability to inspect command output

If the agent cannot perform these capabilities, stop and explain that the environment is not capable enough for the workflow.

Procedure

  1. Inspect runtime/bootstrap_state.json when it exists.
    • if it already says the current workspace root is ready and .venv still exists, do not rerun deep bootstrap work by default
    • if it belongs to another workspace root, treat that as a moved-repo repair case
    • treat self-contained as the only ordinary ask-time ready environment grade
      • in practice this means the repo-local steady-state runtime is trusted for ordinary work
    • treat mixed and degraded as repair-needed states
  2. If .venv is absent or docmason is not yet runnable from the repo-local environment, start with:
    • ./scripts/bootstrap-workspace.sh --yes
    • add --json when machine-readable output helps
    • on native Codex ordinary cold starts, treat ./scripts/bootstrap-workspace.sh --yes --json as the single governed mutation surface before ask-time workspace work can continue
    • the launcher should run a capability-aware preflight first, then either continue silently or stop once with a structured host-access-upgrade boundary
    • in Codex Default permissions, the ordinary path should use repo-local bootstrap cache only; it should not probe shared user cache paths first
    • the launcher should prefer the controlled UV bootstrap asset path for ordinary native cold starts instead of broad local-machine Python scavenging
    • the launcher may honor an explicit DOCMASON_BOOTSTRAP_PYTHON override for operator repair, but that is not the ordinary first-run path
  3. Once the launcher succeeds, prefer the repo-local environment for subsequent commands:
    • ./.venv/bin/python -m docmason doctor --json
    • ./.venv/bin/python -m docmason prepare --json --yes
    • or the docmason executable installed inside .venv
  4. Run docmason doctor --json when you need a readiness snapshot after launcher completion or on an already prepared workspace.
  5. Run docmason prepare --json --yes when the launcher was not used, or when bootstrap needs an explicit rerun to repair or complete the repo-local environment.
  6. If prepare reports a degraded result, follow the reported next steps and rerun only the necessary deterministic command.
  7. Use docs/setup/manual-workspace-recovery.md only when the launcher or prepare still cannot finish honestly after the governed automatic path has already had enough access.
  8. If the corpus already contains PPTX, DOCX, or XLSX files and LibreOffice is missing or detected but unusable:
    • LibreOffice is required only for an Office-rendering corpus; it is not a universal machine baseline dependency
    • on macOS with Homebrew already present, DocMason may use brew install --cask libreoffice-still
    • on macOS without Homebrew, DocMason should use the official LibreOffice installer path instead of trying to install Homebrew first
    • on macOS, if LibreOffice is already detected but fails the governed smoke probe, prepare --yes should treat that as a repair or reinstall case rather than as a fake ready state
    • on Linux, install LibreOffice with the distro package manager or the official packages, then ensure soffice is on PATH
  9. Run docmason status --json when you need to confirm the resulting workspace stage.
  10. Recommend docmason sync --json when source files are present and the user needs a usable knowledge base next.
  11. If the current agent ecosystem is a compatibility target such as Claude Code rather than the native Codex path, decide here whether generated adapter guidance is needed.
  12. Recommend docmason sync-adapters --json only when the current agent ecosystem depends on generated adapter files or those files are missing or stale.
  13. Once .venv exists, prefer the repo-local interpreter for subsequent repository commands instead of switching back to an arbitrary system Python.
  14. Return the final readiness judgment to the main agent. Do not delegate environment sign-off.
Show full SKILL.md (478 more words)Show less

Escalation Rules

  • If the platform or Python version is unsupported, stop and surface that blocker directly.
  • If prepare can only proceed through a higher-intrusion install step, explain it explicitly rather than hiding it inside automation.
  • If system-level installation requires additional permissions, request them when the current platform supports that flow; otherwise give the user the exact command or GUI step to run.
  • On native Codex/macOS, if the thread is still in Default permissions and higher access is required for downloads or machine-level setup, stop once with an explicit Full access upgrade instruction. After Full access is available, continue through the governed automatic repair or reinstall path instead of stopping at diagnosis alone.
  • For Claude Code or another compatibility host, keep the fallback wording short and host-generic; do not expand it into a second native bootstrap story.
  • Deterministic shell setup steps may run as background or main-agent commands, but the final environment judgment returns to the main agent.

Completion Signal

  • The workflow is complete when prepare and follow-up readiness checks leave the workspace ready, or when an actionable environment blocker has been surfaced to the main agent.

Notes

  • prepare bootstraps repo-local state only.
  • ./scripts/bootstrap-workspace.sh --yes is the preferred zero-to-working launcher from a raw checkout because it can prepare .venv before the package is importable from the src/ layout.
  • The launcher now performs governed preflight first, then probes bootstrap-Python liveness in bounded time and prefers repo-local candidates before shared ones.
  • The launcher and prepare now trust real LibreOffice smoke conversion, not only soffice --version, before declaring an Office-rendering machine baseline ready.
  • runtime/bootstrap_state.json is the cached ready marker that ordinary ask-time work should reuse.
  • The steady-state runtime is repo-local managed Python 3.13 under .docmason/toolchain/python/.
  • On the native Codex path, bootstrap should refresh repo-local skill shims under .agents/skills/ rather than writing into ~/.codex/skills.
  • prepare may use shared/system Python only as a bootstrap or repair helper; ordinary steady-state commands should not depend on it.
  • When uv is missing, prepare should provision the repo-local bootstrap helper venv under .docmason/toolchain/bootstrap/venv and install uv there.
  • On the native macOS path, ordinary cold starts should prefer the controlled UV bootstrap asset path first, use repo-local cache in Codex Default permissions, and auto-attempt only the real missing dependency installs when host access allows it.
  • Homebrew is optional. If it is already on PATH, DocMason may use it as a convenience backend, but DocMason should not spend time installing or preparing Homebrew itself.
  • After preparation, prefer ./.venv/bin/python -m docmason ... or the CLI installed inside .venv for ordinary workspace operations.
  • For Office rendering, DocMason detects the standard macOS soffice path inside /Applications/LibreOffice.app/Contents/MacOS/soffice, so shell-profile changes are usually unnecessary.
  • Not every Codex-first first-answer path requires sync-adapters before work can proceed.
  • Avoid shell-profile mutation unless it is clearly required and explicitly explained to the user.
  • Do not silently upgrade the host from Codex Default permissions to Full access; explain that boundary explicitly.

© 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-bootstrap of JetXu-LLM/DocMason.

  • SKILL.md
  • workflow.json

Open the folder on GitHubat commit 362417b

Compare with similar skills

Workspace Bootstrap 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 Bootstrap compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workspace Bootstrap this skillJetXu-LLM/DocMason147—~2.1kAutomated 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
Capture Conversationoutline/outline41k—~474Automated safety check: PassCustom licence

Similar skills

  • Logseq Review Workflow Eval

    logseq/logseq

    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

  • 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

  • Karpathy LLM Wiki

    Astro-Han/karpathy-llm-wiki

    A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.

    2.4k GitHub stars~3.6k tokensUpdated 2 mo ago
    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 9 days ago
    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 9 days ago
    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 9 days ago
    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 9 days ago
    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 9 days ago
    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 9 days ago
    Auto-check passed

Categories

Questions about Workspace Bootstrap

What does Workspace Bootstrap do?

Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state. Workspace Bootstrap is an agent skill from JetXu-LLM/DocMason. Prepare a DocMason repository for local operation by bootstrapping the environment, creating required directories, and recording runtime state.

When should I use Workspace Bootstrap?

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

How do I install Workspace Bootstrap in Claude Code?

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

How do I install Workspace Bootstrap in Codex?

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

Can I use Workspace Bootstrap 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-bootstrap -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-bootstrap, .gemini/skills/workspace-bootstrap, .github/skills/workspace-bootstrap and .opencode/skills/workspace-bootstrap in your project.

What does Workspace Bootstrap need to run?

Going by SKILL.md and its folder, Workspace Bootstrap needs the command-line tools its instructions call (python, brew and soffice). Our summary lists: Python 3.

Does Workspace Bootstrap 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 Bootstrap 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 Bootstrap use?

Workspace Bootstrap 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 Bootstrap use?

About 2.1k tokens (SKILL.md is roughly 8.3k 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 Bootstrap?

Skills that share tags, products or a category with Workspace Bootstrap: 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 Bootstrap?

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 September 30, 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.