How do I install the Tines Cases skill?

Run npx skillmds@latest add tines/tines-cases in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tines Cases safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tines Cases?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tines Cases free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Tines Cases?

tines (@tines) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tines Cases by tines — Agent Skill

Name: Tines Cases
Author: tines

Tines Cases

Working 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.

tines 325280d 2.6 KB Updated Sep 17, 2026

File contents

Working with Tines Cases

Tines Cases is Tines’ investigation and case-management surface, and Records is the structured-data store alongside it. You reach both through the same Tines Stories connector (identifier tines) that covers the rest of the Tines API.

Find the connector first

Before writing any call, use the searchConnectors tool with the identifier tines to find an existing “Tines Stories” connector. Reuse it if one exists. Only if none is found, prompt the user to create one with the connectStepToApp tool.

Read the endpoint doc before you write the call

Payloads have non-obvious fields, so fetch the specific endpoint doc and follow it rather than guessing. The API index the connector points you at links a per-endpoint markdown doc for every case operation and sub-resource (comments, records, subscribers, activities, and so on), and for every record operation. For a conceptual overview of how Cases works, see https://www.tines.com/docs/cases/overview/.

Flag ambiguity rather than guessing silently.

Records

Records are structured, queryable tables: a record type defines typed fields, and each record is a row of field values. They stand on their own, and a record can additionally be linked to one or more cases, e.g., when it’s evidence in an investigation. Records live under records, their schemas under record_types, and a case’s linked records under cases/<case_id>/records.

For a conceptual overview, see https://www.tines.com/docs/records/. Before writing record calls, read https://www.tines.com/llm/stories/docs/api/records/best-practices.md — it covers aggregate queries, pagination, filters, rate limits, retention, and linking records to cases.

Base path

Cases and records live under {TINES_URL}/api/…. Prefer the newest API version an endpoint offers, and don’t fall back to an older version just because the connector’s connection test happens to hit one. Versions vary by endpoint — some case-related operations sit under the newer version while others are still on the older one — so check the endpoint doc for the current version of each call rather than assuming a single base path.

---name: tines-casesdescription: Working 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.license: Apache-2.0---# Working with Tines CasesTines Cases is Tines’ investigation and case-management surface, and Records is the structured-data store alongside it. You reach both through the same **Tines Stories** connector (identifier `tines`) that covers the rest of the Tines API.## Find the connector firstBefore writing any call, use the `searchConnectors` tool with the identifier `tines` to find an existing “Tines Stories” connector. Reuse it if one exists. Only if none is found, prompt the user to create one with the `connectStepToApp` tool.## Read the endpoint doc before you write the callPayloads have non-obvious fields, so fetch the specific endpoint doc and follow it rather than guessing. The API index the connector points you at links a per-endpoint markdown doc for every case operation and sub-resource (comments, records, subscribers, activities, and so on), and for every record operation. For a conceptual overview of how Cases works, see `https://www.tines.com/docs/cases/overview/`.Flag ambiguity rather than guessing silently.## RecordsRecords are structured, queryable tables: a record type defines typed fields, and each record is a row of field values. They stand on their own, and a record can additionally be linked to one or more cases, e.g., when it’s evidence in an investigation. Records live under `records`, their schemas under `record_types`, and a case’s linked records under `cases/<case_id>/records`.For a conceptual overview, see `https://www.tines.com/docs/records/`. Before writing record calls, read `https://www.tines.com/llm/stories/docs/api/records/best-practices.md` — it covers aggregate queries, pagination, filters, rate limits, retention, and linking records to cases.## Base pathCases and records live under `{TINES_URL}/api/…`. Prefer the newest API version an endpoint offers, and don’t fall back to an older version just because the connector’s connection test happens to hit one. Versions vary by endpoint — some case-related operations sit under the newer version while others are still on the older one — so check the endpoint doc for the current version of each call rather than assuming a single base path.

Frequently asked questions