Structure
Show what a good manifest, checklist, template, or handoff note should contain.
Examples
Example workflows and templates
Reference workflows and templates. These are example operating patterns, not claims about real customer deployments.
How to use examples
Use examples as templates, not as customer claims.
These pages are designed to help teams understand structure and handoff. They should make the workflow easy to copy, while still making it clear that the examples are operating patterns.
Verification
Use the examples to check permissions, runtime evidence, and support readiness before launch.
Expectation
Make it obvious that examples are reference workflows, not promises of customer scale or production guarantees.
Manifest review template
Use this template to check display name, description, version, runtime, input schema, output schema, permission notes, examples, support path, and changelog.
Open guideSEO content brief workflow
This example shows how a team can move from keyword intent to page outline, citation gaps, FAQ, internal links, and implementation notes.
Open guidePublisher launch checklist
A publisher can use this checklist before submitting a Skill for review: schema, runtime evidence, pricing intent, support path, and changelog must be clear.
Open guideProject Key runtime test template
Use this template to verify authentication, input schema, policy decision, response shape, logs, and redaction before connecting a Skill to production work.
Open guideMCP tool description template
A good MCP tool description tells an Agent what the Skill does, when to use it, required input, permission risk, and when to ask a human.
Open guideSupport escalation handoff template
Use this template to summarize customer context, missing knowledge, suggested reply, escalation reason, and follow-up owner.
Open guide