Name: tiki
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

tiki

Tiki integration. Manage Recordses. Use when the user wants to interact with Tiki data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/tiki/SKILL.md

Quality

Content

68%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 content is highly actionable, with concrete CLI commands covering connection, discovery, execution, and proxying. Its main gaps are mild redundancy/padding and the absence of validation checkpoints around destructive Records operations.

Suggestions

Add an explicit validation/verification step for destructive Records operations (e.g. read-before-delete confirmation or a dry-run flag) and reference it in the Records CRUD workflow.

De-duplicate the `action list` command (present in both "Searching for actions" and "Popular actions") and trim padding like "so you can focus on the integration logic rather than auth plumbing".

Clarify the dangling "Step 2" reference in the Connecting section by labeling the next step or removing the cross-reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but contains redundant/padded passages such as "so you can focus on the integration logic rather than auth plumbing", a repeated `action list` invocation in two sections, and a Best Practices section that restates earlier guidance, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run with JSON input, proxy requests) plus a flags table, matching the fully-executable anchor that covers common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with state-based feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but the skill exposes destructive Records operations (create/update/delete) with no validation or verification checkpoint, so the destructive/batch cap holds it at 3 rather than higher.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clearly headed sections with no nested references and no bundle files present, matching the good-structure 4-anchor; it is not a 5 because some reference-like material (the detailed clientAction state machine and the proxy flags table) is inlined rather than split out.	4 / 5
	Total	15 / 20 Passed

Description

57%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 compact and correctly includes an explicit "Use when..." trigger plus a named domain, giving it solid completeness and distinctiveness. Its weaknesses are vague, singular action language ("Manage Recordses") and a lack of keyword synonyms/variations.

Suggestions

Replace the generic verb "Manage Recordses" with the concrete operations available, e.g. "Create, read, update, delete, and list Tiki Records."

Broaden trigger coverage with natural variations, e.g. "Use when the user wants to query, create, update, or delete Tiki Records or Tiki order/product data."

Fix the non-word "Recordses" to "Records" for clearer natural-language matching.

Dimension	Reasoning	Score
Specificity	"Manage Recordses" names the domain (Tiki) and a single generic verb over one entity, matching the anchor where the domain is named but actions are minimal/generic; it does not enumerate multiple concrete actions, so it is below the 3-anchor.	2 / 5
Completeness	It explicitly answers both "what" ("Tiki integration. Manage Recordses.") and "when" ("Use when the user wants to interact with Tiki data."), satisfying the 4-anchor where both are present though the trigger could be more specific; it is not a 5 because neither side uses concrete, varied trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural product term "Tiki" and the trigger phrase "Use when the user wants to interact with Tiki data", but offers no synonyms or variations (and "Recordses" is awkward), fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform "Tiki" gives a clear niche with low overlap risk, matching the mostly-distinct 4-anchor; it falls short of 5 because the trigger "interact with Tiki data" is generic within that niche rather than a sharply distinct trigger set.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/tiki/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.