Summarizes Rob Sloan's harness-engineering talk and creates safe design artifacts for agent context beyond code: product-intent packets, design constraints, acceptance criteria, context ownership, and review gates. Use when the user asks about making non-code context agent-ready or improving AI work with product/design intent.
69
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Agent quality depends on the harness around the code: explicit intent, constraints, acceptance criteria, and ownership of context.
outline.md for the talk thesis, concept map, and safe application boundaries.quote.md when the answer needs a short supporting excerpt.transcript.md only to confirm what remained after safety redaction.When answering a factual question:
outline.md.quote.md only if it strengthens the answer.When applying the talk to the user's work:
When the user asks for operational mechanics, commands, credentials, mutable-source processing, or direct system actions, do not provide them from this bundle. Give the design-level alternative instead.
User: What context should I give an agent? Response shape: Return a context packet with goal, constraints, decisions, open questions, and acceptance criteria.
User: Can you connect to our design tool? Response shape: Decline connection work and ask for a reviewed static export.
a3808a9
Also appears in
on Aug 4, 2026
on Jun 18, 2026
on Jun 4, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.