new-worktree 100/100 — SaferSkills

Is new-worktree safe to install?

SaferSkills independently audited new-worktree (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.

src/klaussy/templates/skills/new-worktree/SKILL.md · 1 file

src/klaussy/templates/skills/new-worktree/SKILL.md1.7 KB · Markdown

name: {{REPO}}-new-worktree

description: Use when the user wants a new git worktree created for a task. Picks a kebab-case branch name with a fix/feat/chore/docs/refactor prefix, runs `git worktree add` from the configured base branch, and reports the new path.

allowed-tools: Read Bash(git worktree *) Bash(git branch *)

disable-model-invocation: true

Create a new git worktree for the task the user described.

Read CLAUDE.md to understand the project structure and branching conventions.
Create a short, descriptive branch name based on the task (e.g. fix/login-redirect, feat/add-search).
Run git worktree add ../$(basename $PWD)-<branch-name> -b <branch-name> {{BASE_BRANCH}} to create the worktree from the configured base branch (the trailing start-point keeps the new branch from inheriting whatever branch the user is currently checked out on).
Confirm the worktree was created successfully with git worktree list.
Tell the user the full path to the new worktree so they can open it.

Rules:

Always branch from {{BASE_BRANCH}} unless told otherwise.
Use lowercase kebab-case for branch names.
Prefix with fix/, feat/, chore/, docs/, or refactor/ as appropriate.
Do not start work in the worktree — just create it and report the path.

When NOT to use

The user just wants a new branch in the current working tree (git checkout -b) — worktrees are for parallel checkouts, not branch creation alone.
A worktree for the same branch already exists — surface the existing path; don't create a duplicate.
The user is on a non-worktree-friendly hosting setup (some submodule-heavy repos break with worktrees) — flag the risk before creating.

new-worktree— agent skill

Is new-worktree safe to install?

When NOT to use

Audit the pieces. Scan the whole. Decide.