Skills

Skills are the operational layer behind natural-language orchestration in CurdX Bridge. They turn a request like "let Codex review this plan" into a repeatable workflow with clear responsibilities and state transitions.

Why Skills Matter

Without skills, a multi-provider session becomes ad hoc very quickly. Skills give Claude a structured way to:

• send async requests
• run planning loops
• build execution artifacts
• enforce review gates
• advance automated task pipelines

Most users never need to type a skill name manually, but understanding the workflow helps you ask for better outcomes.

Skill Families

Communication

Skill	Purpose
cxb-ask	Send an async request to a provider

Planning And Execution

Skill	Purpose
cxb-plan	Build a reviewed implementation plan
cxb-task-plan	Convert an approved plan into task artifacts
cxb-task-run	Execute the next task step through AutoFlow

Quality

Skill	Purpose
cxb-review	Run dual assessment for a step or a whole task

Skill Workflow Pipeline

Recommended Mental Model

Think of the skill stack like this:

1. cxb-plan decides what should be done.
2. cxb-task-plan converts that decision into durable execution state.
3. cxb-task-run performs the next unit of work.
4. cxb-review decides whether the work passes or needs correction.

cxb-ask is the transport layer that makes all of the provider collaboration possible.

Common Workflows

Plan before coding

• Ask Claude to draft a plan
• Have Codex review the plan
• Only then start implementation

Break a feature into resumable steps

• Run the planning workflow
• Generate .curdx/ artifacts
• Resume later with curdx -r and continue execution

Use Gemini safely

• Ask Gemini for options
• Require Claude to classify each suggestion as adopt, adapt, or discard
• Send the final chosen direction to Codex for review

Power User Tips

• Ask for the skill outcome, not just the skill name. "Create a reviewed task plan for this migration" is better than "run cxb-task-plan".
• Keep review binary. Ask whether the result is ready to pass or what exact fix items remain.
• Use the task pipeline for larger work only. Small edits often do not need full AutoFlow.