Where your map comes from

When you upload a version, Trilly makes its map in one of three ways:

  • From your trilly.json, when it has a map section with your steps.
  • From the map your skill's page shows now, when your trilly.json has no map and that map still fits the new files. Your changes in Studio carry over to the next version this way.
  • From your SKILL.md otherwise: one step for each line of your procedure checklist (under a heading like "## The procedure"). Trilly fills in the apps, the browser hand-off and your master file from your files.

Each way, the map waits for you on the version's page in Studio (Where the check is up to), under How it works.

Check it and change it

The map shows exactly as buyers will see it, in every look that suits it. Under it, the notes say anything the checks noticed. Choose Change the map to edit any step: what it's called, what it does, who does it, which app it uses, when it happens and where it stops. You can add steps, take them out and move them, with no extra software.

Before you send the version, tick The map above shows only what this skill does. If the map changes after that, tick it again. Once the version is sent, its map can't change: upload a new version to change it.

Rather not show steps? Choose Don't show steps for this version in the editor. The skill's page then shows the apps it can use, without the steps. You can write the map again any time before you send the version.

The rules a map follows

A map shows only what your skill does. Trilly checks it against your files when you upload and save it, and again when it reviews your version:

  • Each step that uses an app uses a kind of app your trilly.json lists. "Step 3 uses your calendar, but trilly.json doesn't list a calendar app" means you add one, or change the step.
  • Every change in someone's app waits for their yes, so a step that writes stops for "Your yes" first.
  • A browser helper fills in a website and stops before the final button. The person presses it.
  • A step after today needs a follow-up, tracker or diary heading in SKILL.md, or a calendar app that writes.
  • Steps name only the apps your trilly.json lists, and never pretend the AI sends, pays or books anything itself.

Naming the apps your skill uses

In trilly.json, each connector can list its apps with what your skill does in each:

"connectors": [
  {
    "category": "email",
    "examples": [
      "Outlook",
      "Gmail"
    ],
    "apps": [
      { "app": "Outlook", "reads": true, "writes": true },
      { "app": "Gmail", "reads": true, "writes": false, "note": "Read only: it writes the email for you to send" }
    ],
    "purpose": "Find earlier emails with your customer.",
    "reads": [
      "Earlier emails with the customer"
    ],
    "writes": [
      "One reminder email per customer, after your yes"
    ],
    "confirmBeforeWrite": true,
    "fallback": "You paste the earlier messages."
  }
]

Without apps, the map uses examples. An app Trilly doesn't know shows as you wrote it, and its steps show the copy-ready way. Make your trilly.json in Studio writes the file from the kinds of app and the apps you pick, and can add the map you checked.

Writing the steps yourself

Add a map to trilly.json to write the steps yourself:

"map": {
  "people": [
    { "id": "customer", "label": "Your customer" }
  ],
  "steps": [
    { "id": "find", "title": "Find who owes you", "does": "Lists every invoice more than 7 days late.", "who": "ai", "uses": "accounting", "action": "read" },
    { "id": "write", "title": "Write each reminder", "who": "ai", "uses": "email", "action": "write", "stop": "your-yes" },
    {
      "id": "send", "title": "You press Send", "who": "you", "stop": "only-you",
      "people": [
        "customer"
      ]
    }
  ]
}

Up to 12 steps and 6 people. Titles are 40 characters at most, and what a step does is 160. If the map says more than your files do, Trilly doesn't use it, says why on the version's page, and you check the map Trilly drafted instead.

When Trilly checks it

Trilly reads the map with your version, against your SKILL.md and trilly.json, before it goes live. If the map changes after that, it's read again. Read how skill maps work to see what buyers see.