Describe why the material matters
Tag evidence by topic, relevance, and sensitivity. Keep it discoverable in the context of the skill and the question it helps answer.
Connect captured claims to their sources, identify the people and systems involved, and examine dependencies and exceptions before an AI Agent Skill moves forward.
Know what supports the decision.
01 / Build the context
A captured answer may name a system, assume a dependency, or describe an exception without explaining its limits. Validation connects those details so the skill designer and subject matter expert can examine the reasoning together.
Link answers, source files, people, processes, and objectives into a coherent evidence model. Review what supports the proposed action, where it applies, and what still needs to be established.
Bring in the source materialTag evidence by topic, relevance, and sensitivity. Keep it discoverable in the context of the skill and the question it helps answer.
Identify experts, applications, systems, and processes in captured material. Review those references so similarly named entities retain their intended context.
Link source evidence and expert statements to the dependencies they describe. Make the conditions behind a proposed skill available for examination.
02 / Follow a claim
Continue the release-recovery example from source intake. Examine the source, the dependency, and the unresolved exception to see how a broad statement becomes a more precise review question.
“An earlier application version can restore service after a failed release.”
The reviewer needs to establish the conditions under which this would hold.
Do these sources describe the same release, application version, and data model?
What evidence confirms compatibility between the application version and the data model it would encounter?
Ask the expert for the applicable recovery path, its limits, and the evidence that supports it.
Return to expert capture03 / Pursue the gaps
A missing dependency or conflicting explanation gives the next capture session a purpose. Bring the expert’s answer and supporting sources back into the same evidence model.
Clarify whether the source and the expert’s explanation refer to the same system, release, and point in time.
Ask for the exception, the signal that reveals it, and the action or escalation it requires.
Identify the expert who can explain the missing context and the artifact a reviewer can use to examine it.
Record what the follow-up resolved, which conditions now apply, and which questions remain open. Use review status and gaps to guide the next step.
Explore Skill Lifecycle Analytics04 / Carry it forward
The evidence model gives subsequent work a foundation. Keep the rationale, source references, operating limits, and unresolved questions available as the skill develops.
Examine the rationales, patterns, and escalation rules in the captured material. Keep each explanation connected to the context that gives it meaning.
Explore Reasoning AnalysisCarry ownership, provenance, and reviewed constraints into the skill’s lifecycle. Version and publish the skill through the catalog’s approval process.
Explore the Skill CatalogTest the skill against scenarios that exercise its conditions and exceptions. Inspect the reasoning and source evidence behind the response.
Explore the AI Skill PlaygroundStart with a decision that matters
Bring a workflow, a captured explanation, and the sources behind it. Work through the dependencies, operating conditions, and open questions that deserve review.