Skip to content

Repository files navigation

QP Agent Skills

Portable focused skills for established codebases. QP aims for one independently useful outcome per public skill, deep references where judgment benefits, native commands/tools for ordinary mechanics, and bundled code only for narrow deterministic kernels.

Browse the documentation.

Portfolio principles

  • Kọ Skill authors every capability/resource at the smallest adequate surface: guidance/reference → visible command → native/project/provider tool → focused library → deterministic script → engine only when it carries a substantial owned vertical.
  • Akọsílẹ̀ owns one repository-scoped .qp: the main worktree holds the real directory and linked worktrees expose symlinks. New records use stable semantic subjects; settings/index/record/artifact resources are created lazily.
  • Supporting skills keep detailed results with their native owners rather than copying caller-specific receipt/lifecycle schemas.
  • HTML Artifact creates reader-specific projections of supplied material without duplicating source archives or originating conclusions.
  • Generated .qp state stays outside Git by default.
  • Small public skills may intentionally exist as reusable model-steering contracts when a narrow named behavior saves users from restating longer instructions.
  • Thin public convenience entrypoints may wrap native commands when one safe memorable invocation materially improves installation, removal, or other human-facing distribution UX.
  • Experimental skills are explicit-only and do not replace stable owners.

Install

npx skills add quantipixels/skills --global

Local checkout:

npx skills add .

Claude Code:

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

Uninstall

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

The entrypoint removes only globally installed skills whose lock-file source is quantipixels/skills; unrelated installed skills remain untouched.

Repository-local workspace

.qp/
├── settings.json optional
├── INDEX.md optional generated navigation
├── records/<owner>/<stable-subject>/ created on first record
└── artifacts/<stable-subject>/ created on first standalone artifact

The real .qp belongs to the non-bare main worktree. Linked worktrees expose .qp as a symlink to it. Existing dated record/artifact directories remain valid legacy identities.

Engineering

SkillOutcome
akosileRepository-scoped .qp paths/worktrees, sparse settings, exact safe publication, generated index
alagaDeliver one supplied build job through implementation, proof, review, and handoff
amoseExact-current project/domain knowledge, .learnings, .nongoals, ADRs, local craft
atonaOne initiative plan from Draft through delivery/closure
atunwoCode defect/proof/state-parity review and provider review publication when authorized
hitl-reviewHuman-led walkthrough, review coverage, specialist discovery, final human decision
irinseSelect/ready/use/upgrade/remove one companion engineering tool and return bounded evidence
ko-skillAuthor/revise/validate one skill or audit a bounded portfolio
pareRead-only simplification audit/review
scope-guardPrevent coding scope drift and enforce the minimum sufficient mechanism/proof
se-triageSupplied-evidence-first issue/report assessment
seda-prScoped commit/push and PR/MR creation/update
seda-specConfirmed implementation-independent behavior specification
seda-ticketVertical delivery tickets with blockers/acceptance
seda-sigidiDraft or explicitly integrate one agent's durable identity/values/boundaries/voice into a known host configuration
solution-architectImplementation-ready technical architecture design/read-only review
wo-prSteward an open PR/MR through CI/conflict/feedback readiness

Design

Use the exact design specialist directly when one deliverable owner is clear. Use apere when design-specific multi-owner routing, prerequisites, dependency order, shared constraints, or approval boundaries are themselves needed.

SkillOutcome
apereRoute broad/multi-deliverable design work
amoye-ui-uxCoherent UI/UX direction/review from current product evidence + curated judgment
brandDurable brand voice/identity/logo/icon/assets source of truth
social-graphicsFeed/carousel/story/social campaign graphics
eto-apereProject-specific token/component-spec contract and CSS realization
asa-oju-ibanisoroAccessible responsive React/web UI implementation
banner-designCovers/headers/heroes/display ads/print banners
slidesPresentation/pitch-deck narrative and visual composition

Banner Design and Social Graphics intentionally remain narrow steering owners even though they share graphic-design fundamentals: the separate selectors encode different surface/adaptation behavior without requiring users to restate it.

Productivity

SkillOutcome
alarinaSelect the shortest route from currently available QP skill descriptions
arojinleResolve consequential product/plan/design choices through user-confirmed decision frontier
ayewo-igba-iseEvidence-backed coding-agent session/corpus retrospective
handoffCompact fresh-session handoff
html-artifactSelective traceable accessible HTML visualization of supplied material
iwadiHigh-trust primary-source research record
ro-woTest one material premise before judgment
salayeReusable plain-language explanation behavior for a supplied subject
system-cleanupSafe macOS storage audit, regenerable cleanup, worktree review, and external-drive offload
technical-writingTechnical communication structure/clarity
yo-slopFinal prose cleanup / explicit pruning without contract change

salaye is intentionally lightweight: its value is reliable reusable model steering, not hidden machinery.

Experimental

Experimental skills require explicit acceptance.

SkillOutcome
akoweExact-candidate adaptive expert implementation counsel
dogfoodReal-browser verification of changed user journeys
fihanServe one bounded local resource privately and return its exact HTTPS URL or Tailcat receiver invocation
ideateGrounded mechanism-diverse possibilities before selection
orisunExact-version upstream source grounding for one bounded technical question
pepeyeExplicit task supervision without a second owner lifecycle
prototypeDisposable truthful decision instrument
root-causeMinimal causal mechanism/set for an observed failure

Historical akowe-java, akowe-spring, and catalogue experiments are research evidence only; Adaptive Akọ̀wé does not load those fixed catalogues at runtime.

Start

Use alarina to choose the shortest QP route for this request:
[describe the outcome]

Releases

Packages

Contributors

Languages