Search papers, labs, and topics across Lattice.
This paper articulates a software-engineering framework for developing Agent Skills, which are reusable procedural knowledge components for large language model agents. By advocating for principles such as single responsibility and low coupling, the authors provide a structured approach to skill construction that enhances agent behavior and efficiency. The study also introduces an evaluation-driven authoring process and compares skills with other behavioral shaping mechanisms, offering practical guidelines for developers in selecting the appropriate approach based on operational guarantees.
Skills for large language model agents can be engineered like software, ensuring better performance and reliability through structured design principles.
Agent Skills are an emerging way to extend large language model agents with reusable procedural knowledge that the agent loads on demand. Anthropic introduced Agent Skills and published the format as an open specification supported across several agent tools. This note argues that a skill is a software artefact and that its construction should follow software-engineering principles, with qualifications: single responsibility, separation of interface from implementation, low coupling, and economy in a shared token budget, together with behavioural evaluation in place of deterministic testing. Using Claude Code as the reference implementation, it describes how a skill is structured, how its contents are loaded in stages, and how to write the description on which selection depends. It places skills against the other mechanisms a developer can use to shape agent behaviour, like project memory files, slash commands, subagents, external tool connections, and hooks, and gives a rule for choosing between them based on who decides that a mechanism runs and what guarantee it provides. It then sets out an evaluation-driven authoring process, a set of patterns and faults commonly encountered in authoring, and the trust question raised by using skills from third parties. We illustrate the comparison drawn in UML class style, the loading model, the anatomy of a skill, the relative position of each mechanism, and the points at which skills and hooks act during a session.
