cds-new-workspace 100/100

Is cds-new-workspace safe to install?

SaferSkills independently audited cds-new-workspace (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

vendor/cds-workflow/skills/cds-new-workspace/SKILL.md · 1 file

vendor/cds-workflow/skills/cds-new-workspace/SKILL.md1.8 KB · Markdown

name: cds-new-workspace

description: "Create an isolated workspace with repo copies and independent .planning/"

argument-hint: "--name <name> [--repos repo1,repo2] [--path /target] [--strategy worktree|clone] [--branch name] [--auto]"

allowed-tools:

- Read

- Bash

- Write

- AskUserQuestion

<context> Flags:

--name (required) — Workspace name
--repos — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd
--path — Target directory. Defaults to ~/cds-workspaces/<name>
--strategy — worktree (default, lightweight) or clone (fully independent)
--branch — Branch to checkout. Defaults to workspace/<name>
--auto — Skip interactive questions, use defaults

</context>

<objective> Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent .planning/ directory for isolated GSD sessions.

Use cases:

Multi-repo orchestration: work on a subset of repos in parallel with isolated GSD state
Feature branch isolation: create a worktree of the current repo with its own .planning/

Creates:

<path>/WORKSPACE.md — workspace manifest
<path>/.planning/ — independent planning directory
<path>/<repo>/ — git worktree or clone for each specified repo

After this command: cd into the workspace and run /cds-new-project to initialize GSD. </objective>

<execution_context> @$HOME/.claude/cds-workflow/workflows/new-workspace.md @$HOME/.claude/cds-workflow/references/ui-brand.md </execution_context>

<process> Execute the new-workspace workflow from @$HOME/.claude/cds-workflow/workflows/new-workspace.md end-to-end. Preserve all workflow gates (validation, approvals, commits, routing). </process>

cds-new-workspace— agent skill

Is cds-new-workspace safe to install?

Audit the pieces. Scan the whole. Decide.