Explain reusable agent skills, prompt context, progressive disclosure, selection metadata, referenced resources, and the boundaries of permissions and validation.
Explain Skills and Progressive Disclosure in an Agent
Company: AMD
Role: Software Engineer
Category: Software Engineering Fundamentals
Difficulty: medium
Interview Round: Onsite
Explain what a skill means in an agent architecture, how it differs from an ordinary prompt, and how progressive disclosure can organize the information supplied to the agent.
### Constraints & Assumptions
Use a generic architecture: a skill is a reusable task package containing instructions and optional references or tools. Do not assume a specific product's file format or loading implementation.
### Clarifying Questions
How are skills discovered and selected? Which information is loaded initially? Who owns permissions and validation? What happens when a referenced document is untrusted or outdated?
### What a Strong Answer Covers
Reusable procedure versus per-interaction instruction, staged loading, context and selection tradeoffs, and limits of what a skill can guarantee.
### Follow-up Questions
How can too many skill descriptions harm selection? When should detailed references be loaded? Why does packaging a procedure not make every instruction in a retrieved document authoritative?
Overview: Explain reusable agent skills, prompt context, progressive disclosure, selection metadata, referenced resources, and the boundaries of permissions and validation.
Explain what a skill means in an agent architecture, how it differs from an ordinary prompt, and how progressive disclosure can organize the information supplied to the agent.
Constraints & Assumptions
Use a generic architecture: a skill is a reusable task package containing instructions and optional references or tools. Do not assume a specific product's file format or loading implementation.
Clarifying Questions Guidance
How are skills discovered and selected? Which information is loaded initially? Who owns permissions and validation? What happens when a referenced document is untrusted or outdated?
What a Strong Answer Covers Guidance
Reusable procedure versus per-interaction instruction, staged loading, context and selection tradeoffs, and limits of what a skill can guarantee.
Follow-up Questions Guidance
How can too many skill descriptions harm selection? When should detailed references be loaded? Why does packaging a procedure not make every instruction in a retrieved document authoritative?