​
Skill Map

​
Purpose

Onelink now uses a small skill family instead of one overloaded project skill. This gives AI agents:
  • a top-level coordinator for broad tasks
  • specialized execution guidance for the major project surfaces
  • cleaner prompts and smaller context when a task is narrow

​
Skill Family

Role:
  • top-level coordinator skill
  • use when the task is broad, crosses multiple project surfaces, or you need help choosing the correct specialized skill
Responsibilities:
  • classify the task
  • select the right execution surface
  • point the agent to the correct docs and specialized skill
  • preserve repo boundaries between app code, docs, and skills
Use for:
  • Rails models
  • services
  • controllers
  • jobs
  • policies
  • account-scoped backend features
Primary docs: Use for:
  • dashboard UI
  • widget
  • portal
  • survey
  • SDK frontend work
  • component sourcing and frontend state decisions
Primary docs: Use for:
  • application, platform, public, or survey APIs
  • request and response contracts
  • Swagger and OpenAPI updates
  • API docs sync into Mintlify
Primary docs: Use for:
  • omnichannel providers
  • inbox/channel setup
  • hooks
  • provider-specific flows
  • TikTok, WhatsApp, Instagram, Facebook, Line, Telegram, email, and similar surfaces
Primary docs: Use for:
  • Captain
  • copilot
  • documents
  • custom tools
  • assistant/scenario flows
  • AI-connected enterprise overlays
Primary docs: Use for:
  • Mintlify docs structure
  • page organization
  • docs content updates
  • docs repo workflow
  • OpenAPI file sync into docs
Primary docs: Use for:
  • self-hosted deployment docs
  • runtime operations
  • Docker and compose flows
  • deployment scripts
  • environment and infrastructure operating guidance
Primary docs: Use for:
  • Git and GitHub workflow
  • branch discipline
  • docs submodule pointer updates
  • versioned skill sync
  • upstream sync from Chatwoot
Primary docs:

​
Selection Rules

Use this decision order:
  1. if the task crosses multiple surfaces, start with onelink-builder
  2. if the task is narrow and obvious, use the specialized skill directly
  3. if the task changes docs and app code, use the surface-specific skill plus the docs workflow rules

​
Repo Awareness Rule

All skills should respect these repo boundaries:
  • app code changes commit in onelink
  • docs content changes commit in onelink/docs
  • the parent app repo commits only the updated docs submodule pointer after docs changes
  • versioned skills change in onelink/.codex/skills

​
Documentation Rule

Every implementation skill should:
  • read the relevant docs before editing
  • update docs/ when behavior, contracts, operator flow, or repo workflow changed
  • keep docs commits separate when the docs repository is involved

​
Where Skills Live

The versioned project source now lives under:
  • onelink/.codex/skills
The installed local skill library is expected under:
  • $CODEX_HOME/skills
In this workspace the current path is:
  • ~/.codex/skills unless CODEX_HOME points elsewhere
Use:
  • ./.codex/scripts/sync-skills.sh to-codex-home
to copy the versioned project source into the installed Codex runtime path. These skills are project tooling assets, not public product features.