Skip to content

Getting Started

Install the plugins you need, check each one's requirements, and run a first skill.

Prerequisites

Claude Code (the CLI, the desktop app, or an IDE extension) runs every plugin. Codex, Copilot CLI and Antigravity CLI run techne, graphe and dokimasia; see Other agent CLIs. Each plugin's setup skill checks the rest and prints the install command for each tool that is missing.

1. Add the marketplace

From inside Claude Code:

/plugin marketplace add ajbarea/techne

2. Pick your plugin

Install only the plugins you use. Every enabled plugin's skill list sits in the agent's context on every turn.

Install each with /plugin install <plugin>@techne, then run its setup.

You want to Plugin Then run First run
Audit a build, review CI or a change, plan commits, catch up on GitHub techne /techne:setup /techne:audit in a repo with a Makefile, or /techne:catchup in any GitHub repo
Build LaTeX, PDFs or talk decks, scaffold or review a paper graphe /graphe:setup /graphe:latex paper/main.tex
Check a bibliography dokimasia needs only uv /dokimasia:check
Triage an idea against prior work heuresis /heuresis:setup /heuresis:idea --now <your idea>
Read and draft Gmail across accounts epistole /epistole:setup /epistole:catch-me-up
Check a Brightspace course site schole /schole:setup /schole:courses
Block attribution lines, guard commits, restart on update phylax switch options on in /config, then /phylax:setup /phylax:setup shows what is on
Hear a gist of each reply (WSL2 only) keryx keryx status speaks the next reply

Each plugin's page under Plugins lists what it needs, its commands, and its fixes.

Other agent CLIs

techne, graphe and dokimasia also run in Codex, Copilot CLI and Antigravity CLI. Codex and Copilot CLI read this repo's marketplace; Antigravity CLI installs one plugin from its folder URL:

codex plugin marketplace add ajbarea/techne
codex plugin add techne@techne

copilot plugin marketplace add ajbarea/techne
copilot plugin install techne@techne

agy plugin install https://github.com/ajbarea/techne/tree/main/plugins/techne

Swap techne for graphe or dokimasia to add those, then ask for a skill by name ("use the techne audit skill") or describe the task. graphe's optional OpenAlex and Semantic Scholar keys come from Claude Code's plugin settings; in other CLIs, export OPENALEX_API_KEY and S2_API_KEY in your shell. techne's opt-in cleanup at session start is a Claude Code hook, and several techne skills (elenchus, docs-site, deslop, reslop, docsync, research-grounded) hand part of their work to Claude Code subagents or /code-review; in other CLIs that step depends on what the agent offers. The other plugins rely on Claude Code's hooks, plugin settings or subagents and run there alone for now.

3. Set up

Run the setup skill for each plugin you installed. It checks what the plugin needs on this machine and prints the exact install command for anything missing. The doctors only read. Run a fix: line yourself when it contains sudo, and after ! in Claude Code.

Confirm the skills loaded:

/skills

The skills of the plugins you installed should be listed. If they are not, run /reload-plugins and check again. To pick up a newer techne, run /plugin install techne@techne again, or enable auto-update for the marketplace in /plugin.

4. First run: validate a build

Pick techne:audit and run it in a repo that has the Makefile pattern:

/techne:audit

It runs the phases your .claude/skill-context.md lists, then prints one table row per command (terminal exit code, archive SUMMARY rc, steps, elapsed) and a one-line verdict such as Full audit clean. A failing row names the archive to open.

Skills that change files show you the plan, report or diff before making changes. Review it, then say "go" or "apply" to execute it, or ask for changes.

Once one skill is familiar, combine them:

/techne:audit
/techne:auto-commit
/techne:ci-audit
/techne:deslop src/

Examples walks through real workflows.

Next steps