CtrlK
BlogDocsLog inGet started
Tessl Logo

formtitan

FormTitan integration. Manage Forms, Submissions, Users, Roles, Integrations. Use when the user wants to interact with FormTitan data.

61

Quality

73%

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/formtitan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, actionable integration guide with real CLI commands and a clear auth/connection workflow including feedback loops. It loses points mainly on conciseness (intro prose and a bare entity list) and minor workflow gaps (an undefined Step 2 reference).

Suggestions

Trim the marketing-style intro and either remove the bare "FormTitan Overview" entity list or annotate each entity with its purpose so the tokens earn their place.

Resolve the dangling "Step 2" reference by either adding the referenced section or relabeling the subsequent sections as the continuation of the connection workflow.

DimensionReasoningScore

Conciseness

Mostly efficient command-and-table content, but the marketing-style intro ("enterprise-grade form and survey platform... used by sales, marketing, and operations teams") and the bare "FormTitan Overview" list of ~18 entity names with no guidance add low-value padding Claude could infer.

3 / 5

Actionability

Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) and an actions table with keys, but examples lean on generic placeholders (CONNECTION_ID, <actionId>) rather than a fully concrete end-to-end case, so it stops short of 5.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop after user action, but references to a "Step 2" that has no matching section and a disconnected overview list introduce minor gaps.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and tables and no bundle files to navigate; the all-in-one-file approach is reasonable for this integration guide, though the Popular actions and proxy-flag tables could plausibly live in a separate reference file.

4 / 5

Total

15

/

20

Passed

Description

78%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.

A concise, third-person description that covers both capability and trigger guidance with a clear niche. Its main weakness is a generic "Manage" verb and a broad trigger clause that lack the concrete action and trigger-phrase specificity of the top anchor.

Suggestions

Replace the single verb "Manage" with distinct operations per entity (e.g., "Create and edit Forms, retrieve Submissions, manage Users and Roles, configure Integrations").

Make the trigger clause more concrete by listing natural phrases, e.g., "Use when the user mentions FormTitan, forms, submissions, or wants to manage FormTitan data."

DimensionReasoningScore

Specificity

Lists several concrete managed entities ("Forms, Submissions, Users, Roles, Integrations"), though the single generic verb "Manage" covers them rather than naming distinct operations, leaving minor action-variety gaps vs the score-5 anchor.

4 / 5

Completeness

Both what ("Manage Forms, Submissions, Users, Roles, Integrations") and when ("Use when the user wants to interact with FormTitan data") are explicit, but the when clause is generic rather than enumerating concrete trigger phrases, so it does not reach 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("Forms", "Submissions", "Users", "FormTitan"), with good keyword coverage but missing common synonyms or variations, fitting the score-4 anchor.

4 / 5

Distinctiveness Conflict Risk

Tied to a uniquely named platform ("FormTitan integration") with distinct entity triggers, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

17

/

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.