agentleFS
noahcostakesnoahcostakes/claudebrain-template/.claude/skills/workspace/SKILL.md

workspace

Skill0 starsChanged 5 months agoMITView on GitHub

Scaffold a nested Claude Code workspace in 15-workspaces/<slug>/ with its own CLAUDE.md, _meta/, .claude/ (including a pre-seeded /status starter skill), and an optional Notion project page. Use when a project warrants its own custom Claude environment.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use schedule, improve and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bivexSkill

    schedule

    Управление расписанием занятий с специалистами по самосовершенствованию. Используй когда пользователь спрашивает о расписании, хочет добавить/удалить/перенести занятие, посмотреть план на день или неделю.

    Also in 3 projects that use this

  • AnasX7Skill

    improve

    Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

    Also in 3 projects that use this

  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 3 projects that use this

  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 2 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run all 7 wizard questions.

    line 24
  2. Very specific:

    Check 15-workspaces/<slug>/ does NOT exist.

    line 28
  3. Very specific:

    Read templates/workspace-claude-md.md.

    line 42
  4. Very specific:

    Read templates/workspace-readme.md.

    line 44
  5. Very specific:

    If wizard answer 6 was y, write 15-workspaces/<slug>/_meta/people.md:

    line 64
  6. Very specific:

    Read templates/workspace-settings.json.

    line 89
  7. Very specific:

    If the Notion MCP is not connected, skip this step (treat as none).

    line 99
  8. Very specific:

    Orient update: ask: *"Add to vault _meta/orient.md under Active projects (tagged [workspace])?

    line 111
  9. Distinctive:

    Never overwrite an existing folder.

    line 129
  10. Very specific:

    Use [[wikilinks]] throughout.

    line 132

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workspace Skill

What this does

Runs a 7-question wizard, then scaffolds a complete nested Claude Code workspace at 15-workspaces/<slug>/. The workspace inherits vault context (vault CLAUDE.md, vault skills) and adds its own scoped layer (CLAUDE.md, _meta/, .claude/skills/).

Wizard questions (ask one at a time)

  1. Workspace name (human-readable).
  2. One-liner: what is this workspace?
  3. Primary goal.
  4. Expected duration (days / weeks / months / open-ended).
  5. Related vault area (validate against 20-areas/; allow "—").
  6. Will this workspace have its own people-graph? (y/n — if y, create _meta/people.md in the workspace; if n, omit.)
  7. Notion side? (page / none) — only meaningful if the Notion MCP is connected; otherwise answer none. A full "project space" with a child Tasks DB is deferred; you create the Tasks DB manually afterward if needed.

Steps

  1. Run all 7 wizard questions. Store answers.
  2. Slugify name → <slug>. Confirm with user.
  3. Check 15-workspaces/<slug>/ does NOT exist. If it exists, report and stop.
  4. Create directory tree:
    15-workspaces/<slug>/
    ├── _meta/
    ├── notes/                  (with .gitkeep)
    └── .claude/
        ├── skills/
        │   └── status/
        ├── agents/             (with .gitkeep)
        └── hooks/              (with .gitkeep)
  5. Read templates/workspace-claude-md.md. Substitute placeholders. Write to 15-workspaces/<slug>/CLAUDE.md.
  6. Read templates/workspace-readme.md. Substitute. Write to 15-workspaces/<slug>/README.md.
  7. Write 15-workspaces/<slug>/status.md:
    ---
    type: status
    date: <today>
    tags: [status, workspace]
    workspace: <slug>
    ---
    
    # Status — <name>
  8. Read templates/workspace-orient.md. Substitute. Write to 15-workspaces/<slug>/_meta/orient.md.
  9. Read templates/workspace-memory.md. Substitute. Write to 15-workspaces/<slug>/_meta/memory.md.
  10. Read templates/workspace-decisions.md. Substitute. Write to 15-workspaces/<slug>/_meta/decisions.md.
  11. If wizard answer 6 was y, write 15-workspaces/<slug>/_meta/people.md:
    ---
    type: meta
    status: living-document
    last-updated: <today>
    tags: [meta, people, workspace]
    workspace: <slug>
    ---
    
    # <name> — People
    
    > [!info] Workspace-specific people
    > Vault-wide people live in vault root `_meta/people.md`. This file is for people relevant ONLY to this workspace.
    
    ## Active contributors
    -
    
    ## Stakeholders
    -
    
    ## External contacts
    -
  12. Read templates/workspace-settings.json. Write verbatim to 15-workspaces/<slug>/.claude/settings.json.
  13. Write 15-workspaces/<slug>/.claude/settings.local.json:
    {}
  14. Read templates/workspace-starter-skill-status.md. Write verbatim to 15-workspaces/<slug>/.claude/skills/status/SKILL.md.
  15. Notion handoff (OPTIONAL — only if the Notion MCP is connected; use wizard answer 7):
    • If the Notion MCP is not connected, skip this step (treat as none).
    • page: discover Notion Projects database via mcp__claude_ai_Notion__notion-search. Show always-confirm preview:
      Create in Notion → [Projects DB]:
        Name:          <name>
        One-liner:     <answer 2>
        Type:          workspace
      Confirm? (y/n)
      On y: create via mcp__claude_ai_Notion__notion-create-pages. Paste URL into the workspace README's "Workspace-specific Notion" section.
    • none: skip.
  16. Orient update: ask: "Add to vault _meta/orient.md under Active projects (tagged [workspace])? (y/n)"
    • On y: append - **<name>** [workspace] — <answer 2> to the Active projects list. Update last-updated:.
    • On n: skip.
  17. Final message (exact wording):
    Workspace ready at 15-workspaces/<slug>/.
    
    To activate scoped context: open a new terminal, cd into the workspace,
    and start Claude Code from there. The workspace inherits vault skills
    automatically. Project-specific skills you add to .claude/skills/ will
    register on next session.
    
    Try the starter skill: /status (inside the workspace).

Rules

  • Never overwrite an existing folder.
  • Notion is OPTIONAL — skip cleanly if the MCP isn't connected; when it is, the write confirms separately from the wizard.
  • Vault orient.md update confirms separately.
  • Use [[wikilinks]] throughout. Frontmatter related: field must be a YAML list of wikilinks.
  • Workspace _meta/ minimum: orient + memory + decisions. People.md is conditional on answer 6.
  • All .gitkeep files exist so empty directories survive git add.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.