Skip to content

inprealpha/inprealpha-agent-skills

v1.0.0

Personal workflows for engineering, review, investigation, verification, and craft.

architect

Design caller usage, interfaces, data types, and module ownership before implementing a change.

blast-radius

Assess what a change could break beyond its diff and test the assumptions its safety depends on.

craft

Simplify writing, documentation, code, architecture, interfaces, and creative work so people can quickly understand and use it. Use for “AI slop,” confusing or overcomplicated output, project reviews, and making the current result ready to share or ship. Not an AI detector.

create-verification-skill

Create executable project verification instructions with a feature map and retained evidence.

hillclimb

Improve one measurable outcome through isolated hypotheses, repeated measurements, and regression checks.

how

Explain a subsystem through traced runtime flow, data ownership, and concrete code references.

interrogate

Adversarially review a change and deliver a prioritized verdict grounded in reachable failures.

maintain-verification-skill

Audit a project verification skill against current source and observed application behavior.

orchestrate-work

Coordinate substantial work with ownership suited to the task, parallel execution, and fresh perspectives. Use for broad ambiguous goals, separable workstreams, or requested team workflows.

reflect

Extract durable lessons from a work session and route them to focused skill or tooling improvements.

review-loop

Finish work through repeated fresh-context reviews and fixes. Use when the user wants an autonomous review loop after a brief alignment on the outcome and review perspectives.

simplify-code

Simplify code when asked to review over-engineering or apply cleanup, including redundant tests and avoidable dependencies. Preserve behavior; keep unrelated feature work and general correctness reviews outside this skill's scope.

skill-evaluation

Compare skill variants on realistic tasks with controlled inputs and evidence-based scoring.

why

Investigate the history and rationale behind code, with cited facts and explicit uncertainty.