Name: totvs
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

totvs

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

Quality

74%

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/totvs/SKILL.md

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 a well-structured, highly actionable CLI guide with copy-paste commands, a clear connection/polling workflow, and validation checkpoints for risky states. Its main weaknesses are minor verbosity in the vendor intro and inconsistent step numbering ("1b" without a "1a") that slightly muddies navigation.

Suggestions

Trim or move the "TOTVS is a Brazilian software company..." intro, since Claude already knows the vendor; lead with the integration workflow instead.

Fix the step numbering (the lone "1b" heading has no matching "1a" or "Step 2" anchor) so the connection sequence reads as a coherent ordered list.

Consider splitting the large flags table and state-handling detail into a referenced file if the body grows, to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused ("membrane connection ensure", a flags table, short prose), assuming Claude's competence. Not a 5 because the opening "TOTVS is a Brazilian software company...helping them manage various aspects of their operations" explains vendor background Claude largely already knows. Not a 3 because the padding is minor relative to the actionable bulk.	4 / 5
Actionability	Commands are copy-paste ready throughout (login, connection ensure, connection get --wait, action run with --input JSON, request with a full flags table), and examples cover the common cases of discovery, execution, and proxying. Not a 4 because guidance is fully executable with concrete flags and parameters rather than leaving minor gaps.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, check error on CONFIGURATION_ERROR/SETUP_FAILED), giving real validation feedback loops. Not a 5 because numbering is inconsistent (a "#### 1b" heading with no matching "1a"/"Step 2" anchor), leaving minor sequence gaps; not a 3 because explicit validation/polling checkpoints are present.	4 / 5
Progressive Disclosure	Single self-contained file with clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and no nested references; structure is good and navigable. Not a 5 because the "1b"/"Step 2" references are slightly buried/inconsistent and there is no explicit signposting of deeper material; not a 3 because organization is solid with content appropriately placed.	4 / 5
	Total	17 / 20 Passed

Description

66%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 correctly includes both a "what" and an explicit "Use when" trigger, and TOTVS is a distinct niche with low conflict risk. Weaknesses are the awkward term "Recordses", thin trigger-term coverage, and a generic "Manage" action that understates the available operations.

Suggestions

Replace the non-natural term "Recordses" with natural phrasing like "records" and enumerate concrete operations (create, read, update, delete, list) to lift specificity.

Add trigger synonyms a user would actually say, e.g. "Use when the user wants to query, create, or update TOTVS ERP/CRM/HCM records."

Expand the "when" clause with concrete trigger phrases (e.g. TOTVS data, TOTVS records, ERP records) to reach full completeness.

Dimension	Reasoning	Score
Specificity	"Manage Recordses" names the domain (TOTVS) plus one concrete action, but "Manage" is generic and the coverage is not comprehensive (no create/read/update/delete/list enumerated in the description). Not a 2 because a concrete action is named; not a 4 because only one generic action is given with minor gaps being generous, and several TOTVS operations exist that are unstated.	3 / 5
Completeness	Both "what" ("TOTVS integration. Manage Recordses.") and "when" ("Use when the user wants to interact with TOTVS data.") are present. Not a 5 because the "when" trigger is generic ("interact with TOTVS data") without concrete trigger phrases; not a 3 because the "when" clause is explicit rather than weakly implied.	4 / 5
Trigger Term Quality	The term "TOTVS" is a natural keyword a user would say, and "interact with TOTVS data" is a usable phrase, but "Recordses" is an awkward non-natural term and common variations/synonyms (ERP, CRM, HCM, records) are missing. Not a 4 because keyword coverage is thin with no synonyms; not a 2 because at least one relevant natural term (TOTVS) is present.	3 / 5
Distinctiveness Conflict Risk	"TOTVS" is a clearly distinct niche (a specific Brazilian ERP/CRM/HCM vendor) with a distinct trigger unlikely to fire for unrelated skills. Not a 4 because the vendor name itself anchors a clear niche with minimal overlap risk.	5 / 5
	Total	15 / 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/totvs/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.