CLI Testing and Debugging

The fastest way to lose time in Worka pack development is to debug runtime integration problems too late.

Use the CLI and local tooling to verify the basics early:

• the pack builds
• the manifest is coherent
• the tools expose the names and schemas you expect
• the pack returns structured results

What usually breaks first

In practice, the first failures are usually:

• tool name mismatch
• incorrect manifest fields
• missing outbound or connection declarations
• pack code returning text where structured output is needed

If you validate those early, the later runtime path becomes much easier to reason about.