Operational guide

How to use Agentique

Use this guide to browse the catalog, inspect resource records, understand scan and review readback, download with version, checksum, and target context, upload drafts, and contribute community feedback.

Core workflow

Move from search to adoption with context attached.

These steps cover the daily path for users and creators: find a resource, inspect the record, understand readback, download deliberately, upload drafts, and contribute feedback.

Browse and search the catalog

Start from the public catalog when you know the task but not the right resource.

Search by task, resource name, creator, tag, or format.
Compare task-fit summaries, compatibility notes, publisher context, and community feedback.
Treat homepage sample cards as illustrative examples, then use the catalog for current published resources.

Inspect a resource record

Open the detail page before adopting a resource.

Read what the resource does, which version is current, and which formats or runtimes it expects.
Check source or package references, parser import readback, publisher profile context, and compatibility notes.
If target-specific download buttons appear, confirm they are tied to materialized public download evidence.
Review warnings or missing context before downloading or following an external handoff.

Understand scan and review readback

Use visible checks as review signals, not as safety guarantees.

Look for scan and review signals where they are available on the record.
Read checksum context, parser/import readback, target guidance, warnings, and review state before reuse.
Use the transparency page for detailed platform boundaries when a resource looks risky.

Download with version, checksum, and target context

Keep resource identity attached to the handoff.

Confirm the resource name, version, publisher, and expected package or source reference.
Compare checksum context before using a downloaded package.
Use a target-specific file only when the detail page shows materialized public download evidence for that target.
Treat install-target guidance for other clients as setup context, not a direct install flow.
Keep visible review signals with the resource when sharing it with a team.

Upload a draft resource

Creators start privately and submit context before public listing.

Sign in, open the upload path, and create a draft with a clear name and summary.
Choose the resource format that best matches what you are sharing.
Add source, package, endpoint, version, compatibility, and example context before requesting review.

Prepare with Creator Kit

Use the Creator Kit path before uploading complex resources.

Review starter guidance, schemas, validator/readback packages, source-preview agent-native contracts, and release notes.
Use local validation as preparation, not as public approval.
Keep Marketplace-style promotion separate from the website upload path.

Manage account, library, and notifications

Use account surfaces to track private work and public feedback.

Use the account dashboard to return to drafts, owned resources, and saved context.
Keep library items organized while you compare resources for a task.
Use notifications to follow comments, review activity, collection changes, and security notices.

Contribute reviews, comments, and collections

Community feedback helps users learn without becoming verification authority.

Leave comments or reviews that describe actual use, limitations, and compatibility notes.
Save resources into collections when they help a workflow or team evaluation.
Report unclear or suspicious records so reviewers can inspect them.

Review states

Know what each visibility state means.

Agentique separates private drafting, limited sharing, review preparation, and public discovery so users can understand where a resource is in the path.

Draft

Private creator work in progress. Use it to add summary, format, version, source, package, endpoint, and compatibility context.

Unlisted

Available only through a direct path or owner surface. Use it for review preparation or limited sharing before public discovery.

Pending review

Submitted for review. Visible signals, warnings, and missing context may still change before public listing.

Published

Visible in the public catalog after the review path allows listing. Users should still inspect current context before adoption.

Resource formats

Choose the resource format that matches what you are sharing.

Pick the clearest representation for the resource. The guide keeps the choice focused on user inspection, compatibility, and handoff context.

Agent card or descriptor

Use this when the resource is primarily structured metadata, protocol description, task fit, or capability context.

External endpoint

Use this when the runtime stays with an outside provider. Agentique records endpoint context and does not proxy user tasks to it.

Downloadable package

Use this when users need package files, inventory, version notes, source references, checksum context, and target-specific handoff context before download.

Skill or workflow

Use this when the reusable value is a static skill, workflow template, example, or documented process; target-specific files appear only when materialized from public-safe evidence.

Resource bundle

Use this when several compatible records belong together but each item still needs its own context and review signals.

Boundaries

Use the signals without turning them into guarantees.

Visible checks are review signals

Scan and review readback helps users inspect context. It is not platform approval, not safety certification, and not a malware-free guarantee.

Upload is not direct public publishing

Creating a draft or using Creator Kit validation prepares a resource. It does not make the resource public by itself.

Install guidance is not direct installation

Target guidance can explain a client handoff, but only materialized download buttons provide files. Agentique does not install packages into external tools.

Community feedback is learning context

Reviews, comments, reports, and collections help other users evaluate fit, but they do not verify a resource.

Next step

Prepare a real resource or inspect the catalog.

Browse first if you are adopting. Use Creator Kit before uploading complex packages, endpoints, skills, workflows, or bundles.

Explore catalog Workflow resources Skill resources Creator Kit Upload resource