Overview
A skill library may contain many detailed workflows. Loading every skill in full would consume a large portion of the context window. The architecture therefore separates discovery from execution.
The agent can load only the compact name and description of each skill. When the current request matches a skill, the agent loads the full instructions for that specific workflow.
This allows the system to know that many capabilities exist without paying the full context cost of all of them at once. The pattern becomes especially important as the skill library grows.
A useful rule is:
Keep always-needed preferences in persistent instructions. Keep task-specific procedures in skills. Load the detailed skill only when it is required.