Publish your first profile, preset, lorebook or plugin

In the prompt, preset and lorebook editors, open Build with AI to chat about your draft. Send follow-up changes or questions in the same conversation. Edits stay unsaved until you Save; Undo edits restores the draft before the last message, and New chat clears the conversation while keeping the draft.

1. Set up one of your keys the way you like it: preset, prompts, lorebooks, plugins and memory layer. The key's Active on this key summary shows what is on it.
2. On the API Keys page, choose Save as profile on that key.
3. Name it after what it's for ("Slow-burn fantasy", "Group chat narrator"), set visibility to Public in Discovery, and save.

Assets in a public profile have to be public too, or people applying it get the parts they can see and a note about the rest. If the profile uses premium memory or Composite-run helpers, Discovery marks it as needing credits on a provider key.

1. In Create, Presets, import a SillyTavern preset JSON. You can import several files at once; the result lists anything that was skipped.
2. Set visibility to Public before importing, or publish the draft afterwards.
3. Under Key setup, try it on your own key and switch individual sections on or off to check it reads well.

1. In Create, Lorebooks, start a new lorebook or import a SillyTavern lorebook or character book JSON.
2. For each entry, set its keys, and where needed its placement, sticky and cooldown timing, and regex. Book-level scan depth and token budget sit above the entries.
3. Use the Preview tab with a sample conversation to see which entries fire before you publish.

Entries can use {{char}}, {{user}}, {{random:a,b,c}} and {{roll:2d6}}; the reference lists them.

1. In Create, Prompts, open Creation, write the prompt, and give it a title, category, description and tags so people can find it.
2. Choose Public and save.

1. In Create, Plugins, build the workflow with blocks, or switch to the graph for full control.
2. A plugin can react to a command the user types, like [recap]; command names use letters, numbers, dashes and underscores.
3. Use Preview on key to watch it change a sample request, then set visibility to Public and save.

1. In Create, Voices, upload or record 3 to 15 seconds of one person speaking, or pick a preset voice. For a recording, confirm that it is your voice or that you have the speaker's permission.
2. Save the voice, then choose Make a sample. It speaks a fixed line with your saved voice on a key you pick, which is a real speech request billed like any other. The sample is what people hear on your voice's page and in Discovery, and publishing needs one.
3. Fill in Whose voice is this?: your own voice, an original voice, or the name of the speaker and that you have their permission. It is shown on the public page and is required to publish.
4. Set visibility to Public and save.

Nobody else ever receives your recording. They hear the voice through the sample and by using its code in speech requests. Changing the recording, model, transcript or speed hides the sample until you make a new one. Don't publish a voice that imitates a real person without their permission: anyone can report a voice for Impersonates a real person, and a voice a moderator hides stops working for other people's requests straight away.

Every public asset gets an eight-character tag code, shown when you save. People can apply it to a key from Discovery, or paste the tag, such as [lorebook:ABCD1234], into a character definition so it applies to that bot only. Votes and weekly use counts appear on its Discovery card.

Composite's content policy applies to public text just as it does to chat, and it is checked when you publish, not only when someone uses the asset. Link Discord on your account page and the Composite bot tells you when an asset of yours passes a use or vote milestone; the same milestones show as notifications on your dashboard.

Each public asset also has its own page at composite.lucidity.sh/lab/<type>/<tag code> that anyone can open without an account, and that search engines can find. It shows your description, votes, views and how many accounts use it, with buttons to apply it to a key or copy its tag.

Every time you save a public asset with changes, it becomes a new numbered version. Keys keep running the version their owner applied, so an edit never changes what someone else's bot does behind their back. Add a changelog line when you save; Discovery cards show it under an "Updated" mark, and people whose keys are on an older version see an Update button on their Keys page. A key can also be set to Auto-update to follow you. Your own keys always follow your edits.

Your public assets gather on your creator page (click your avatar, then your name): your username, when you joined, your main platform, your followers, and how many accounts use what you made. Set your platform and a short bio with Edit page. People can follow you, and your new and updated assets then show on their dashboard. Votes only count from accounts that have run a request with the asset, and the score appears once there are five. Views count once per person per day.

The Analytics tab on your own page shows views, applies, active users, requests over time, your vote trend and which models people use your asset with. It is always totals and daily counts, never who used it. Comments on your assets and your page are open to signed-in accounts, and you can reply to them and remove ones you don't want.

Add a profile picture under Edit page on your creator page. To give a profile, preset, prompt, lorebook or plugin a cover image, open it in Discovery (switch to Your drafts for unpublished ones) and choose Add image. The cover shows on its Discovery tile, its page and its cards on your creator page.

PNG, JPEG, GIF and WebP work. Images are cropped to a square from the centre and scaled down before upload, so pick one with the subject in the middle; animated GIFs keep only their first frame. Images follow the same rules as everything else you publish, and moderators can remove one without taking the asset down.

Fork on any public asset copies it into your own drafts. The copy is private until you publish it, and it keeps a credit to the original that shows on its page. Lorebooks and presets can be downloaded as SillyTavern JSON, from the asset's page or Create, so you are never locked in.

Anyone signed in can report an asset or a comment. Moderators can hide an asset without deleting it: it leaves Discovery and stops running on other people's keys, and only you can still see it. Publishing something close to another creator's older public asset is flagged for review automatically, so copy-and-repost gets looked at.