Question 29
Domain 4A team writes a Cowork skill instructing the agent to 'use the GitHub tool to create issues' but no GitHub plugin is installed. What's the structural critique?
Correct answer: B
Explanation
A skill can only direct an agent to use capabilities that already exist; it does not add tools itself. Since the GitHub plugin is what “introduces the tool (capability),” a skill telling the agent to “use the GitHub tool” without that plugin is a miswire because the referenced tool does not exist.
Why each option is right or wrong
A. Cowork doesn't support GitHub integration.
GitHub integration can exist conceptually; the issue is that the required plugin is not installed.
B. Plugin vs skill miswire — the GitHub *plugin* introduces the tool (capability); the skill can only steer existing capabilities. Without the plugin, the skill's instructions reference a tool that doesn't exist.
The structural error is that the skill is attempting to invoke a capability that is not present in the agent’s toolset. In Cowork’s architecture, the plugin is the component that exposes the GitHub tool; a skill only provides instructions for how to use already-installed capabilities, so without the plugin there is no underlying GitHub tool for the skill to reference. The critique is therefore a plugin/skill miswire: the instruction points to a non-existent tool, making the skill unenforceable as written.
C. The skill needs to be in a different folder.
Folder placement affects organization, not whether a missing tool capability is available to the agent.
D. Skills are deprecated in Cowork.
Deprecation is unrelated; the failure comes from referencing a tool that was never provided.