Build your own

The plugin blueprint

How a Skales plugin is built so that it holds up: what to decide before the first line, what every plugin page keeps, where your approval sits, and how to check and share the result.

← Back to Plugins in the guide

1 · Start from something that works

The quickest way in is a template. Open Sidebar → Plugins, scroll to Start from a template, pick one and give it a name. You get a plugin of your own that already runs:

ListA page that keeps a list in the plugin's own storage, with undo. Needs no model, no key and no network.
AskA page that asks your model a question and keeps the last answers. Its button is an AI entry, so the manual mode hides it.
Weekly reviewAn agent on a schedule that writes a file into the plugin's folder every Friday; the page lists what it wrote. The paid weekly run starts paused unless you switch it on.
SnippetsA page of text you reuse, with two tools of its own: the chat and the plugin's agent search it with one and suggest a new snippet with the other. A suggestion waits on the page until you add it.

Then change it. By hand in the plugin's folder, or by asking the chat: "Change the plugin My list so that every item has a due date." Asking about the same plugin again changes that plugin and keeps everything it saved.

A plugin can bring tools of its own, the way Snippets does: a small module in its tools folder, declared with a name, a sentence on what it does, the input it takes and what it does to the world (only reads, changes the plugin's data, or sends something outward). The chat can build one for you: "Give the plugin Snippets a tool that counts the words of a snippet." A tool runs inside what the plugin was granted and never wider, a tool that sends something asks you first, and a declaration with a bad name or a missing module is refused by name instead of half-written.

2 · What makes a plugin hold up

  1. A real result first. Make the thing the plugin should produce once by hand, and use it. That result is what the plugin is measured against.
  2. A gold standard. Pick one finished result that every check has to pass. If it fails a check, the check is wrong, not the result.
  3. Only the public interface. A plugin reaches Skales through its page interface and its own tools, nothing else. If something is missing, it is missing for everybody, and it is asked for, not worked around.
  4. Every view named before it is built. The full list of screens in order, and one sentence that says what good looks like. Failures say what went wrong, on the page.
  5. Real example content. What the page shows on its first open is real, not lorem ipsum, so a person sees at once what the plugin is for.

3 · The brief, before the first line

A brief is ready when every row has an answer. A row without one is a question to settle first, not a guess to build on.

PartWhat it says
PurposeOne sentence: who does what with it, and what comes out at the end.
Reference resultThe real, hand-made result it is measured against, and who used it.
Gold standardWhich result every check must pass, and which checks those are.
ViewsThe complete list of screens, in order.
Quality barThe rule in one sentence, plus the shared rule of the three modes below.
Page actionsEvery action as a future tool of the plugin: its name, whether it reads, writes or sends, and where the approval sits.
Skales toolsThe tools the plugin may call, each with a reason. An empty list means none.
PermissionsNetwork, files and memory. Keys and sign-ins go through Skales' encrypted store, never into the plugin's folder.
Example contentWhat appears on the first open.
LanguagesEnglish first, then the others the plugin carries. Product names stay as they are.
Example jobsTwo to five sentences a person could hand the AI in the "AI does it" mode.
DistributionThe public catalogue, or a file you hand on yourself.
AcceptanceOne full run per mode, the gold-standard run, and the checks in section 6.

4 · The three modes are a contract

Every plugin with a page carries all three. Skales draws the choice under the page, remembers it per plugin and tells the page before it paints.

ModeWho presses the buttonsWhat the page does
ManualYouMarks every AI entry with data-skales-ai; Skales hides those in this mode.
With AIYou, the AI when askedShows its AI buttons; Skales adds a line to ask the plugin's agent.
AI does itThe AIOffers its actions as tools of its own; every change is one step that can be undone.

The rule all three share: the AI may do anything, you approve, and every step stays correctable on its own.

Where approval sits

5 · What every plugin page keeps

The page interface itself (storage, tools, model answers, jobs, previews, files) is described in the developer kit's plugin reference.

6 · Check it

7 · Share it

Ideas for a next plugin

A newsletter (lists, draft, design, test send, send, results), a small CRM (contacts, companies, pipeline, tasks, notes) or a shop helper (products, texts, pictures, prices, publish). In each, everything that sends or publishes asks you first.

← Plugins in the guide Roadmap →
Skales v12.9.60 · © 2024-2026 Mario Simic · Proprietary licence skales.app