skills: prevent agent from using timeouts and retrying commands

When an S3 endpoint is slow, ramenctl hangs because it has no timeout
on S3 calls. The agent shell harness kills the command after 120
seconds, then the agent retries in the background with a new output
directory — wasting time and creating unexpected partial output.

Remove time estimates from the skills ("takes a few seconds locally
and about a minute on remote clusters") since the agent uses them to
guess a timeout. Add explicit rules to all agent context files:
- Run ramenctl commands without a timeout
- Do not run commands in the background
- Do not retry on timeout — report it and let the user decide

The real fix is adding S3 call timeouts in ramenctl itself so it
fails fast instead of hanging. These skill changes are a workaround
until that is done.

Assisted-by: Cursor/Claude Opus 4.6
Signed-off-by: Nir Soffer <nsoffer@redhat.com>

Author: nirs

pkg/skills/templates/agents/bob.tmpl

@@ -17,6 +17,7 @@ guidance that you need to follow precisely.
 
 ## Running commands
 
+- Run {{.Command.Name}} commands without a timeout.
 - Do not run {{.Command.Name}} commands in the background.
 - Do not retry a command that timed out — report the timeout and let
   the user decide.

pkg/skills/templates/agents/claude.tmpl

@@ -12,6 +12,7 @@ Run `{{.Command.Name}} init` to create a configuration file, then use
 
 ## Running commands
 
+- Run {{.Command.Name}} commands without a timeout.
 - Do not run {{.Command.Name}} commands in the background.
 - Do not retry a command that timed out — report the timeout and let
   the user decide.

pkg/skills/templates/agents/codex.tmpl

@@ -12,6 +12,7 @@ Run `{{.Command.Name}} init` to create a configuration file, then use
 
 ## Running commands
 
+- Run {{.Command.Name}} commands without a timeout.
 - Do not run {{.Command.Name}} commands in the background.
 - Do not retry a command that timed out — report the timeout and let
   the user decide.

pkg/skills/templates/agents/cursor.tmpl

@@ -17,6 +17,7 @@ Run `{{.Command.Name}} init` to create a configuration file, then use
 
 ## Running commands
 
+- Run {{.Command.Name}} commands without a timeout.
 - Do not run {{.Command.Name}} commands in the background.
 - Do not retry a command that timed out — report the timeout and let
   the user decide.

pkg/skills/templates/agents/generic.tmpl

@@ -9,6 +9,7 @@ steps, flags, and expected output that you need to follow.
 
 ## Running commands
 
+- Run {{.Command.Name}} commands without a timeout.
 - Do not run {{.Command.Name}} commands in the background.
 - Do not retry a command that timed out — report the timeout and let
   the user decide.

pkg/skills/templates/skills/gather-application.tmpl

@@ -49,8 +49,7 @@ $ {{.Command.Name}} gather application --name <drpc-name> --namespace <namespace
 
 Use `--config <file>` if the config file is not the default `config.yaml`.
 
-The command takes a few seconds on local clusters and about a minute on
-remote clusters.
+Run without a timeout — the command may take a while on remote clusters.
 
 ### Step 4: Check the result
 

pkg/skills/templates/skills/test-run.tmpl

@@ -38,8 +38,8 @@ Use `--config <file>` if the config file is not the default `config.yaml`.
 The test runs through the full DR flow for each test case:
 deploy, protect, failover, relocate, unprotect, undeploy.
 
-**This typically takes 15-20 minutes per test case.** Multiple test cases
-run in parallel.
+Run without a timeout — tests take a long time. Multiple test cases run
+in parallel.
 
 ### Step 3: Check the result
 

pkg/skills/templates/skills/validate-application.tmpl

@@ -55,8 +55,7 @@ report yourself in Step 4.
 
 Use `--config <file>` if the config file is not the default `config.yaml`.
 
-The command takes a few seconds on local clusters and about a minute on
-remote clusters.
+Run without a timeout — the command may take a while on remote clusters.
 
 ### Step 4: Check the result
 

pkg/skills/templates/skills/validate-clusters.tmpl

@@ -36,8 +36,7 @@ report yourself in Step 4.
 
 Use `--config <file>` if the config file is not the default `config.yaml`.
 
-The command takes a few seconds on local clusters and about a minute on
-remote clusters.
+Run without a timeout — the command may take a while on remote clusters.
 
 ### Step 3: Check the result