Menu
How to create and label GitHub issues for the ore repository. Load this skill whenever you need to open a new issue.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Codifies the principle of centrality-weighted reasonability for Go code in the ore repository. Central packages (many dependents, high change impact) must be radically simple, while peripheral packages (few dependents, low change frequency) can carry more internal complexity provided they are self-contained. The skill guides agents to keep code simple in a contextual way: simplicity is risk management, not a moral virtue.
Implements a new ore I/O conduit package under x/conduit/<name>/ using the functional-options constructor pattern, exported Descriptor for discovery, and blocking Start(ctx) lifecycle. Dumb pipe that translates external system events (HTTP, TUI, chat bot, webhook) into ore session events via junk.Manager, subscribes to broadcast FanOut output streams, and routes text/reasoning/image artifacts back to external systems. Compatible with the broadcast multi-conduit model. Does NOT handle cognitive orchestration, provider invocation, or turn-loop management.
Guidelines for creating, reviewing, and improving agent skills.
Guidelines for Go development, testing, and tooling.
Implements a new ore I/O conduit package.
| name | github-issues |
| description | How to create and label GitHub issues for the ore repository. Load this skill whenever you need to open a new issue. |
Load this skill whenever you are about to create a new GitHub issue in the
andrewhowdencom/ore repository.
Apply labels based on the issue type and scope. These labels are mandatory where they match.
If the issue is a plan — a design document, task list, or work breakdown for a planned feature or refactor — label it:
plan
A plan issue is typically a task list that links to implementation PRs or
describes a multi-step change. Use the same label regardless of whether the
plan also has a second label (e.g. conduit:http).
If the issue is associated with a specific conduit (an I/O adapter under
x/conduit/<name>/), label it with the conduit prefix:
| Conduit | Label |
|---|---|
| HTTP | conduit:http |
| TUI | conduit:tui |
| Future conduits | conduit:<name> |
Use the label that matches the exact directory name under x/conduit/.
Examples:
conduit:httpconduit:slack + planDo not add labels for:
artifact/, state/, provider/, loop/, junk/)Keep the label set minimal; only use plan and conduit:<name> when they
apply.