Skip to content
Skills Library
Programming · Building & coding

si-init

/si-init

Bootstrap or register a project's convention repair system in Codex, preserving existing records and separating Codex instruction wiring from Claude. Use for initial setup or checking the setup after a plugin update.

Licence
MIT
Last repository change
06.09.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Bootstrap or register a project's convention repair system in Codex, preserving existing records and separating Codex instruction wiring from Claude. Use for initial setup or checking the setup after a plugin update.

Original author description

Bootstrap or register a project's convention repair system in Codex, preserving existing records and separating Codex instruction wiring from Claude. Use for initial setup or checking the setup after a plugin update.

How it works

SKILL.md has no level-two headings · 48 lines, 393 words

SKILL.md preview
---
name: si-init
description: Bootstrap or register a project's convention repair system in Codex, preserving existing records and separating Codex instruction wiring from Claude. Use for initial setup or checking the setup after a plugin update.
---

# Initialize self-improvement in Codex

Read [runtime boundaries](../../references/runtime.md) and
[data discovery and format maps](../../references/data.md).

Identify the project root and the canonical existing system before creating a file. Existing
Claude registrations and table-less convention logs remain canonical. Do not copy a whole
CLAUDE.md into AGENTS.md, create a Claude import, or start a second log for Codex.

The bundled helper performs conservative, idempotent wiring:

~~~sh
python3 "<this-skill-directory>/../../scripts/init_project.py" --project "<project-root>" --check
python3 "<this-skill-directory>/../../scripts/init_project.py" --project "<project-root>"
~~~

Resolve the script relative to this installed SKILL.md, not to the shell cwd. Python 3.9+
is required only for the helper. Without it, perform the same inspection and minimal edits
directly; report that the helper was not run.

- The helper creates a neutral generated log only when no credible system exists. It
  registers existing data without modifying its bytes. Multiple candidates require an
  explicit canonical choice: `--data-file "docs/actual-log.md"`.
- Existing registered systems default to `archive: none` until their actual destination is
  confirmed. Preserve a legacy declared archive or pass `--archive "docs/actual-archive"`;
  this registers the path and does not move records.
- It writes only the marked Codex section in the effective AGENTS.override.md/AGENTS.md.
  Symlinked instruction files require inspecting their ownership first; do not bypass a
  refusal by writing through a link into CLAUDE.md.
- Inspect the reported format map and correct it to the real system's sections, log unit,
  budgets and archive. `none` is valid. Do not create missing tables just to satisfy defaults.

Inspect the actual document terrain: tool configs and scripts; nested Codex instruction
files; shared task/domain docs; Claude-only files as a separate runtime layer. On a new log,
fill §routing with existing locations or `none (create when needed)`. Add Codex destinations
to an existing routing system in its own format, without changing Claude's routing rows.

After a plugin update, compare the installed .codex-plugin/plugin.json version with the
Codex template stamp, if present. The helper intentionally preserves existing data. Inspect
stale wording and repair only Codex-owned fixed text when needed, preserving table values,
index, migration history, log bodies and all Claude stamps. A public/internal version
switch is not evidence that the data needs upgrading; inspect schema and content.

Report created / registered / unchanged / repaired, the real data path, effective Codex
instruction path, format map and any unmeasured or missing layer. Confirm Claude files
were not modified by Codex wiring. Next action: `$self-improvement:si-improve` when an evidenced gap recurs.

Versions

The database has no other skills named si-init.

Database snapshot: 13.11.2026 · package version 87cceaeef674 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100port-to-codex
    Ports a project's Claude Code setup (CLAUDE.md, skills, agents, MCP, hooks) to Codex: AGENTS.md becomes the shared instruction file with CLAUDE.md as a symlink to it, and Codex's .agents/skills/ and .codex/ are generated from .claude/ and .mcp.json with rulesync. Use when the…
  • 95si-archive
    Demote, merge, or archive over-budget convention docs and specifically identified dead or duplicate rules in Codex. Use for log rotation or named cleanup even below budget; exclude new convention repair and initial setup.
  • 100project-init
    Set up concise, guidance-first Claude/Codex/Grok project context after inspecting the repository. Use on first setup, after cloning, or when the user runs /project-init.
  • 100cc-spex-init
    Install or refresh Spex specification-driven workflows in the current project from the Spex source bundled with the cc-spex plugin. Use when a Codex user asks to initialize Spex, configure Spex extensions or security, or update an existing Spex project through the cc-spex plugin.
  • 100nacl-init
    Initialize or refresh a NaCl project for Codex by creating project configuration, graph infrastructure files, project registry entries, and optional Codex-readable guidance. Use when setting up a new or existing NaCl project, checking install discovery, or when the user says `/nacl-init`.
  • 100nacl-init
    Initialize or refresh a NaCl project for Codex by creating project configuration, graph infrastructure files, project registry entries, and optional Codex-readable guidance. Use when setting up a new or existing NaCl project, checking install discovery, or when the user says `/nacl-init`.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.