The /qovery-troubleshoot skill systematically tries to run qovery context and struggles hard with it. I am always forced to hint it to use the qovery log instead, passing the proper arguments.
● Bash(qovery context set --organization FooBarCompany --project "ACME" --environment Production 2>&1 | tail -5; qovery list-pods --service "API"…)
⎿ Interrupted · What should Claude do instead?
What about embedding it in the skill directly?
The
/qovery-troubleshootskill systematically tries to runqovery contextand struggles hard with it. I am always forced to hint it to use theqovery loginstead, passing the proper arguments.What about embedding it in the skill directly?