Skip to content
Skills Library
Programming · Automation

refactory-install

/refactory-install

Use this skill to materialize the refactory runtime into a repo by creating `.refactor/` and `.startup/`, copying the runtime scripts, writing the local install/troubleshooting guide, and verifying startup output and preflight.

Licence
MIT
Last repository change
17.10.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
0
Deprecation

No signals detected. Repository changed on 17.10.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 this skill to materialize the refactory runtime into a repo by creating `.refactor/` and `.startup/`, copying the runtime scripts, writing the local install/troubleshooting guide, and verifying startup output and preflight.

Original author description

Use this skill to materialize the refactory runtime into a repo by creating `.refactor/` and `.startup/`, copying the runtime scripts, writing the local install/troubleshooting guide, and verifying startup output and preflight.

How it works

  1. What This Installs
  2. Installation Preconditions
  3. How To Invoke
  4. What The Installer Must Do
  5. Expected Result
  6. Verification Checklist
  7. Failure Handling
  8. Safety
Original SKILL.md headings · 99 lines, 384 words
SKILL.md preview
---
name: refactory-install
version: 0.2.0
description: >
  Use this skill to materialize the refactory runtime into a repo by creating
  `.refactor/` and `.startup/`, copying the runtime scripts, writing the local
  install/troubleshooting guide, and verifying startup output and preflight.
---

# Refactory Install

Use this skill after the policy design is stable enough to bootstrap a repo.

## What This Installs

- `.refactor/docs/`
- `.refactor/rules/`
- `.refactor/profiles/`
- `.refactor/scripts/`
- `.refactor/reports/`
- `.refactor/db/`
- `.refactor/logs/`
- `.refactor/temp/`
- `.startup/team-lead`

The runtime scripts are copied from the installed package scripts into the
repo-local `.refactor/scripts/` folder.

## Installation Preconditions

Before running the installer, confirm:

- the repo root is known
- the rule design is stable enough to define runtime layout
- `oxigraph` is installed from crates.io or the user accepts installer guidance
- the repo should receive a local-only install

## How To Invoke

Resolve the installed package script from the local repo first, then fall back
to the global install if needed.

Local-first pattern:

```bash
repo_root="$(git rev-parse --show-toplevel)"

if [ -f "$repo_root/.claude/scripts/install_refactory.py" ]; then
  python3 "$repo_root/.claude/scripts/install_refactory.py" --repo-root "$repo_root"
else
  python3 "$HOME/.claude/scripts/install_refactory.py" --repo-root "$repo_root"
fi
```

Optional flags:

- `--force` to refresh runtime-managed files
- `--seed empty` for runtime only
- `--seed templates` to include starter rule templates

## What The Installer Must Do

1. Resolve the target repo root.
2. Create `.refactor/` directories.
3. Create `.startup/team-lead`.
4. Copy runtime scripts into `.refactor/scripts/`.
5. Write `.refactor/.gitignore`.
6. Write `.refactor/docs/install-and-troubleshooting.md`.
7. Optionally install starter templates.
8. Render a startup preview.

## Expected Result

- `.refactor/.gitignore` ignores `db/`, `logs/`, and `temp/`
- `.startup/team-lead` exists
- `.refactor/scripts/session_start.py` exists
- `.refactor/docs/install-and-troubleshooting.md` exists
- `python3 .refactor/scripts/preflight.py --skill refactor-lookup` prints
  `oxigraph v ... checks pass` when the environment is healthy

## Verification Checklist

After installation, verify:

1. `.startup/team-lead` executes without traceback
2. `python3 .refactor/scripts/session_start.py --mode startup` prints a trigger
   block or `(no triggers registered yet)`
3. `python3 .refactor/scripts/preflight.py --skill refactor-lookup` succeeds
   when the runtime is healthy
4. `.refactor/db/`, `.refactor/logs/`, and `.refactor/temp/` are ignored by
   `.refactor/.gitignore`

## Failure Handling

- If `oxigraph` is missing, surface the install guidance and stop.
- If the repo already contains user-authored rules or docs, do not overwrite
  them unless `--force` or explicit approval says to do so.
- If startup preview fails, keep the installed files but report the exact stage
  that failed.

## Safety

- Do not overwrite existing rule docs or TTL files unless the user asked for it.
- Runtime scripts may be refreshed during reinstall.
- The installer should be deterministic and low freedom.
- Treat `.refactor/docs/` and `.refactor/rules/` as user-owned content.

Versions

The database has no other skills named refactory-install.

Database snapshot: 13.11.2026 · package version 3755434f6814 (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

  • 100refactory-design
    Use this skill to design a constrained refactoring system before any package or runtime is built. It walks through approved-rule design, trigger and sample-fix guidelines, startup authorization policy, named-teammate responsibilities, QA gating, and package/runtime layout.
  • 90vrm-sandbox-startup-acceptance
    Validate and repair VRM Sandbox startup acceptance with shim-first local model authority, frontend/backend bring-up, and avatar-runtime launch proof. Use when launch behavior, chat handoff, voice fallback, or runtime bridge acceptance must be verified end to end.
  • 100materialize
    Install or upgrade a project's harness by completely replacing its harness-owned runtime with the current /harness. Auto-detects the stack (Go, Java Spring Boot, or the generic fallback) from the build marker, scaffolds project-owned files via /init when they are missing,…
  • 100install-opendirector
    Install OpenDirector from source on the current machine. Detect the platform, check and install missing prerequisites, prepare project dependencies, build the application, verify startup, and provide platform-specific launch commands. Use for first installation or repairing an…

Feedback and reports

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