Skip to content
Back to skills

Setup All

ASecurity

Run all project setup steps in sequence — scaffold project-context.json and set up rules-ex infrastructure.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
development

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add atman-33/workhub --skill setup-all --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Setup All?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Setup All
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/atman-33-setup-all/badge)](https://www.skillsdirectory.com/skills/atman-33-setup-all)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: setup-all
description: Run all project setup steps in sequence — scaffold project-context.json and set up rules-ex infrastructure.
disable-model-invocation: true
allowed-tools: Read Write Skill
---

Run all project setup steps in sequence. Each phase is independent — a failure in one phase is reported and the next phase continues.

Both phases scaffold files that only the `workhub` plugin's harness hooks
read (`inject-project-context`, `inject-extended-rules`), so the skills that own
those templates live in that plugin. This skill delegates to them rather than
carrying its own copies — one template, one owner.

---

## Phase 1 — Scaffold project-context.json

1. Invoke the `workhub:setup-project-context` skill and let it do the work.
   - If the skill is unavailable (the `workhub` plugin is not installed), skip
     this phase and report that `.claude/project-context.json` was not
     scaffolded, naming the plugin the user has to enable.

---

## Phase 2 — Scaffold rules-ex infrastructure

2. Invoke the `workhub:setup-rules-ex` skill and let it do the work.
   - If the skill is unavailable (the `workhub` plugin is not installed), skip
     this phase and report that `.claude/rules/rules-ex-authoring.md` and
     `.claude/rules-ex/README.md` were not scaffolded, naming the plugin the
     user has to enable.

---

## Output Format

After both phases complete, print a summary table:

| Phase | Status | Notes |
|-------|--------|-------|
| 1 — project-context.json | ✓ / ✗ / skipped | created / already existed / `workhub` not installed |
| 2 — rules-ex infrastructure | ✓ / ✗ / skipped | created / already existed (per file) / `workhub` not installed |

Then remind the user:
- Edit the placeholder paths in `.claude/project-context.json` before starting a new session.
- Changes to `project-context.json` take effect on the next session start (not `/reload-plugins`).
- Use absolute paths matching your environment (Windows: `C:/repos/...`, WSL: `/mnt/c/repos/...`).
- Add cross-cutting rules as `*.md` files under `.claude/rules-ex/` — each must have a `paths:` front matter.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.