aictrl.dev engineering skills and plugin

Essential, vendor-neutral AI engineering-workflow skills in one canonical tree. Install the skills alone, or install the aictrl.dev plugin to add the same skills plus OAuth-connected controlled workflow execution.

Install

Skills only — Codex, Claude Code, OpenCode, and compatible agents

npx skills add aictrl-dev/skills

Claude Code plugin

/plugin marketplace add aictrl-dev/skills
/plugin install aictrl@aictrl-public

Codex plugin

codex plugin marketplace add aictrl-dev/skills --ref main
codex plugin add aictrl@aictrl-public

OpenCode plugin package

npx @aictrl/opencode@beta
opencode mcp auth aictrl

Cursor / direct OpenCode skills — skills use the cross-tool Agent Skills standard:

git clone https://github.com/aictrl-dev/skills && cd skills
./scripts/install.sh cursor       # or: opencode | all

…or copy skills/* into your tool's skills dir (~/.cursor/skills, ~/.config/opencode/skills).

Then ask for the task naturally or invoke a supported slash command, for example /create-issue, /implement-code-change, /code-review, or /create-workflow.

The Skills

Skill	What it does	Try it
create-issue	Vague feature or chore → code-grounded issue with scope, acceptance criteria, tests, risks, and open questions.	/create-issue
create-bug	Symptoms or regression → reproducible, evidence-backed bug and regression-test requirement.	/create-bug
spec-review	Issue/spec → repository-grounded readiness verdict and concrete gap fixes.	/spec-review
implement-code-change	Issue → tested, reviewed, merge-ready PR locally or through an optional connected workflow.	/implement-code-change
create-pr	Exact revision + evidence → concise reviewer-ready PR title and body, with rollout and verification claims kept honest.	/create-pr
code-review	Exact PR head → actionable correctness, security, reliability, and test findings; no code changes.	/code-review
judge-review-findings	Current-head findings → TRUE/FALSE/UNCERTAIN plus FIX/DEFER/IGNORE judgments.	/judge-review-findings
reply-to-code-review	Accepted review findings → fixes, verification, evidence-backed replies, and bounded re-review.	/reply-to-code-review
root-cause-analysis	Incident or recurring failure → evidence-driven causal analysis, sibling exposure map, and prevention portfolio.	/root-cause-analysis
create-workflow	Workflow intent → validated aictrl.dev workflow v2 YAML with portable inline task nodes.	/create-workflow
design-review	Drop an HTML mock or screenshot — get a sharp, located critique across IA, value prop, hierarchy, trust/friction, and a11y. Ends with "Fix these 3 first."	/design-review path/to/mock.html
measurement-plan	Feature → structured measurement plan: learning objectives, metrics table, product-analytics events, warehouse changes, event pipeline.	/measurement-plan
recording-product-demo	Point it at a repo with a web UI — it boots the app, preps demo data/auth, records a narrated time-locked Playwright demo synced to an ElevenLabs voiceover, and builds a publish kit (MP4 + captions + embed).	/recording-product-demo
explain-change	PR, commit range, or design document → a grounded technical explainer of the design, difficult trade-offs, and real rollout state.	/explain-change

design-review in action

Input: a SaaS landing page mock.

Value Proposition — WEAK
  Hero headline "Workflows made simple" says nothing about what the product does.
  Fix: replace with a one-liner that names the user, the problem, and the outcome.

Actionability — BROKEN
  Three competing CTAs above the fold (Start free, Book demo, Watch video).
  Fix: one primary CTA above the fold; demote the others below.

Every critique names the element. Every fix is concrete. No generic "improve clarity."

Why these exist

These skills are free and standalone. aictrl.dev adds controlled remote execution, approvals, policy, history, integrations, and cost limits. The first connected path is implement-code-change; local mode remains available for every launch skill.

The Claude, Codex, and OpenCode distributions in this repository all consume the root skills/ directory directly. There are no vendor-specific copies to repin or hand-edit. Connected execution always uses the aictrl MCP identity at https://aictrl.dev/mcp; OAuth is requested only when a connected workflow is used.

Contributing

PRs that add skills are welcome — see CONTRIBUTING.md. Release owners should also follow the public plugin release runbook.