vikarti.anatra/Skyvern
1
0
Fork 0
mirror of https://github.com/Skyvern-AI/skyvern.git synced 2026-04-29 20:20:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

Stop MCP model-key hallucinations in workflow creation (#SKY-8302) (#5061)

Browse source
This commit is contained in:
Marc Kelechava 2026-03-11 16:56:19 -07:00 • committed by GitHub
parent af91183d75
commit 87f18f4ee0
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
11 changed files with 810 additions and 26 deletions
Download patch file Download diff file Expand all files Collapse all files

1
skyvern/cli/mcp_tools/__init__.py
View file

@ -198,6 +198,7 @@ Validate blocks with skyvern_block_validate() before submitting.
Split workflows into multiple blocks — one block per logical step — rather than cramming everything into a single block.
Use **navigation** blocks for actions (filling forms, clicking buttons) and **extraction** blocks for pulling data.
Do NOT use the deprecated "task" or "task_v2" block types — use "navigation" for actions and "extraction" for data extraction. These replacements give clearer semantics and are what the Skyvern UI uses. Existing workflows with task/task_v2 blocks will continue to work — do not convert them unless the user asks. New workflows must use navigation/extraction.
For **text_prompt** blocks, default to Skyvern Optimized by omitting both `model` and `llm_key`. If an explicit model is required, use `model: {"model_name": "<value from /models>"}`. Do not invent internal `llm_key` strings.
GOOD (4 blocks, each with clear single responsibility):
Block 1 (navigation): "Select Sole Proprietor and click Continue"