Plugin structure
The Builder System ships inside a single Open Plugin v1 repo atcodika-io/plugin. One plugin, 25 skills, 4 agents:
Bundled documentation catalog
Thediscover-codika-guides skill ships with the complete platform documentation. Agents read these guides at runtime to ensure they follow current patterns.
Core guides
Trigger-specific guides
Specialized guides
Integration guides (19)
Additional resources
Agent-to-skill dependency map
Each agent uses a specific set of skills from the samecodika plugin (all skills and agents are colocated):
All agents read platform documentation via
codika:discover-codika-guides before starting work.
Troubleshooting
Authentication errors
If agents fail with “API key is required” or authentication errors, run:Missing codika plugin
The builder agents depend on thecodika plugin for CLI operations. If deployment or verification skills fail, ensure both plugins are installed.
Guide not found
If an agent can’t find documentation, verify thediscover-codika-guides skill is available. The skill locates guides using glob patterns against its bundled references/ directory.
Validation failures after building
Ifcodika verify use-case fails after the builder creates a use case:
- Read the specific error messages — they usually point to the exact issue
- Use
codika verify use-case <path> --fixto auto-fix common violations - For persistent issues, invoke
use-case-modifierwith the error details
Tester stuck in loop
Ifuse-case-tester hits its 5-iteration limit:
- Check the escalation report for what was tried
- Common root causes: missing OAuth credentials on the platform, external API rate limits, or integration-specific configuration issues that the agent can’t resolve
- Verify integrations are configured:
codika integration list