Turn Process Notes into a Knowledge Base Article with Codex
Convert meeting notes, support threads, or an SOP draft into instructions for a specific audience. Include prerequisites, exceptions, ownership, and review details.
中文Install in Codex
Use Codex with access to a local project. Keep the skill directory and its companion files from the same pinned revision.
- Run git clone https://github.com/ClarentCinematics/Codex-Skills-for-Enterprise.git. From the checkout, run git checkout --detach 3598e7788282b6548430aadfcbfcfd7181ebb02a.
- Copy the full skills/knowledge-base-capture folder to .agents/skills/knowledge-base-capture in your project, with its companion files.
- Open your project in Codex. Select the skill via /skills or $knowledge-base-capture and use the example on this page.
Example task
Use fictional notes: operations can request template publication, the duty editor checks naming, rejected requests get a reason, and the owner is undecided. Draft an article for a new teammate.What to check
The article describes the audience, the request procedure, rejection handling, and source. Ownership stays open, along with any permissions or dates missing from the notes.
Original SKILL.md on GitHub · Updated
Frequently asked question
What if the knowledge base article has no named owner?
Mark ownership as pending and include it in the prepublication review. Keep the procedure grounded in the details that the notes actually establish.