Update to Tessryx

{
  "description": "Build an internal tool, admin page or team dashboard on Tessryx, such as an inventory list, a request tracker, a CRM-style list or a scheduled report, that only the owner's team can open. Use when the user asks for an internal tool, admin panel, back-office page, team dashboard or a tool to replace a spreadsheet.",
  "included_files": [],
  "name": "internal-tool",
  "skill_md_contents": "---\nname: internal-tool\ndescription: Build an internal tool, admin page or team dashboard on Tessryx, such as an inventory list, a request tracker, a CRM-style list or a scheduled report, that only the owner's team can open. Use when the user asks for an internal tool, admin panel, back-office page, team dashboard or a tool to replace a spreadsheet.\n---\n\n# Internal tool\n\nAn internal tool on Tessryx is a page gated to the workspace's own team, backed by datafiles the team edits in generated forms, with optional scheduled jobs. Follow `build-small-first` for the build order; this skill adds the parts specific to internal tools.\n\nThe user's explicit instructions always take priority over this skill.\n\n## Read first (only these)\n\n- `whoami`, then the `build-a-page` guide.\n- The `endpoints` guide, section \"Gated endpoints\", for `auth.allow.tenant_roles`.\n- The `datafiles` guide if the tool lists many records (\"Listing at scale\") or counts things.\n\n## First version (one sitting)\n\n1. An **app** with a short prefix (e.g. `ops`), and a **schema** for one record type (an item, a request, a customer). Datafiles under the prefix hold the records; the schema also gives the owner an editing form at https://tessryx.io/dashboard.\n2. **One page workflow** that lists the records, and an endpoint gated with `auth.required: true`, `allow.tenant_roles: [\"ROLE_OWNER\", \"ROLE_ADMIN\", \"ROLE_VISITOR\"]`, `expose_identity: true` and `on_unauthenticated.mode: \"prompt\"`. List every role that should get in; the match is exact.\n3. **Teammates use the tool as invited visitors** (`invite_visitor`): they sign in and use the pages, and take no seat. So people add and change records **on the page**: a JSON **route** (POST) that validates and writes them, called from the page's script, gated the same way with `on_unauthenticated.mode: \"refuse\"`.\n4. Preview, publish, give the link.\n\n## After it's live (offer, don't build unprompted)\n\n- A scheduled job that refreshes a summary or pulls data from another service (`schedules` and `api-templates` guides).\n- An email to the team when something needs attention (`workflows` guide, \"Email\").\n\n## Keep in mind\n\n- **Look:** dense and fast to scan: a clear table or cards, filters at the top, status colors that mean something, and big touch targets for people on phones.\n- Build it so the team works in the tool's own pages, not in the workspace dashboard: the owner builds, everyone else is an invited visitor. That works on the free plan.\n- Use one scheduled job at most, running no more than hourly, unless the user asks for more.\n"
}