codex-setup

Convert Markdown PARA-ZK agent prompts into Codex TOML configurations.

7|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/kangig94/obsidian-para-zk --skill codex-setup-kangig94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-setup
Source: https://github.com/kangig94/obsidian-para-zk/tree/main/clients/skills/codex-setup
Command: npx skills add https://github.com/kangig94/obsidian-para-zk --skill codex-setup-kangig94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill bridges the gap between the PARA-ZK Obsidian plugin and the Codex environment, ensuring that specialized AI agents are correctly installed and configured to interact with your vault.

Core Features & Use Cases

  • Agent Synchronization: Automatically converts PARA-ZK agent definitions into Codex-compatible TOML files.
  • Workflow Integration: Enables specialized agents like wiki-weaver to function within Codex by mapping them to the correct command transports.
  • Use Case: After updating the PARA-ZK plugin, use this skill to refresh your local Codex agent directory so that your AI assistant can immediately access the latest vault-management tools and instructions.

Quick Start

Run the codex-setup skill to install or refresh all PARA-ZK custom agents in your local Codex configuration directory.

Frequently Asked Questions about codex-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync PARA-ZK agent definitions into Codex custom agents?

To sync PARA-ZK agents into Codex, convert Markdown-based agent prompts into TOML configurations and install them into the local Codex agent directory structure. This bridges the Obsidian plugin and Codex environment for immediate vault-management access.

What is the process for converting Markdown agent prompts to TOML for Codex?

Converting Markdown agent prompts to TOML involves transforming PARA-ZK Obsidian plugin definitions into Codex-compatible TOML files. This format conversion enables specialized AI agents to function within the Codex environment using mapped command transports.

Does the Codex agent setup validate command transport availability for Obsidian vaults?

Yes, the Codex agent setup validates command transport availability to ensure seamless interaction between Codex and the Obsidian vault. It checks MCP or CLI transports to guarantee specialized agents like wiki-weaver operate correctly.

Can I use PARA-ZK workflows with Codex if my agents rely on MCP or CLI?

Yes, you can use PARA-ZK workflows with Codex when agents rely on MCP or CLI. The setup maps specialized agents to the correct command transports, validating their availability to maintain continuous interaction with your Obsidian vault.

When should I refresh my Codex agent directory for PARA-ZK vault-management tools?

You should refresh your Codex agent directory after updating the PARA-ZK Obsidian plugin. Running the synchronization process ensures your AI assistant immediately accesses the latest vault-management tools and updated Markdown-based agent instructions.

What are the limitations of synchronizing PARA-ZK agents into Codex?

Synchronization depends on available MCP or CLI command transports between Codex and the Obsidian vault. If these transports are unavailable, validation fails, preventing specialized agents from functioning correctly within the Codex environment.