Skip to main content
This directory collects Codex-compatible skills that are useful for everyday workflows and personal operations. Each skill should be usable as an installable package with a human-facing README.md, an agent-facing SKILL.md, and only the supporting resources it needs.

Specialization IDs

Specialization IDs use two letters followed by a two-digit sequence number. The first letter identifies the category: G = General, P = Professional. The second identifies the format: W = Workshop-type short course, T = Internship with real-project engagement.

GW02 · Professional AI Agent Course

The Professional AI Agent Course composes twelve focused capabilities for Lessons 2–5. Each package link opens the complete skill codebase. Start with the shared setup and classroom guide; production course persistence is a separately tracked backend dependency.

PT01 · AI-Native Internship

The PT01 · AI-Native Internship specialization is a separate three-phase pathway: 4–6 private two-hour coaching sessions based on the student’s existing skill proficiency, a formal GitHub open-source contribution, and supervised real-project engagement subject to readiness and project matching. Coaching covers flexible content areas rather than a fixed session-by-session syllabus. Its curriculum and deliverables are documented separately from the GW02 skill packages.

Additional Practitioner Skills

Skill Package Shape

Each shared skill should keep the package itself small:
Use README.md for the human-facing story: why the package exists, who it is for, and the end-to-end workflow a student or operator should understand before using it. Use SKILL.md for the Codex invocation contract. Use scripts/ for deterministic helpers, references/ for rule files or supporting guidance, and agents/openai.yaml for UI metadata.

Contribution Type

Practitioner skill packages are code-plus-docs contributions. A package should include a human-facing README.md, an agent-facing SKILL.md, agent metadata, deterministic scripts, reference rules, and the minimum supporting documentation needed to make the skill reviewable and runnable. Do not treat these issues as documentation-only unless the requested change only edits explanatory pages.

Contribution Type

Practitioner skill packages are code-plus-docs contributions. A package can include Markdown instructions, agent metadata, deterministic scripts, reference rules, and the minimum supporting documentation needed to make the skill reviewable and runnable. Do not treat these issues as documentation-only unless the requested change only edits explanatory pages.

Practitioner Boundary

Practitioner skills should show where Codex execution is stronger than a plain chat answer: local files, persistent rules, repeatable workflows, browser or system interaction, and explicit safety checks.