CtrlK
BlogDocsLog inGet started
Tessl Logo

tines

Tines integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tines data.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/tines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an actionable, command-driven guide with a solid connection-readiness feedback loop and good section structure. Its main gaps are a couple of broken step cross-references and inline reference-style content that could be split out.

Suggestions

Fix the dangling cross-references: either add explicit 'Step 1'/'Step 2' headers or replace 'skip to Step 2' with the actual section name (e.g., 'skip to Searching for actions').

Add a brief validation/verification note after running actions (e.g., check the `output` field for errors before treating a result as success), since action runs can fail silently.

Consider moving the Tines entity overview and the proxy flags table into a references file to keep the main flow lean and signal where detail lives.

DimensionReasoningScore

Conciseness

The body is mostly efficient, leading with executable commands and brief explanations; only minor padding remains (e.g., the 'focus on the integration logic rather than auth plumbing' aside and the introductory Tines definition).

4 / 5

Actionability

It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy requests, plus a concrete flags table, covering the common Tines integration cases fully.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→search→run sequence with a polling/state feedback loop for connection readiness, but dangling references to 'Step 2' and a '1b' section without a '1'/'2' create minor sequencing gaps.

4 / 5

Progressive Disclosure

Content is well-organized under clear section headers in a single SKILL.md with no external bundle files; some inline material (the entity overview list, proxy flags table) could plausibly live in a reference file, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is in third person and answers both what and when, anchored to a distinct platform. Its main weakness is generic action verbs ('manage', 'interact with') that lack specific Tines capabilities and natural trigger variations.

Suggestions

Replace generic verbs with concrete Tines capabilities (e.g., 'Create and trigger Stories, manage Agents and Credentials, query Events and Logs').

Add natural trigger phrases users actually say, such as 'when the user wants to automate a Tines workflow, manage Tines Stories/Agents, or query Tines events and logs'.

Mention the security-automation context as a trigger cue (e.g., 'Use for security team workflow automation in Tines').

DimensionReasoningScore

Specificity

It names the Tines domain and a few actions ('Manage data, records, and automate workflows'), but those actions are minimal and fairly generic rather than comprehensive concrete capabilities.

3 / 5

Completeness

Both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Tines data) are present; the 'when' is explicit but could be more specific about concrete triggering scenarios.

4 / 5

Trigger Term Quality

The natural keyword 'Tines' appears and there is an explicit 'Use when the user wants to interact with Tines data' trigger, but common variations, synonyms, or task-specific phrases users would say are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Tines platform gives it a clear niche with a distinct trigger, but the broad 'manage data, records, and automate workflows' wording leaves minor overlap risk with generic automation/data skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.