Vault

Practical agent workflows, skills, and small helpers I actually use.

This repo is the canonical home for my public-facing agent material:

• skills/: reusable agent skills
• scripts/: small validation and listing helpers
• docs/: notes about the repo's philosophy and conventions
• AGENTS.md: repo-local instructions for agents working here

The goal is not to collect every prompt. The goal is to keep useful workflows small, inspectable, reusable, and grounded in real sessions.

Quickstart

List available skills:

scripts/list-skills

Validate skill frontmatter:

scripts/validate-skills

Install a skill into local Codex:

scripts/install-codex-skill career-profile-overhaul

Install all skills into local Codex:

scripts/install-all-codex-skills

Skills

Skills live under category folders:

skills/<category>/<skill-name>/SKILL.md

Current skills:

• career-profile-overhaul — Human-in-loop LinkedIn and CV overhaul workflow.
• code-simplifier — Behavior-preserving anti-slop implementation cleanup.
• slopper — Read-only docs/code drift and cleanup-candidate audit.
• surface-proof — Prove browser-visible changes with real targets, snapshots, and flow receipts.
• session-bootstrap — Start a repo session by reading maps, task truth, and relevant context.
• session-closeout — End work with verification, git, docs, task, coordination, and commit-note receipts.

Install

Install a selected skill into:

~/.codex/skills/

Example:

scripts/install-codex-skill career-profile-overhaul

The installer copies the skill folder by name. It does not symlink, so local Codex usage stays stable even while this repo changes.

For manual install, copy a skill folder into:

~/.codex/skills/

For Claude-style plugin use, see:

.claude-plugin/plugin.json

Inspiration

The repo shape is inspired by public agent-skill repositories such as steipete/agent-scripts and mattpocock/skills. The skills here are my own workflows, distilled from real sessions.

Hooks

Optional local pre-commit hook:

git config core.hooksPath hooks

This runs scripts/validate-skills before commits.

Principles

• Keep skill descriptions short and useful for routing.
• Keep SKILL.md operational; move heavier detail into references.
• Prefer real folders first. Add symlinks/install machinery only when needed.
• Validate after editing skills.
• Public copy should be useful without exposing private session context.

More detail: Skill Conventions.