tines
- 19 skills
- 0 followers
- 11 hours ago last updated
- ▌ Claude API · tinesBuild, debug, and optimize code that calls the Claude (Anthropic) API. Use when writing a step or service that calls Claude — covers picking a surface, the Messages API, choosing a model, prompt caching, tool use, streaming, thinking, and batch.
- ▌ MCP Client · tinesCall tools on a remote MCP (Model Context Protocol) server over streamable HTTP. Use whenever a connector is an MCP server (e.g. the “MCP server” connector type), or the user asks to list or invoke an MCP server’s tools, prompts, or resources.
- ▌ MCP Builder · tinesBuild high-quality MCP (Model Context Protocol) servers that let an AI interact with external services through well-designed tools. Use whenever you are building an MCP server to integrate an external API or service, in either Python (FastMCP) or TypeScript (MCP SDK). When the server is deployed as a 3B workflow, put it behind the built-in `space` or `tenant` route auth and let the platform authenticate clients instead of implementing the MCP OAuth handshake in the server.
- ▌ Tines Cases · tinesWorking with Tines Cases from a 3B workflow or chat — creating, updating, listing, and managing cases with their comments, subscribers, and activities, plus the Records store cases draw on. Use this whenever you’re asked to open, update, close, search, or manage a Tines case, to work with Tines records, or to call the Tines API for anything case- or record-related.
- ▌ Skill Creator · tinesWrite and improve 3B skills. Use when creating a new skill from scratch or refining an existing one — covers writing a description that triggers reliably, structuring clear instructions, and testing on realistic prompts.
- ▌ Status Update · tinesDraft evidence-based status updates from recent work across the user’s connectors. Use for daily or weekly updates, project summaries, stakeholder notes, and progress reports.
- ▌ Daily Briefing · tinesBuild a concise briefing from calendars, tasks, tickets, pull requests, messages, and documents. Use when the user asks what needs attention, what is assigned to them, or how to prepare for an upcoming meeting.
- ▌ Internal Comms · tinesWrite internal communications — status reports, leadership updates, incident reports, project updates, FAQs, and newsletters — in clear, consistent formats. Use whenever drafting an internal update, announcement, or report for a team or company.
- ▌ Webapp Testing · tinesInteract with and test web applications using Playwright. Use to verify frontend behavior, drive UI flows, capture screenshots, and read browser logs from a code step — whenever a task involves checking what a web page actually does in a browser.
- ▌ Building Agents · tinesBuild the AI parts of a 3B workflow — any step that calls a language model. Use whenever a task calls a model (Anthropic, OpenAI, Gemini, …) or is model-shaped — summarize, extract, classify, generate, rewrite, answer, converse, or a tool-using agent — even if “AI” or “agent” is never said. Covers choosing the shape, the agent step, the mandatory self-loop for async agents, tools, model choice, conversations, chat UIs, and single-request calls. Pair with the claude-api skill for Anthropic-native features (Batches, the Files API).
- ▌ Frontend Design · tinesCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
- ▌ Workflow Review · tinesExplain, test, simplify, and improve an existing workflow. Use when reviewing behavior, finding edge cases or failure points, validating sample data, or improving reliability, clarity, and performance.
- ▌ Dashboard Design · tinesBuild polished, interactive analytics dashboards for any data source. Use this whenever the request involves a dashboard, data visualization, internal metrics, spend/usage/cost reporting, or any UI that shows data sliced across time, users, categories, or other dimensions — even if the word "dashboard" is never used. Covers cross-filtering, shareable URL state, filter models, legends, transitions, honest handling of incomplete data, and visualization craft. Not needed for a single static chart.
- ▌ Building Workflows · tines bundleBuild and modify Tines 3B workflows from a workflow or space Git checkout, the 3B MCP server, the 3B CLI, or the in-product editor. Use whenever an agent works with workflow.toml, step directories, config.toml, FROM 3b/base Dockerfiles, workflow routes, links, triggers, connectors, step tests, or needs to create, inspect, run, debug, commit, or publish a 3B workflow.
- ▌ Tines Export To 3b · tinesYour guide to reading a Tines story export JSON and rebuilding it as a 3B workflow. Use this whenever you see a Tines export JSON, are asked to migrate or convert a Tines story to 3B, or hit Tines concepts like actions, Event Transformation, formulas, credentials, teams, or links and need the 3B equivalent in order to build it.
- ▌ Workflow Discovery · tinesTurn an automation idea into a clear workflow brief and practical design. Use when the user is starting a workflow, wants questions that clarify it, or wants workflow ideas based on their connectors.
- ▌ Cross Tool Research · tinesFind, correlate, summarize, and investigate information across the user’s connectors. Use for cross-tool searches, conversation or ticket summaries, and investigations that need alerts, logs, messages, documents, or code context.
- ▌ Workflow Operations · tinesAdd production operating behavior to a workflow. Use for schedules and event triggers, completion or failure notifications, targeted retries, operational logging, and follow-on automation.
- ▌ Workflow Volume Design · tinesDesign reliable 3B workflows that use named volumes or filesystem state. Use this whenever a workflow stores files, shares files between steps, persists state across runs, uses SQLite or cache files, handles uploads or generated artifacts, receives many concurrent inputs, runs parallel workers, builds reporting data, or needs temporary per-run files, even if the user does not mention volumes, scope, concurrency, exclusive writers, or filesystems.