cds-from-gsd2 100/100 — SaferSkills

Is cds-from-gsd2 safe to install?

SaferSkills independently audited cds-from-gsd2 (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-from-gsd2/SKILL.md · 1 file

vendor/cds-workflow/skills/cds-from-gsd2/SKILL.md1.8 KB · Markdown

name: cds-from-gsd2

description: "Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format"

argument-hint: "[--path <dir>] [--force]"

allowed-tools:

- Read

- Write

- Bash

<objective> Reverse-migrate a GSD-2 project (.gsd/ directory) back to GSD v1 (.planning/) format.

Maps the GSD-2 hierarchy (Milestone → Slice → Task) to the GSD v1 hierarchy (Milestone sections in ROADMAP.md → Phase → Plan), preserving completion state, research files, and summaries. </objective>

Locate the .gsd/ directory — check the current working directory (or --path argument):

   node "$HOME/.claude/cds-workflow/bin/gsd-tools.cjs" from-gsd2 --dry-run

If no .gsd/ is found, report the error and stop.

Show the dry-run preview — present the full file list and migration statistics to the user. Ask for confirmation before writing anything.

Run the migration after confirmation:

   node "$HOME/.claude/cds-workflow/bin/gsd-tools.cjs" from-gsd2

Use --force if .planning/ already exists and the user has confirmed overwrite.

Report the result — show the filesWritten count, planningDir path, and the preview summary.

</process>

<notes>

The migration is non-destructive: .gsd/ is never modified or removed.
Pass --path <dir> to migrate a project at a different path than the current directory.
Slices are numbered sequentially across all milestones (M001/S01 → phase 01, M001/S02 → phase 02, M002/S01 → phase 03, etc.).
Tasks within each slice become plans (T01 → plan 01, T02 → plan 02, etc.).
Completed slices and tasks carry their done state into ROADMAP.md checkboxes and SUMMARY.md files.
GSD-2 cost/token ledger, database state, and VS Code extension state cannot be migrated.

</notes>

cds-from-gsd2— agent skill

Is cds-from-gsd2 safe to install?

Audit the pieces. Scan the whole. Decide.