persops-install-skills

Add or update agent skills in ~/p/persops, including vendoring upstream skills into modules/ai/skills, choosing the right propagation profile (`all`, `coding`, `claw`, `codex`), updating metadata, and applying local+remote Nix switches. Use when the user asks to add a skill, install a skill, update a skill, make a coding skill, make a Codex-only skill, or make a claw/openclaw/clawdbot-only skill in persops.

Jump to install

Repository: ci/persops
Last source activity: August 23, 2026 at 01:48
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ci/persops --skill persops-install-skills

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

3 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

deploying-persops

Deploys persops configurations to aglaea and amalthea. Use when asked to build, apply, switch, or deploy persops locally or through an Amp runner.

2026-08-23

install-anti-slop

Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.

2026-08-23

jjpr

Manage stacked pull requests with jjpr in Jujutsu repositories.

2026-08-22

View all from this repository

Persops Install Skills

Use this workflow for skills managed in ~/p/persops/modules/ai/skills.

Profile Mapping

Default to all: publish to .claude/skills, .agents/skills, .openclaw/skills, and .pi/agent/skills.

Use coding: publish to .claude/skills, .agents/skills, and .pi/agent/skills only.

Use claw: publish to .openclaw/skills only.

Use codex: publish to .agents/skills only.

Interpret claw skill, openclaw skill, or clawdbot skill as claw.

Workflow

Start with jj status, then inspect modules/ai/home.nix, modules/ai/skill-overrides.json, and any existing skill directory you might touch.

For new upstream skills, run modules/ai/scripts/add-skill.sh [--profile <all|coding|claw|codex>] <source> [skills-add args...].

Example: modules/ai/scripts/add-skill.sh https://github.com/vercel-labs/skills --skill find-skills
Direct GitHub blob / tree skill URLs work too; the helper infers the single skill name and vendors only that skill.

Review the vendored files under modules/ai/skills/<name>/. Keep repo-owned truth there and verify UPSTREAM.txt.

If the profile is not default all, update modules/ai/skill-overrides.json. Use it for coding, claw, codex, or other per-skill exceptions like recursive = true.

If you create or update a repo-local skill, keep SKILL.md concise, keep agents/openai.yaml aligned, and validate the skill with uv run --with pyyaml python3 /Users/cat/.codex/skills/.system/skill-creator/scripts/quick_validate.py <skill-dir>.

Run make deploy to apply the skill to every target reachable from the current controller.

Verify the expected symlinks locally and on amalthea:

~/.claude/skills/<name> when profile includes Claude
~/.agents/skills/<name> when profile includes Codex/Agents
~/.openclaw/skills/<name> when profile includes Claw
~/.pi/agent/skills/<name> when profile includes Pi

Commit changes at the end after verification. Use a Conventional Commit. Do not push unless the user asks.

Notes

make deploy snapshots a path: flake so freshly added uncommitted skill files are included consistently on every selected target.

Do a quick upstream health check before vendoring external skills, for example gh repo view <owner/repo> --json pushedAt,stargazerCount,url.

If the user asks for claw-only propagation, do not also wire Claude or Codex.