Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

Using QuantEcon skills

For lecture authors, reviewers, and maintainers who want to use the skills. (Building new ones: Developing skills.)

Setup

In a lecture repo that has opted in — nothing to do. Repos that check the marketplace into .claude/settings.json (see the repo README) install everything automatically when you open the repo in Claude Code and trust it.

Anywhere else — two commands in a Claude Code session (the marketplace, then the one plugin):

/plugin marketplace add QuantEcon/skills
/plugin install qe@quantecon

/plugin is a terminal-CLI built-in, so the VS Code extension and the web app answer /plugin isn't available in this environment. The claude plugin CLI does the same job from any shell and works everywhere:

claude plugin marketplace add QuantEcon/skills
claude plugin install qe@quantecon

Either route, restart the session afterwards — plugins register at startup, so a newly installed skill is absent until you reopen. claude plugin list shows what is installed and at which version.

In CI — anthropics/claude-code-action@v1 accepts plugin_marketplaces and plugins inputs directly; see the repo README for the workflow snippet.

Invoking a skill

Two ways, equivalent:

  1. Slash command — type / and pick from the menu, e.g. /qe:benchmark 717. Trailing words are passed to the skill as arguments.

  2. Natural language — describe what you want (“work through Copilot’s review of this PR”; “is this JAX conversion actually an improvement?”) and the matching skill triggers on its description.

What to expect

The skills

Everything that registers in your slash menu — one plugin, five skills. Since qe 0.6.0 every entry is a skill that actually runs — an unbuilt skill lives only as the plan in its family’s tracking issue (the style-check family, for example, is skills#3). CATALOG.md is the stricter list: merged, operational, and stating how far each has been validated.

SkillWhat it doesStatus
/qe:copilot-reviewWork through GitHub Copilot’s review of a PR: a verdict and recommended fix per comment, then a threaded reply to each one so they can be resolved from the GitHub UIoperational, validated from an installed plugin 2026-08-03 — #26
/qe:workplan-project, /qe:workplanThe work-plan family: workplan-project turns an audit/review report into a tracking issue with linked sub-issues; workplan carries the single work-plan issue that holds state between agent sessions through its lifecycle — create, read (validate against live state and recommend next steps; writes nothing), resume, update, close-and-succeed. All GitHub writes are drafted first and gated on your approvalworkplan operational for update and resume (validated from an installed plugin 2026-08-20, and again 2026-08-25 on this repo’s own plan issue); its create, read and close verbs, and workplan-project, are merged procedures with no run yet — skills#3
/qe:benchmarkAdvise whether a lecture is worth converting at all (triage — the front door), or score a submitted NumPy→JAX/Numba conversion against the rubric (review)operational for workspace runs — guide, skills#4
/qe:audit-issuesSweep a whole tracker: verify each issue’s status against the code rather than the thread, tier the open set into the repo’s plan, deliver a report bundle. Read-only — it recommends, never appliesrun twice as a skill (2026-07-28, 2026-08-25); run 2 validated resume-across-a-lost-session and measured the read-only boundary, and left the closed pass’s checkpointing as the open defect — tutorial, guide, skills#16

Updating and troubleshooting

QuantEcon Skills
QuantEcon Skills
Guides
Developing skills