Use an sks script
- For an executable task, search once with the sks MCP
search_scriptstool before writing or running ad-hoc code or shell commands. Use a concise capability query and preserve the user's domain terms. - Treat every request to use a script as an explicit search trigger, regardless of task size.
- Select matches by
commentandtags. Read the source resource or run--helpwhen arguments or behavior are unclear; do not invent arguments. - Run a selected script with
sks run <name> [args...]when execution is available and appropriate. The name is case-sensitive and must be copied exactly from the result. - If no useful match exists, continue with another approach. Do not repeat equivalent searches.
Skip discovery for purely conceptual discussion that requires no execution. Do not force a script when no registered script matches the task.