Skip to content

Move the agent's guides into skills and shorten its system prompt #9456

Open

Description

@bobbai00

Task Summary

Every call sends the same 26 KB system prompt, or 198 KB when all 168 operator types are allowed. Most of it is operator schemas, and the Python and R guides are always in it. Parts of it point at tools that don't exist.

Keep a short base prompt with the role, the rules that must hold, and one line per skill. Load a guide only when it's needed, look up an operator's schema with a tool, and make the Texera docs a skill whose pages load by name.

  • Skills use the open Agent Skills format (agentskills.io): a folder per skill with a SKILL.md that holds its name, description and instructions, and longer pages under references/. Claude Code, Cursor, VS Code and ChatGPT read the same format, so the skills can also be handed to outside assistants.
  • The agent loads a skill with one load_skill tool, and the prompt lists each skill's name and description.
  • Operator schemas are not a skill: they come from get_operator_schema (Give the agent one workflow edit tool that takes a patch #9481). A rule that must always hold is checked in a tool, not written in a skill.
  • Skills name tools, so they are written after Give the agent one workflow edit tool that takes a patch #9481 fixes the tool names.

For the docs work in #9421, #9424 keeps its page reader and its 25 questions but drops the keyword index. #9423's two prompt rules move into a skill.

What every call sends today, and what moves into skills

Task Type

  • Refactor / Cleanup
  • DevOps / Deployment / CI
  • Testing / QA
  • Documentation
  • Performance
  • Other

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions