Repository navigation
Codex Plugin
The PlainLogic plugin supplies one skill for implementing, writing, and validating PlainLogic. Its machine identifier is lowercase plainlogic; its display name is PlainLogic. The plugin and VS Code extension are independent installations.
The repository contains a portable Agent Plugins 1.0.0 manifest plus a Codex compatibility manifest and local marketplace. They all use the same maintained skills/plainlogic/ folder. The plugin adds no MCP server or lifecycle hook. Portable manifest · Codex manifest · Codex catalog
With Codex CLI available, clone a checkout and install from it:
git clone https://github.com/Sceleratis/PlainLogic-Language.git
cd PlainLogic-Language
codex plugin marketplace add .
codex plugin add plainlogic@plainlogic-localIf the repository is already cloned, open a terminal at its root and start with the marketplace command.
The first plugin command registers the catalog; the second installs its plainlogic plugin. These commands are supported by Codex CLI 0.154.0. If your client differs, inspect codex plugin --help and codex plugin marketplace add --help. OpenAI documents local and Git marketplace sources.
The checkout contains the complete skill resources, so plugin loading needs no npm install or build. Python 3 is used for the optional bundled structural checker. Interpretation and implementation use Codex's tools and model; this plugin does not introduce an independent compiler runtime.
Instead of registering a local checkout, use:
codex plugin marketplace add Sceleratis/PlainLogic-Language
codex plugin add plainlogic@plainlogic-localThis reads the remote repository. The manifests, catalog, and skill must be present on its remote default branch; changes that exist only in a local checkout are unavailable to this route. Both installation routes register the same marketplace name, plainlogic-local. Choose the source you want to track instead of registering both. A GitHub-backed catalog is sufficient for this workflow; it does not require claiming a listing in an official plugin directory. Repository installation guide
Start a new Codex session in the project whose code you want to work on. Select PlainLogic from the skill picker, or send a natural-language request:
Use PlainLogic on feature.plog.
Use PlainLogic on docs/requirements.md and implement it in this project.
Use PlainLogic on src/request.lua.
Use PlainLogic to write pseudocode from docs/requirements.md.
Use PlainLogic to validate feature.plog without implementing it.
These are agent prompts, not shell commands. A plugin-qualified name may appear in the picker depending on the Codex client. The short $plainlogic form below describes a standalone skill; do not assume an undocumented plugin namespace. Bare input defaults to validation followed by implementation. See Using PlainLogic for source conversion and mode selection.
To use Agent Skills discovery without a plugin loader, copy the entire skills/plainlogic/ folder into your target project's .agents/skills/ directory:
your-project/
.agents/
skills/
plainlogic/
SKILL.md
agents/
references/
scripts/
assets/
Keep every resource directory with SKILL.md; the workflow reads those references and uses its own checker/examples. Do not copy just the entry-point file. Codex documents repository skill discovery under .agents/skills.
Invoke a standalone installation with:
$plainlogic feature.plog
$plainlogic write docs/requirements.md
$plainlogic validate feature.plog
$plainlogic src/request.lua
Choose the plugin or the standalone copy to avoid duplicate skill entries. Other Agent Skills clients can consume the same complete folder at their own documented discovery path; that does not imply they support Codex's marketplace commands. For distributable ZIPs, see Development and Packaging.
PlainLogic 0.3 · Home · Implementation source · Validation limits
Learn
Install and use
Check and contribute