QP Agent Skills

QP Agent Skills is a portable collection of focused skills for established codebases. It helps you make decisions, plan work, implement changes, review code, and craft portable HTML artifacts from durable records to interactive prototypes.

Skills are organized into exclusive Engineering, Design, Productivity, and Experimental source groups.

Browse the QP Agent Skills documentation.

Portfolio shape

• Skills belong to one Engineering, Design, Productivity, or Experimental source group, with interactive group selection during installation.
• Test-first delivery stays with Alaga, maintainability review stays with Pare, skill portfolio auditing stays with Ko Skill, and stateful refactor-parity auditing stays with Àtúnwò.
• Alaga handles bounded features and supplied build jobs through integration, proof, documentation, and applicable review.

Install

Install the QP skill portfolio globally:

npx skills add quantipixels/skills --global

Follow the Skills CLI prompts to choose skills and target agents. The command does not remove retired skills.

Install from a local checkout

npx skills add .

The local selection groups the portfolio under Qp Skills (qp-skills). Its Claude display name and repository identity remain quantipixels/skills.

Install in Claude Code

claude plugin marketplace add quantipixels/skills
claude plugin install qp-skills@qp-skills

Uninstall

Remove all globally installed QP skills:

curl -fsSL https://raw.githubusercontent.com/quantipixels/skills/ori/scripts/uninstall.sh | bash

Releases

Read the latest GitHub release and the repository changelog.

Start

Use Alarina when you need help to choose the right skill:

Use alarina to choose the right QP skill for this request:

[describe the outcome you need]

Engineering skills

Skill	Use when
alaga	test-first mode handles one bounded feature or fix; job mode handles a supplied build job through integration, acceptance, reconciliation, and applicable review
amose	Project terms, CONTEXT.md, domain rules, .learnings, .nongoals, or ADRs need clarification or reconciliation
atona	Architecture or migration work needs one live plan through delivery
atunwo	broad, defect-only, or read-only refactor-parity audit is needed in general local/supplied or provider PR/MR mode; broad review consumes Pare review evidence
irinse	A companion engineering tool needs selection, setup, safe use, or removal
ko-skill	Creates, revises, or validates one skill through one workflow; bounded portfolio audits remain read-only
pare	Read-only audit or review finds material simplifications and classifies implementation, dependency, support-artifact, and test cleanup candidates
se-triage	One issue or bug report needs supplied-evidence-first assessment before implementation
seda-pr	A bounded current-branch change needs commit, push, and a clear ready-for-review GitHub PR or GitLab MR
seda-ticket	Supplied work needs consumable vertical tickets with blockers, acceptance, and lifecycle state
seda-sigidi	An AI agent needs a named soul installed into the config its host loads, ported across hosts, or refreshed from evidence
wo-pr	An open PR or MR needs active CI and feedback stewardship through readiness and later changes until explicit stop or closure

Design skills

Use apere as the end-to-end router, or invoke the narrowest owner directly:

Skill	Use when
apere	A visual request spans specialists or needs its built-in logo, corporate identity program, icons, or social graphics mode
amoye-ui-ux	UI/UX recommendations need searchable styles, palettes, typography, accessibility, charts, or stack rules
brand	Brand voice, identity, assets, or consistency needs a source of truth
eto-apere	Tokens, CSS variables, component specs, or theme architecture need definition
asa-oju-ibanisoro	Components and responsive interfaces need accessible Tailwind/shadcn implementation, with an explicit UI-library choice
banner-design	Social, ad, web hero, cover, or print banners need exact platform constraints
slides	Presentations and pitch decks need narrative, layout, and chart guidance

For React UI work, asa-oju-ibanisoro asks for an explicit component-library decision and keeps the local 14-library inventory in skills/design/asa-oju-ibanisoro/references/ui-component-libraries.md.

Productivity skills

Skill	Use when
alarina	You need to choose the shortest QP route for a request
arojinle	A material plan or design needs a complete decision tree, durable records, and final confirmation
ayewo-igba-ise	A coding-agent session or bounded multi-session corpus needs an evidence-backed friction and recurrence analysis
handoff	A conversation needs a compact handoff for another agent or session
html-artifact	Supplied results, purpose-fit reports, analysis, data, decisions, or designs need a portable visual explanation for a zero-context reader
iwadi	A question needs high-trust research from primary sources, captured in a Markdown file
ro-wo	A material premise needs a brief evidence-backed check before agreement or disagreement
salaye	One user-supplied subject needs a plain-language explanation for a first-time reader
technical-writing	Developer documentation, technical communication, or applicable human-facing artifact copy needs layered structure and sentence-level clarity
yo-slop	Human- or agent-facing prose needs a final pass for AI tells, filler, vague abstraction, or instruction noise without changing meaning

Experimental skills

Experimental skills must be selected explicitly during installation.

Skill	Use when
pepeye	A task needs provider-neutral lifecycle control across QP-native playbooks, leaf owners, proof, pause or pickup, and final learning

Optional agent instructions

Add any of these snippets to your AGENTS.md, CLAUDE.md, or equivalent agent-instruction file.

Default Pepeye lifecycle mode

Copy the exact managed block from Pepeye portable activation into a supported global instruction file. This activates Pepeye as the task-wide controller when the host can expose the skill and current context. Explicit invocation remains the fallback. Pepeye selects and advances a playbook while leaf skills retain their specialist outcomes, procedures, and authority gates.

olofofo is retired and no longer published by this plugin. An installed copy can remain active until its host removes it. Replace an authorized Olofofo activation block through the migration branch in Pepeye portable activation; preserve existing reports and OGBON evidence.

Companion-tool routing

Use `irinse` when a companion tool could materially improve the result.

Technical writing and prose cleanup

Use `technical-writing` and `yo-slop` for communication.

Consider before judgment

Use `ro-wo` before agreeing or disagreeing with a material premise.