Skip to content
Skills Library
AI & agents · Tool integration

setup

/setup

Use when the person asks you to set up Ork, install it, or get started with it in a repository - checking it's installed, setting up the project, making Ork's tools available to you, and a first workflow.

Repository
ork ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the person asks you to set up Ork, install it, or get started with it in a repository - checking it's installed, setting up the project, making Ork's tools available to you, and a first workflow.

Triggers from the description

s installed, setting up the project, making Ork
Original author description

Use when the person asks you to set up Ork, install it, or get started with it in a repository - checking it's installed, setting up the project, making Ork's tools available to you, and a first workflow.

How it works

  1. 1. Check
  2. 2. The project
  3. 3. Make Ork available to you
  4. 4. A first workflow
  5. 5. Show them ork ui
  6. Never
Original SKILL.md headings · 89 lines, 585 words
SKILL.md preview
---
name: setup
description: Use when the person asks you to set up Ork, install it, or get started with it in a repository - checking it's installed, setting up the project, making Ork's tools available to you, and a first workflow.
---

# Setting up Ork

Ork runs workflows on the person's machine with their own accounts. Setting it
up changes their machine and their repository, so say what each step does and
ask before it. Work through these in order, and stop where they say no.

## 1. Check

```sh
ork --version
ork doctor
```

- **No `ork`:** it needs Node 24.20 or later (`node --version`). The install is
  `npm install --global @krapht/ork`; show it and run it only when they say
  yes. The guide:
  https://github.com/mimshins/ork/blob/main/docs/getting-started/installation.md
- **Read `ork doctor` to them.** It needs git, a git repository with a commit,
  and one agent driver. Don't run `git init` or a commit without asking.
- **A driver not ready:** they log in themselves, with `claude auth login`, or
  by setting `ANTHROPIC_API_KEY` or a cloud provider in their own shell (either
  makes the claude-code driver ready). Never ask for a key, never take one pasted to you, and
  never write one into a file or a command. `gh` and `aws` are optional, and
  their logins are their own too (`gh auth login`, `aws sso login`).

## 2. The project

- **`ork init`** keeps Ork's files in the repository, in `.ork/`, committed with
  the code. It adds `.ork/runs/` to `.gitignore`, links `.claude/` and similar
  folders to `.ork/`, and writes a starter workflow, `hello`.
- **`ork register`** keeps them beside it, in `~/.ork/projects/<id>/`, and
  writes nothing into the repository. For a repository whose process isn't
  theirs to change, or to try Ork first.

Explain both and ask which. Skip the question when the repository decides it: a
`.ork/` folder means `ork init` has run (`ork projects` lists what's
registered). Neither overwrites a file.

## 3. Make Ork available to you

If Ork's tools (`workflows`, `check`) already answer you, skip this. Otherwise,
by where you run, and asking before each change to a config:

- **Claude Code:** Ork's plugin brings the skills and the tools. The person
  types these themselves:

  ```
  /plugin marketplace add mimshins/ork
  /plugin install ork@ork
  ```

  Or, in a project set up with `ork init`, the skills in the repository for
  everyone who clones it, then the tools:

  ```sh
  ork init --skills
  claude mcp add ork -- ork mcp
  ```

  New tools start when they restart Claude Code or reconnect `ork` in `/mcp`;
  so does the plugin's, once `ork` is installed.

- **Another MCP client:** add a server named `ork` with command `ork` and args
  `["mcp"]` to its MCP config, where its own docs say. Its tools find the
  project by its id, from `ork projects`.
- **A shell only:** use the CLI. `ork --help` and each command's `--help` say
  what it takes.

## 4. A first workflow

Offer to write one for a task they name. Follow `/ork:write`, check each draft
(the `check` tool, or `ork validate <file>`) until it has no error, then save
it. Don't start it: a run spends their money. Start it only when they say so,
in the background with its inputs (`start_run`, or
`ork run <name> --detach --input name=value`), and follow it with `/ork:run`.

## 5. Show them `ork ui`

Tell them to run `ork ui` in their own terminal: their runs, graphs and logs in
the browser, and where they answer what a run asks.

## Never

- Ask for, store or pass on a password, key or token.
- Answer a run's decision: they answer in `ork ui` or with `ork decide` in
  their own terminal.
- Install, edit a config, or start a run without a yes.

Versions

RepositoryScoreLicence
This page · mimshins/ork100MIT
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version fb90b41ea29b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100write
    Use when writing or changing an Ork workflow (a `.ork/workflows/*.ork.yaml` file) - its nodes, edges, conditions and loops - and checking each draft until Ork accepts it.
  • 100principles
    Use when deciding how to split work into an Ork workflow - which steps are programs, which are Claude sessions, where a person decides - so it costs less than doing it by hand and can't go wrong quietly.
  • 100implement
    Full-power feature implementation using parallel subagents for backend, frontend, testing, and security, with worktree isolation and quality verification in one workflow. Chains with /ork:cover for tests and /ork:verify for validation. Use when asked to build, add, create,…
  • 100design-ship
    One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all…
  • 90workflow-setup
    Use when the user runs /workflow-setup or asks to set up, install or configure sams-agentic-workflow globally or for a project. "/workflow-setup" is the guided standard setup; "/workflow-setup full" lists every setting at the global and project layers to turn on or off. Also…
  • 100setup-project
    When setting up agentskel on a new project that does not yet have .memory/ or .agents/. Use when the user says "set up agentskel", "install agentskel", or "add agent memory to this project".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.