Reusable model-workflow building blocks, when published.
The Marketplace direction is a home for templates, skills, workflow patterns, and connector building blocks that help teams start from a reviewable structure. It is framed as a place for reusable starting points, not as a promise that every workflow should become push-button automation. Templates, skills, and patterns matter because they give teams a stronger first draft for how work should be structured and reviewed.
Reusable patterns for model work.
The marketplace is framed as a reusable workflow direction: templates, skills, connector patterns, and model-work building blocks that can become useful as they are published. The goal is to help teams start from a reviewable shape instead of rebuilding every workflow from a blank prompt. A reusable block is valuable when it carries good defaults, clear boundaries, and understandable evidence expectations. Without that, a marketplace becomes a collection of shortcuts that are hard to trust.
- Reusable templates can give common workflows a clear starting structure. Reusable structure helps teams start from a known pattern instead of from scratch.
- Skills can package repeatable model-work patterns with review steps and evidence expectations. Good blocks should explain what they do, what they need, and what they should not imply.
- Connector patterns can show how context enters a workflow where supported. Review boundaries matter because reuse should not erase responsibility.
- Human approval remains part of sensitive or state-changing workflow movement. Evidence expectations help teams understand how a block should behave in practice.
- Marketplace inventory is presented through real resources as they become available. Availability should be tied to real published resources, not aspirational inventory.
Marketplace direction
The Marketplace is a direction for reusable building blocks that help teams start from known patterns as resources become available. The marketplace direction is about reusable shape: repeatable starts, clearer templates, and safer patterns for model work that appears again and again.
Workflow templates
Start common model tasks from a repeatable structure with inputs, steps, review points, and expected evidence. Templates should give teams a head start without hiding the workflow underneath.
Skill patterns
Package repeatable behaviors such as planning, review, extraction, summarization, or verification into reusable patterns where supported. Skill blocks are more useful when the expected context and outputs are named clearly.
Prompt structures
Save high-quality prompt patterns as reusable starting points while keeping outputs reviewable. Connector patterns help teams reuse context paths with better discipline.
Connector recipes
Describe how connected context can enter a workflow where connectors are supported and configured. Review notes matter because reusable work still needs local judgment.
Approval-ready workflows
Include human gates for sensitive or state-changing steps so users can review important movement before it happens. Evidence expectations help teams adopt patterns more responsibly.
Evidence expectations
Attach receipts, review notes, and evidence expectations to reusable workflows. Published inventory should speak for itself when it is truly available.
How reusable blocks should work
A marketplace block should give users a strong starting point without hiding responsibility. A good marketplace start should save time while preserving understanding.
Choose a template or pattern
The user starts from a published resource when available, such as a workflow template or skill pattern. Choose a block because it matches the job, not because it sounds impressive.
Review the inputs
The workspace shows what context the block needs and which model lanes may be involved. Review the block’s boundaries, assumptions, and evidence expectations first.
Inspect the steps
The user sees the planned workflow, review points, and approval boundaries before running it. Adapt the pattern to the team’s actual workflow and policies.
Run with evidence
Outputs, route decisions, logs, and receipts stay attached to the workspace history. Run it in a way the workspace can still inspect and approve.
Adapt before reuse
The user can adjust the structure for their context rather than accepting a template blindly. Keep the result connected to the team’s own record of what changed.
Visibility and control
Reusable does not mean automatic. Marketplace blocks should stay inspectable. Reusable does not mean opaque. The user should still understand what the block is doing.
Reviewable templates
Reusable blocks should show inputs, steps, model lanes, and expected outputs. Visible structure makes it easier to trust a reused pattern.
Approval points
Sensitive steps are easier to trust when the template makes review points clear. Assumption awareness helps teams avoid adopting blocks blindly.
Configuration notes
Templates can explain what needs to be connected, changed, or reviewed before use. Approval fit matters because different organizations reuse work differently.
Evidence expectations
Reusable workflows can define what receipts and records are useful to keep. Evidence expectations help teams compare a reusable start against real outcomes.
What this page represents
This page presents the Marketplace as a direction for reusable model-work building blocks. It explains the shape of the experience while inventory appears through real published resources. The page stays careful about inventory and availability. It explains the shape of a marketplace without inventing a catalog the repo does not prove.