Skip to content

skill.md

Latest commit

 

History

History
49 lines (39 loc) · 2.55 KB

skill.md

File metadata and controls

49 lines (39 loc) · 2.55 KB
Raw
name tilde
description Build and operate TypeScript AI agents with Tilde tools, MCP servers, ChatKit, memory, skills, secure browser sessions, Dev Tunnels, and organisation controls. Use when connecting an agent to Tilde or configuring Tilde resources.
license MIT
compatibility Requires an MCP-compatible agent or Node.js 20 or later for the Tilde TypeScript SDK and CLI.
metadata
author version
Tilde
1.0

Use Tilde

Tilde is a TypeScript-first platform for building and operating AI agents. It provides secure tools and MCP servers, ChatKit, memory, skills, browser sessions, organisation controls, and portable state.

Start here

  1. Read the canonical agent context at https://trytilde.ai/llms.txt.
  2. Follow the Quickstart at https://trytilde.ai/docs/quickstart.
  3. Use the global Tilde MCP server at https://api.trytilde.ai/mcp for configuration tasks.
  4. Read the canonical OpenAPI description at https://trytilde.ai/openapi.json when implementing direct API integrations.

Choose the right surface

  • Use the global MCP server to inspect the current identity and workspace, discover provider and tool schemas, configure resources, and export portable state.
  • Use a runtime MCP server created in Tilde when an agent needs selected tools during normal work.
  • Use the TypeScript Tilde SDK when implementing ChatKit endpoints, custom tools, memory access, or application-side integrations.
  • Use the Tilde CLI for authentication, Dev Tunnels, and state import or export.

Safe operating rules

  • Call tilde_whoami before performing workspace-scoped configuration and use the returned team_id.
  • Discover provider, credential source, and tool identifiers from Tilde. Never guess identifiers.
  • Keep API keys, webhook signing keys, OAuth credentials, claim tokens, and PINs out of source code, logs, chat history, and generated state.
  • Treat tilde.state.yaml as portable configuration, not as a secret store.
  • Keep webhook verification and server-side credentials in ChatKit endpoints.
  • Ask before changing or deleting existing resources when the requested scope is ambiguous.

Reference