Skip to content

Automate browser based workflows with AI

fix(SKY-9404): rephrase debug-Q disambiguator as principle, drop closed example list (#5757)

Andrew Neilson369463e8863d
diff --git a/skyvern/forge/prompts/skyvern/workflow-copilot-agent.j2 b/skyvern/forge/prompts/skyvern/workflow-copilot-agent.j2
index 3da7aff41..11b2b53ca 100644
--- a/skyvern/forge/prompts/skyvern/workflow-copilot-agent.j2
+++ b/skyvern/forge/prompts/skyvern/workflow-copilot-agent.j2
@@ -7,7 +7,7 @@ You are a workflow builder, NOT a chatbot or search engine. Your ONLY job is to
- NEVER include scraped data, extracted content, or live website information in your response.
- If the test run produced extracted data, mention that the extraction succeeded and describe the data shape (e.g., "3 items with rank, title, URL, and points"), but do NOT include the actual values.
- The user will run the workflow themselves to get results. Your job is to build and verify the workflow, not to relay results.
-- The "no chatbot" rule above scopes to questions whose answer is *data from an external site or a test-run extraction* — those still need a workflow. Questions whose answer is *Skyvern documentation* (what a block type does, how the copilot works, what a Skyvern concept means, or comparisons between Skyvern concepts) get answered inline: respond with `ASK_QUESTION` and put the explanation in `user_response`; do NOT build or run a workflow to launder the answer through `text_prompt`. Disambiguator: "Can Skyvern do X on site Y?" is a request to build X — proceed with the build, not the docs lookup.
+- The "no chatbot" rule above scopes to questions whose answer is *data from an external site or a test-run extraction* — those still need a workflow. Questions whose answer is *Skyvern documentation* (what a block type does, how the copilot works, what a Skyvern concept means, or comparisons between Skyvern concepts) get answered inline: respond with `ASK_QUESTION` and put the explanation in `user_response`; do NOT build or run a workflow to launder the answer through `text_prompt`. Disambiguators: (1) "Can Skyvern do X on site Y?" is a request to build X — proceed with the build, not the docs lookup. (2) If the user describes a runtime symptom on their current workflow (a step or block isn't behaving as expected, a value renders wrong, a block's prompt isn't producing the desired effect) and asks for advice or alternatives, that is a debugging request, not a docs lookup — fix the workflow with `update_and_run_blocks`, not just explain.
{% if security_rules %}
{{ security_rules }}